The ‘EVD for Agile’ method combines Deloitte Digital’s standard Enterprise Value Delivery approach and agile development principles. It is based on Scrum, meaning that work is managed through quick iterations called Sprints, facilitated by the Scrum Master. Organizations are increasingly turning from Waterfall to Agile for improved responsiveness to business drivers, greater visibility into development, and faster implementation. Agile is an iterative approach to software development emphasizing flexibility, customer involvement, and rapid delivery of functionality, where requirements and solutions evolve through collaboration between self – organizing, cross-functional teams.
The Discovery phase consists of a two subphases, which are called “Project Planning” and “Sprint 0”. Project Planning includes the set up of the project vision and objectives. The planning of the different activities and the roadmap is proposed and agreed upon with the customer.
After a finishing the initial phase, a Sprint 0 is organized to establish the architecture and to set up the foundation. Also a Product Backlog is created, which consists of User Stories that form the basis for developments of the upcoming Sprints.
Each Sprint starts with 2 time-boxed meetings: The Backlog Ordering and Sprint Planning session. During the first meeting, all User Stories to be delivered over the lifetime of the project are prioritised. The Sprint Planning session prioritises the User Stories to be taken up during the upcoming Sprint.
The Sprint Backlog is the list of refined Product Backlog items chosen for development in the current Sprint, together with the team’s plan for accomplishing the work. It reflects the team’s forecast of what work can be completed. With the Sprint Backlog in place, the Sprint begins, and the Development Team develops the included user stories. The Development Team uses the Daily Stand-up meeting to ensure that they are on track for attaining the Sprint Goal.
At the end of each Sprint a Sprint Retrospective is organized among the members of the Sprint Team. The purpose is to review how things went with respect to the process, the relationships among people, and the tools. The team identifies what went well and not so well, and identifies potential improvements.
Also after the delivery of the Sprint the Sprint Team and stakeholders review the output of the Sprint in the Sprint Review session. If everything is accepted, the developed User Stories need to be deployed in the production environment and the release will be closed.