-
Notifications
You must be signed in to change notification settings - Fork 3
Agile Methodology
- Monday Catch-up/Daily 8:30 - 9:15 CET - 45 min depending on the feedback conversation
This meeting is split into 2
- 15 min, normal daily Stand-up as defined below
- 30 min max brief conversation based on the Sprint Retrospective feedback filled in by the team- adapt if required
- Tuesday, Wednesday, Thursday - Catch-up 8:30 - 9:00. Daily Stand-up as per definition below
- Sprint Review/Planning - Friday 8:30 - 9:30. This is a 1h session covering 2 Agile ceremonies (usually each session should have at least 1h but we're trying to keep things as efficient as possible so we made it shorter):
- 30 min Sprint Review internally for the team. This is the team meeting where we showcase what was done during the Sprint, open to the team's feedback.
- 30 min Sprint Planning - the team should define an achievable goal and define the task/user stories required to achieve it
- Friday - Sunday: team to fill in the Sprint Retrospective board here. Open items should be taken up for discussion in the Retro meeting on Monday.
As described in the Scrum Guide, the purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.
The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. To reduce complexity, it is held at the same time and place every working day of the Sprint. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.
As described in the Scrum Guide, Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team.
The Product Owner ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal. The Scrum Team may also invite other people to attend Sprint Planning to provide advice.
Sprint Planning addresses the following topics:
- Topic One: Why is this Sprint valuable?
- Topic Two: What can be Done this Sprint?
- Topic Three: How will the chosen work get done?
https://www.drutas.com/wp-content/uploads/2016/10/sprint-planning-2@2x.png
As described in the Scrum Guide, the purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.
https://files.sitebuilder.webafrica.co.za/64/24/6424676f-cc0e-4654-b08f-b11cd3afa039.PNG
What is a Sprint Retrospective
As described in the Scrum Guide, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.
During the Sprint Retrospective, the team discusses:
- What went well in the Sprint
- What could be improved
- What will we commit to improve in the next Sprint
https://scrumorg-website-prod.s3.amazonaws.com/drupal/inline-images/2017-03/SprintRetro.png
