Implementing an Agile Project Case Study
Traditional project delivery makes a large assumption that all requirements can be effectively identified at the start of the project. The stages executed in the implementation of a Traditional project are:
- Requirements and Design Signoff
- Development
- Testing and
- Release to production.
Backlog Refinement versus Requirements Gathering
The predominant tool in an Agile project is the product backlog. This is a set of features defined by the Product Owner in partnership with the stakeholders, customers and the scrum team. The features are categorized into Epics that align with major components within the product. Features are generally customer centric. Technical features may also be included to minimize risks, align dependencies and adequately prepare for multiple releases. The product backlog is refined continuously for relevancy. Features can be removed, priority adjusted, and changes made based on learnings from the scrum team.
Traditional projects assume that all requirements and design are defined at the start of the project. There may be some prioritization but, this is generally done when development teams realize that the time box may not be sufficient for delivery.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: