When to perform Major version Skimming
We are doing major redesign and Modernization in our application.
-- Moving out from deprecated rules
-- Redesiging some modules for better performance
--- Movement to case type management
Is it recommended to do Skimming before doing these changes?
Accepted Solution
Updated: 12 Feb 2024 7:56 EST
Pegasystems Inc.
US
@ShwetaB96Sounds like you don't need to rush into another major skimming at this point. Maybe after 6 months, your project can reconsider and include a major skimming and regression testing into your project planning when there is a next major phase of the project.
Updated: 3 Feb 2024 16:43 EST
Pegasystems Inc.
US
@ShwetaB96If teams have done development for a while (e.g. more than 1-2 years) without any major skimming, i'd suggest doing a *major* skimming to clean up unused rules to establish a new baseline going forward. Major skimming can be done after achieving some major milestone in the project and before starting a new major phase. Some clients do major skimming every year or so, but each client is different.
In our client, we are currently doing the first major skimming after 4 years of developments (which might be too long) and already see many unused rules cleaned up. Major skimming is supposed to improve overall application performance and maintenance and should be part of regular project cadence with stories points assigned and regression testing planned.
Infosys
IN
If we did skimming 1.5 years back and still we are left with 75+ minor versions should we continue working on these major changes without major version skimming
Accepted Solution
Updated: 12 Feb 2024 7:56 EST
Pegasystems Inc.
US
@ShwetaB96Sounds like you don't need to rush into another major skimming at this point. Maybe after 6 months, your project can reconsider and include a major skimming and regression testing into your project planning when there is a next major phase of the project.