An introduction to the development stage of the Way of Working.
The development stage is the part of the cycle where the product is actually built and tested. The development team delivers early and often, striving to maximise learning along the way. This stage is comprised of iterations which repeat until development is finished.
Before going into the development stage, a project must have:
- Completed the scoping stage.
- A backlog of stories in the first milestone.
- A project roadmap.
- The details required for hosting the product.
Before going into each iteration, the following things must be completed:
- Definitions of Ready and Done
- Planning session
- Internal elaboration
- Estimations for each ticket
- Final iteration plan
Meetings and Ceremonies
Every iteration consists of a series of meetings and checkpoints to ensure both product manager and team satisfaction, providing everyone with a chance to make suggestions and learnings.
Before each iteration, the team meets with the Product Manager to define the iteration goal and choose priorities for the issues. The team also works with the PM to define acceptance criteria for each task. Normally, this meeting is also merged with the review meeting for the previous iteration so that there aren’t two meetings in one day.
Normally, this is conducted at the same time as a planning session. The team presents the completed work from the iteration to the product manager, discussing what went well and what impeded development progress. This is the chance to review how the project is progressing and whether the team are on track to deliver the milestone on time.
This is an internal meeting within the development team. The purpose of this meeting is for the team to get more technical about each issue and ensure that all members understand both the requirements and the solution which will be implemented. At the end of the meeting, the team produces estimations against each issue.
Every day the team members have a daily huddle, where they discuss what they completed yesterday, what they plan to complete today, and if they have any blockers inhibiting their work.
At the end of each iteration, the development team conducts a retrospective session. The retrospective
is used as a chance to have a reflection on how the iteration went, and to identify actions for improvements going forward.
User Acceptance Testing Sessions
UAT sessions are conducted after each iteration has been completed, and is typically done between the testing team member and the project manager. You can learn more this process in the Conducting User Acceptance Tests article.
User Testing Interviews
User Testing interviews are conducted after an iteration or milestone has been completed. They are used to validate that what was built provides value to the user, and users can easily understand how to use the product.
Last updated: 15 January 2020