What's involved in the Agile Process?
At the beginning of the sprint cycle (every 7–30 days), a “Sprint Planning Meeting” is held. The exact length of each sprint should be determined by the Team, and should be relative to things like Project Timelines, Deliverable Due Dates, and how much time is required to complete tasks. This meeting is designed to preform the following tasks:
- (1st part) Product Owner + Team: dialog for prioritizing the Product Backlog
- (2nd part) Team only: hashing out a plan for the Sprint, resulting in the Sprint Backlog
Each day during the sprint, a project status meeting occurs. This is called a “daily scrum”, or “the daily standup”. This meeting has specific guidelines:
The meeting starts precisely on time
All are welcome, but only “pigs” may speak
The meeting is time boxed to 15 minutes
The meeting should happen at the same location and same time every day and during the meeting, each team member answers three questions:
At the end of a sprint cycle, two meetings are held: the “Sprint Review Meeting” and the “Sprint Retrospective”
Review the work that was completed and not completed
Present the completed work to the stakeholders (a.k.a. “the demo”)
All team members reflect on the past sprint and examine areas where improvements to the process are in order.
Two main questions are asked in the sprint retrospective:
Next time we shall see what Artifacts are produced from the process... Next Up Agile Part 4: Artifacts
It is the role of the ScrumMaster to facilitate resolution of these impediments. Typically this should occur outside the context of the Daily Scrum so that it may stay under 15 minutes. ↩