Thursday, October 2, 2014

SCRUM: A BREATHTAKING BRIEF AND AGILE INTRODUCTION - book summary

---

# book summary

Title: 'SCRUM: A BREATHTAKING BRIEF AND AGILE INTRODUCTION'

Authors:
  - Chris Sims
  - Hillary Louise Johnson

Scrum Definition: >
  Is a framework designed to help small teams of people develop complex products,
  the framework is not technical and can easily adapt the tools and practices to
  other industries.

more: >
  A Scrum team typically consists of seven (+-2) people who work together in short,
  sustainable bursts of activity called sprints, one of the mantras of scrum is
  “inspect and adapt” both the process and product.

# chapter 1: Roles
Roles:
  - Product-Owner
  - Scrum-Master
  - Team-Member

Product-Owner::responsibilities:
  - looks at ROI (product vision)
  - controls priority of work
  - responsible for user stories (business interests, customer, acceptance criteria, answer questions)

Scrum-Master::responsibilities:
  - facilitator (between team and stockholder)
  - team impediment resolver

Team-Member::responsibilities:
  - provides estimates
  - completes user stories

Team-size-significance:
  - few: less skills to finish the job
  - more: communication overhead

# chapter 2: Artifacts
Scrum-Artifacts (tools):
  - Product Backlog: Todo List of prioritized work items or user stories (e.g. features, bugs, doc etc)

Sprint-Backlog:
  - todo list (current sprint)

Story:
  - team deliverable unit
  - contains one or more task.
  - user (customer or owner to who the story will benefit)
  - description
  - value
  - estimate (size)
  - acceptance criteria (how to know that it was implemented correctly)

Task: 
  - person deliverable unit

BurnCharts: 
  - represents time(x-axis) and scope(y-axis), i.e. scope reduces with time.

Task-Board:
  - visible to all
  - contains todo, doing, done items
  - helps team and stakeholders see progress

Done-Definition: Team should define the definition to avoid confusion (code complete is not done may require other task like testing and releasing etc)

# chapter 3: Cycles
Sprint-Cycle-Meetings:
  - Sprint-Planning  (2 hrs)
  - Daily-Scrum       (15 mins)
  - Story-Time         (1 hr)
  - Sprint-Review     (30 mins)
  - Retrospective     (90 mins)

Sprint-Planning:
  - commit to stories and tasks

Daily-Scrum:
  - tasks completed
  - task expect to complete
  - any obstacles
  - problems are solved out site the meeting

Story-Time: discuss and improve product backlog

Sprint-Review:
  - show accomplishments to all including stakeholders
  - highlight any work not done
  - feedback

Retrospective:
  - what went well
  - what did not went well.

Frequent-demo: inspect and feedback

Notes:
  - Terminating a sprint half way is business decision.

No comments: