These key process areas are still in the v3. Yearly assessment allows assessing the progression of the improvements, no matter what best practice framework you are using. This is because it enables you to determine your software maintenance organizations maturity level strength/weaknesses against bet practices. Based on that assessment, you can pinpoint the best starting point for using S3M guidance. For example, if your organization is mature in its software evolution or correction services, then it’s probably time to assess the benefits of process management or support to evolution engineering activities.
Under S3M v2 my organization started with evolution engineering processes such as predelivery, transition and operational support. Does that change with S3M v3?
Posted in .