Skip to main content

Scrum Resume

Scrum Events​

Product Backlog​

Product Backlog is an ordered list by priority of items of requirements that the product must have (features, fixes, changes, improvements, etc). Items inside the Product Backlog are called Product Backlog Items. An item contains all that is needed to understand the requirements (description, estimation, acceptance criteria, etc). Note: Scrum don't force the usage of any tools to manage a backlog or form for the Product Backlog Items.

Scrum Events​

Sprint​

  • Objective: Having regular feedbacks on each iteration and make improvement on the product faster. Enable predictability.
  • Duration: one-month or less
  • Input: Scrum Events, Team scrum work
  • Output: A done increment

Each Sprint may be considered a short project

A scrum project is splited in sprints.

A Sprint is a repeatable fixed time-box during when all the things needed to develop a product (requirement, analyse, design, develoment and testing) are done. At the end of a sprint a shippable product increment is created and the Scrum team demonstrate the shippable product increment to stackholders and product owner. By mo means a release of the SPI is mandatory at the end of the sprint. It must be shippable but not necessarily shipped.

It allows to have regular feedbacks on each iteration and make improvement on the product faster. So that we have more chances to build the right product.

Sprints contain the Sprint Planning, daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective.

Sprint Planning​

  • Objective: Organize the sprint and define what can be delivered before it starts
  • Attendees: The Scrum Team
  • When: At the very beginning of the sprint
  • Where: unspecified by the scrum guide
  • Duration: 8h meeting for one-month Sprints
  • Input:
    • Product Backlog
    • Existing work
  • Outputs:
    • Current Sprint backlog
    • The described goal of the sprint
  • Responsabilities:
    • The Product Owner describes the objective (or goal) for the sprint.
    • The Developers plans the work necessary to deliver
    • Product Owner and Developers negociate the content of the sprint

Describe the goal of the sprint and how they to start working

Daily Scrum​

  • Objective: The Developers plans work for the next 24 hours, inspecting the progress toward the Sprint Goal since the last Daily Scrum and identify impediments.
  • Attendees: The Developers and optionnaly the Scrum Master. Other can present but must not participate.
  • When: everyday. Scrum Doesn't specify a specific time
  • Where: Same place everyday to reduce complexity
  • Duration: 15min max
  • Input: State of the Sprint backlog
  • Output:
    • Planned task for the next 24 hours
    • Defined impediments since the last Daily Scrum
  • Responsabilities:
    • The Scrum Master ensures that:
      • The Developers have the meeting
      • The 15mins are respected
      • Other do not disrupt the meeting.
    • The Scrum Team improve, within the Scrum process framework
    • The Developers :
      • Conduct the Daily Scrum
      • Plan task for the next 24 hours
      • Inform each other about the sprint advancement and the problems they encoutered
    • Product Owner or Scrum Master participate as Developers if they are actively working on items in the Sprint Backlog.

Sprint Review​

  • Objective: Inspect the increment done, take update from variables and adapt product backlog if needed
  • Attendees: The Scrum Team and stakeholders
  • When: At the end of the sprint before the sprint Retrospective
  • Where: unspecified by the scrum guide
  • Duration: 4h meeting for one-month Sprints
  • Input: Product increment of the current sprint
  • Outputs:
    • A revised Product Backlog and probable Product Backlog items for the next Sprint
    • Feedback from the stakeholders regarding the increments
    • Potential update on the timeline, budget, potential capabilities, and marketplace
  • Responsabilities:
    • The Scrum Master ensure that :
      • The event takes place and that attendees understand its purpose
      • The time is respected
    • The Product Owner :
      • Invite stakeholders
      • Explains what Product Backlog items have been "Done" and what has not been "Done";
    • The Developments:
      • Discusses what went well during the Sprint, what problems they ran into, and how those problems were solved
      • Demonstrates the work that it has "Done"
      • Answers questions about the increment

Sprint Retrospective​

  • Objective: Inspect how the last Sprint went with regards to people, relationships, process, and tools. Identify what went well, what could be improve and make a plan to achieve it
  • Attendees: The Scrum team only
  • When: After the Sprint Review and prior to the next Sprint Planning.
  • Where: As the scrum guide doesn't presice it the place may varie
  • Duration: 3h meeting for one-month Sprints
  • Inputs: Impression of team members on the last Sprint about to people, relationships, process, tools, etc.
  • Outputs: Plan for Improving to the process in the next Sprint.
  • Responsabilities:
    • The Scrum Master ensures that:
      • the event takes place,
      • attendants understand its purpose.
      • The Scrum Team improve, within the Scrum process framework
      • The meeting is productif and the time boxe is respected.
    • The Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of "Done"

Final say​

And that's it for a basic understanding of Scrum and its concept. As scrum is often mixed with other agile principles like users story or poker planning, it can be confusing to differential what is part of scrum and what is not.

Resources​