RELEASE PLANNING IN AGILE FROM A TESTING PERSPECTIVE
Architectural modelling and design of the end product are part of the initial backlog planning. This modelling is light in nature, with the remainder being completed based on feature sets included in sprints. Testers in the scrum team will use this model to create acceptance criteria and regression testing that focuses on test-driven development. This is extremely valuable to the developers in that the tests provide concise metrics for successful delivery of feature sets.
The sprint and release reviews will finalise which features are ready for release. The testers will aid the product owner in determining the readiness of a release. Releases may be postponed in order to execute another sprint that addresses defects or features that could not be completed during previous sprints. A product owner in partnership with project stakeholders, will also use the testers inputs to determine if some features can move back to the product backlog for future release consideration.
Date Driven releases are defined by calendar milestones. These milestones are usually tied to major events such as the end of a quarter, a holiday season or some other metric important to the organisation. As the product backlog is created, the testers develop acceptance criteria for use in development and testing. The velocity will determine the number of features that can be included to meet a milestone date.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: