SCRUM basics

In

SCRUM

Framework: teams: roles, events, artifacts and rules

  • begin: start with what can be seen or known
  • track teh progress and tweaks
  • it is based in pillars and values
    • values: commitment, courage, focus, openness and respect
    • pillars: transparency, inspection, adaptation
  • team members learn and explore those values with events, roles and artifacts

Pillars

  • transpareny: understanding progress status of features or product by all stakeholders
  • inspection: progress status and tools used should be reviewed regularly to identify undesirable gaps
  • adaptation: adjustment of process or material should be done as soon as possible, when several aspects of the process cross acceptable boundaries, as a result that the product will not be acceptable

Values

  • commitment: commit to achieve goals
  • courage: do the right thing
  • focus: on work and goals
  • openness: open about work and challenges
  • respect: members are capable and independent

Events

Time boxed, sprint duration can not be changed once it is defined

  • sprint
  • sprint planning
  • daily scrum
  • sprint review
  • sprint retrospective

Sprint

  • the heart of scrum
  • time boxed in a month or less
  • during the sprint
    • no changes are made which could endanger the goals
    • quality goals do not decrease
    • scope may be clarified and re-negociated between the PO and dev team as more is learned
  • considerations
    • each sprint may be considered a project with no more than 1 month horizon
    • are used to accomplish something
    • each sprint has a definition, a design and a planning
    • limited to 1 month top: enable predictability and limit risk

Sprint planning

  • plan with the whole team
  • 8 hours top
  • scrum master ensures the event happens
  • define goals
  • what can be delivered/how can that be delivered
  • what can be done
    • work selected from product backlog
    • the number of items is solely up to the scrum team
    • only developers can assess what it can be accomplished
    • backlog = forecast, not commitment
    • the goal is defined on planning
    • goal is objective to be met within sprint duthrough implementation of backlog, provides gudance to devs on why it is building this increment
  • how the chosen work gets done
    • once items are selected, scruym team decides how it will be on done during that time
    • product backlog items + plan to deliver = sprint backlog
    • after meeting, dev team self-orgnizes to undertake the work in the backlog and decompose this work in units of 1 day or less
    • by the ned of the sprint planning: the development team should be able to explain the PO and Scrum master how thet organize

Daily SCRUM

  • 15 minutes internal meeting for devs, other people should not disrupt
  • every dayplan work for 24 hours
  • optimize collaboration
  • after taht devs meet for detailed discussions

Sprint review

  • at the end of sprint
  • inspect Increment and backlog
  • informal meeting
  • result: revised product backlog that defiens probable backlog items for next sprint
  • SCRUM team + key stakeholders invited by PO
  • PO explains what is being done and what is not
  • dev team: what went well, what was solved
  • dev team demo
  • PO discuss backlog as it stands
  • eveyone gives valluable input for next planning
  • review timeline, budget…

Sprint restrospective

  • team inspects itself and creates plan for improvements
  • after the review, prior to next planningScrum master ensures it takes place, it is positive and productive

SCRUM team

  • Definition

    • 3 types of members
      • Product Owner (PO)
      • Development Team (DT)
      • Scrum Master (SM)
    • self organized and cross-functional
    • designed to optimize flexibility, creativity and productivity
    • delivers product iteratively and incrementally, maximizing opportunities for feedback.

  • Roles

    • PO

      • maximize value of the product resulting from DT work
      • clearly express and order the backlog to optimize DT work
      • makes backlog visible, transparent and clearly
      • 1 person, not a comittee

    • SM

      • responsible SCRUM is understood and enacted
      • facilitator for PO and DT
      • organizes events, helps improving

    • DT

      • deliver “done” product
      • 3 to 9 persons

SCRUM artifacts

  • Product backlog
    • ordered list with eveything needed by the product
    • PO is responsible of this
    • living artifact: it is never completed as it evolves with the productive
    • changes on business requirements, market conditions or tech = changes on backlog
    • product backlog refinement: adding details, estimates, order, done by PO + DT
  • Sprint backlog
    • items from product backlog selected for the sprint + plan to deliver them
    • forecast
    • highly visible, real time picture
  • Increment
    • sum of all items of sprint backlog completed on the sprint
    • 1 step towards a vision or goal
graph LR;
A[Product backlog]
B(sprint planning)
C[Sprint backlog]
D(Scrum team daily scrum)
E(sprint review)
F[Increment]
G(sprint retrospective)

A --> B;
B --> C;
C --> D;
D --> E;
E --> F;
E --> G;
G --> B;