CA's Agile Scrum development process (briefly).
-
CA maintains a backlog of major feature areas (called Epics) and smaller features (called Stories). These are expressed in external function and benefit form, such as an IDMS customer I need sets across page group boundaries to allow more growth in my database.
-
The IDMS team – led by the product manager and product owner – constantly “groom the backlog” evaluating and ordering items in importance.
-
Stories are broken down into smaller pieces that can be addressed in four-week cycles called Sprints.
-
At the start of each Sprint, the IDMS Scrum Team takes top ranked stories from the backlog and builds, tests and documents the story, resulting in working software.
-
Customers engage in end-of-Sprint demos and testing to provide early validation and feedback.
-
Software is released on a release or version basis, or more frequently as appropriate.