[Case Study] Scrum Proposal

The organisation here faces the issue with giving equal effort on new releases for the existing product. Because they continuously face support and maintenance requests for already insalled software. Being an ISO9001 certified company in quality management system, they are next considering Scrum methodology to overcome this problem.

According to the case here, the company does 4 major releases a year and does a lot of roll-up patches. They are spending considerable amount of time and effort to provide patches and minor updates. Looks like they could readily adopt the scrum methodolgy as the rate of errors is proven to be less with scrum. They have to ensure all of the pre-conditions for scrum are met before considering moving into scrum. As there is a support and maintenance team needed, they need to keep a team dedicated for that task. The overall project being a large, complex & mature system, the rest of the team should go through the scrum process. This way the customer is aware of the status of project throughout, is more deeply invovled. And also requests for future patches will reduce since the requirements can be incrementally modified at the end of each sprint (scrum iteration). Overall, scrum looks like the way to go for this team.

Reference: Case analysis based on case from: http://managingdesignanddevelopment.blogspot.ie/2011/09/scrum-proposal-case.html