Elusive Software by GloryKidd Technologies LLC

The endless pursuit of an unobtainable level of excellence in our code. The genuine enjoyment that is in the pursuit. To connect with us online, find us on...

Agile Part 3: The Process (the "How")

Elusive Software posted on July 13, 2016 in #Agile Development
| | Share on Google+

The Process

What's involved in the Agile Process?


Sprint Planning

Sprint Planning

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:

  • Select what work is to be done
  • Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team
  • Identify and communicate how much of the work is likely to be done during the current sprint
  • Eight hour time limit
  • (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
Daily Scrum

Daily Scrum

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:

  1. The meeting starts precisely on time

  2. All are welcome, but only “pigs” may speak

  3. 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:

  • What have you done since yesterday?
  • What are you planning to do today?
  • Do you have any problems preventing you from accomplishing your goal? 1

At the end of a sprint cycle, two meetings are held: the “Sprint Review Meeting” and the “Sprint Retrospective”

Sprint Review

Review the work that was completed and not completed
Present the completed work to the stakeholders (a.k.a. “the demo”)

  • Incomplete work cannot be demonstrated
  • Four hour time limit

Sprint Retrospective

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:

  • What went well during the sprint?
  • What could be improved in the next sprint?
  • Three hour time limit

Next time we shall see what Artifacts are produced from the process... Next Up Agile Part 4: Artifacts

  1. 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.