Scrum

What is Scrum

Agile process framework, where deliverable are

• defined as stories and epics

• each story should bring value by itself, when delivered

• work is split into sprints (2-4 weeks) of work

• the team commits to the amount of work to deliver per sprint, and no one else

Roles

• scrum master (SM)

  • facilitate ceremonies, blockers

  • shield team from outside interference

  • reduce current sprint changes

• product owner (PO)

  • defines priorities

  • manage backlog

  • stakeholder interaction

  • define deliverable, and high level tasks

  • manage milestones

• team member (TM)

  • chooses the work that can be done

  • powerhouse

  • can do attitude

The team

• diverse

• collaborative

• open

• autonomous

• empowered

• accountable

Ceremonies

• daily

  • daily meeting to discuss: what did you do yesterday, what are you doing today, what are your blockers

  • each persons goes one by one, to discuss the above, without interruption (except for clarification once everything is said)

  • usually time-boxed to 15 mins in total (1-2 mins/pers)

• planning

  • define and size the work for the next spring

• review (demo)

  • team and stakeholders discuss what was done (and potentially present)

  • analyse the work that was committed vs the achieved

• backlog grooming

  • clarify, split work, identify potential blockers for future work (2-3 sprints in advance, or from the backlog)

  • arrange backlog in priority order

  • raise new cards, drop no longer needed cards

• retrospective

  • team + sm only

  • ask: what went well (celebrate), what can be improved, what to commit to improve (action items and timelines)