Scrum Master Notes

Comments

Sprint Overview

Roles

  1. Product Owner - The voice of customer, responosible for the Product Backlog
  2. Scrum Master - Servant Leader, responsible for ensuring the team is fully functional and productive
  3. Scrum Team - self-organising and self-managing, responsible for the outcomes of the sprint

Ceremonies (meetings)

  1. Sprint Planning
  2. Daily Scrum (stand up) - daily updates
  3. Sprint Retro - reflective look back
  4. Sprint Review - demo to product owner and customer and give feedback

Artefacts

  1. Product Backlog - list of objectives need to be done to deliver the product. Product Owner is responsible for the Product Backlog, decides what should be in it
  2. Sprint Backlog - list of tasks for the current sprint, Scrum Team move tasks from Product Backlog to the Sprint Backlog and only focus on these tasks for the sprint
  3. Scrum Board - visible to client, tasks for the day
  4. Burndown Chart - visible to client, tasks for the day
  5. Sprint Delivery - Tasks finished at the end of the sprint, should be the same as Product Backlog if nothing had gone wrong

Non Core Roles

  • Stakeholders
  • Scrum Guidance Body
  • Vendors

Ceremonies

Sprint Planning

  • Agreeing and committing to what tasks will be done in the next sprint, move tasks from Product Backlog to Sprint Backlog

Daily Stand Up

  • The team provides short and concise progress updates daily

Sprint Review / Showcase

  • Allows stakeholders to assess progress and re-prioritise Product Backlog if necessary

Sprint Retro

  • Where performance inefficiencies are discussed and opportunities for improvement are identified.
  • What went well, what didn’t go well, what can we start / stop doing (for scrum team itself)

Non Official Ceremonies

Release Planning

  • Identifying and communicating how often a solution will be released and what features will be included

Elaboration

  • Ask questions and understand the problem in Backlog

Backlog Grooming

  • Review and redefinition of existing tasks

Backlog Prioritisation

  • Prioritise the Backlog tasks

Risk Review Sessions

Scrum Artifacts

Prodcut Backlog

  • List of tasks within the project

Sprint Backlog

  • List of tasks to be done within the next sprint

Scrum Board and Burndown Chart

  • Tracking progress and commmunications in an open and visual way

Scrum Principles

Empriical Process Control

  • making decisions based on observation and experimentation rather than detailed upfront planning
  • Transparency, Allows all components to be observed by everyone
  • Inspection, Monitoring in place to ensure deliverables conform to stated requirements
  • Adaption, Lessons learn through transparency and inspection used to improve performance

Self Organisation

  • Deliver greater value
  • Team buy-in and shared ownership
  • Higher levels of motivation
  • Innovative and creative environment

Collaboration

  • Awareness, be aware of each other’s work
  • Articulation, paritition work into units
  • Appropriation, adapting technology to one’s own situation

Value Based Prioritisation

  • Delivering value to the customer on an early and continuous basis
  • Methods used: Paried Comoparison, KANO, MoSCoW (Must, Should, Could, Won’t), 100 point comparison

Timeboxing

  • The rhythm to which stakeholders work / contribute

Iterative Development

  • Deliver value throughout the project, incorporating change as part of the process, adapt to the changing requirements

Scrum Aspects

Business Justification

  • based on the concept of value-driven delivery

Quality

  • Definition of done, a set of rules that are applicable to all user stories
  • Ways of working, a set of guidelines that make up a social contract between the Scrum Team

Change

  • Adapt of change, it is inevitable

Risk

  • Need to be identified and mitigated early, they are inevitable

Scrum Phases

Initiate

  • The Initiate phase includes the processes related to initiation of a project – these are all pre-sprint activities such as
    forming of the Scrum Core Team, identification of stakeholder, development of high level requirements (epics), creation
    of the Prioritised Product Backlog and release planning.

Plan and Estimate

  • This phase consists of processes related to planning and estimating tasks for the upcoming Sprint (Sprint Backlog).
    These activities happen during the Sprint Planning Meeting.

Implement

  • Implementation is related to the execution of the tasks and activities to create a project’s products. These activities
    include creating the various deliverables, conducting Daily Stand Up Meetings, and grooming (i.e., reviewing, fine-tuning,
    and regularly updating) the Product Backlog at regular intervals.

Review and Retrospect

  • This phase is concerned with reviewing the deliverables and the work that has been done during the sprint (Sprint
    Review Meeting) for acceptance and determining ways to improve the practices and methods used to do project work
    and for incorporation into future sprints (Retrospect Sprint Meeting).

Release

  • The release phase is focused on delivering/shipping the Accepted Deliverables to the customer and identifying,
    documenting, and internalising the lessons learned during the project.

Writing a User Story

  • User Stories will allow the Product Owner, Stakeholders and the Scrum Team to discuss, prioritise and deliver requirements and features
  • As a Role, I want to Perform an action, so I can achieve an objective
  • Epic, Feature, Story
  • story delivers business value

User Story Estimate

  • story points

Acceptance Criteria

  • Conditions that developers and testers will use to complete the stories
  • the story will need to satisfy acceptance criteria to be considered complete

Scrum of Scrums

  • Chief Product Owner
  • Chief Scrum Master

Yuan ChengSoftware Engineer

Wait and see