...
The Agile process HDX uses is broadly similar to Scrum, a framework to support teams in complex product development. In scrumScrum, the time available to work is broken down into time periods known as Sprints of two weeks during which a “Done”, useable, and potentially releasable product Increment is created. It is helpful to look at a diagram of the Scrum Framework.
...
The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint. Only members of the Development Team create the Increment. They are self-organizing: no one (not even the Scrum Master or Product Owner) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.
...
- The previous day's work
- Progress toward the Sprint Goal
- Work for the next 24 hours
- Any impediments to progress.
Deployment to Staging and Testing (+2 weeks)
The completed product Increment is deployed to a staging server and testing is performed. Relevant team members from outside the Scrum Team can help with testing.
Sprint Review (+2 weeks, Tuesday XX:XX CET for X hours)
...
- The Product Owner explains what Product Backlog items have been "Done" and what are not "Done".
- The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved.
- The Development Team demonstrates the work that it has "Done" and answers questions about the Increment.
- The Product Owner discusses the Product Backlog as it stands. She projects likely target and delivery dates based on progress to date (if needed).
- The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint.
- The Product Backlog may also be adjusted to meet new opportunities.
Minor Bug Fixes and Deployment to Production ( > Sprint Review date)
Any last minute minor bug fixes are implemented and if there are no serious issues, the completed product Increment is deployed to production.
Sprint Retrospective (+2 weeks, Tuesday XX:XX CET for X hours)
The Sprint Retrospective is a formal opportunity for the Scrum Team to:
- Inspect how the last Sprint went with regards to people, relationships, process, and tools.
- Identify and order the major items that went well and potential improvements.
- Plan ways to increase product quality by improving work processes or adapting the definition of "Done" if appropriate and not in conflict with product or organizational standards.
- Enumerate improvements to its development process and practices to make it more effective and enjoyable for the next Sprint.
Periodic Demo to HDX
When major pieces of work are completed eg. an Epic, there will be is a demonstration to the wider HDX Team which offers an opportunity for discussion and feedback.