Based

 on  the  Scrum  Guide.  October  2011  Edn

Scrum Aide Memoire
Scrum  (n):  A  framework  within  which  people  can  address  complex  adaptive  problems,  while  productively  and  creatively  delivering  products  of  the  highest  possible  value.
Roles Artifacts Events Miscellaneous
Product  Owner  (PO) Product  Backlog  (PB) The  Sprint Scrum  Team  (ST)
Resonsible  for  maximizing  value  of  the  product  &  DT Single  source  of  requirements  for  a  project Time-­‐box:  <=  A  calendar  month.  Must  be  consistent Consists  of  PO,  SM  &  DT
Manages  Product  Backlog,  incl.  order PO  solely  responsible  for  content,  avail  &  ordering Work  on  SBI's  until  "Done"  and  create  a  usable  & Self-­‐organizing  and  cross-­‐functional
One  person,  not  a  committee Only  one  PB  per  project,  even  if  multi  Scrum  teams potentially  releasable  product  Increment Have  all  skills  needed  to  accomplish  the  work
Scrum  Master  (SM) PO  tracks  total  work  left  every  SR  or  sooner During  Sprint: Definition  of  Done  (DoD)
Management  position  but  does  not  manage  ST Sprint  Backlog  (SB) >  No  changes  made  that  will  affect  Sprint  Goal Varies  per  Scrum  Team
Removes  impediments Forecast  by  DT  of  PBI's  to  be  done  for  next  Increment >  DT  composition  remains  constant  (Where  poss) Everyone  must  understand  what  'Done'  means
Servant  leader.  Facilitates  but  does  not  manage Evolves  during  the  Sprint >  Quality  goals  do  not  decrease When  Multi  Scrum  Teams  integrate  their  work  it  must
Development  Team  (DT) Only  DT  can  modify  SB  during  a  Sprint >  Scope  may  be  negotiated  between  PO  &  DT result  in  a  DoD  that  is  potentially  releasable
Cross-­‐functional  and  self-­‐managing.  Team  size  3-­‐9 DT  tracks  total  work  left  every  Daily  Scrum  or  sooner Only  PO  can  cancel  Sprint  before  time-­‐box  over Sprint  Goal
There  are  no  set  project  roles  within  the  team Increment New  Sprint  starts  immediately  after  end  prior  Sprint Defined  before  Sprint  Backlog  is  devised
Responsible  for  updating  work  estimate  during  Sprint Sum  of  all  PBI's  'done'  during  this  and  prior  Sprints Sprint  is  a  wrapper  around  all  events  below Objective  that  will  be  met  by  implementing  SB

Sprint  Planning  (SP) Daily  Scrum  (DS) Sprint  Review  (SR) Sprint  Retrospective  (SRet)
For  entire  Scrum  Team  (PO  optional  Pt  2) For  DT.  Held  same  place  &  time  to  reduce  complexity For  Scrum  Team  and  Stakeholders For  Scrum  Team
Time-­‐box:  8  hrs  (prop  less  for  shorter  Sprint) Time-­‐box:  15  minutes Time-­‐box:  4hrs  (prop  less  for  shorter  Sprints) Time-­‐box:  3  hrs  (prop  less  for  shorter  Sprints)
Divided  into  two  meetings,  each  50%  of  time-­‐box Team  update  each  other  on  three  questions: Collaborate  about  what  was  done  in  Sprint Inspect  for  improvements  to  be  made  for  next  Sprint
First  part  of  meeting:  What  will  be  delivered >  What  I  have  done  since  last  Daily  Scrum" Collaborate  on  the  next  things  that  could  be  done Adapt  'DoD'  as  req'd
Second  part  of  meeting:  How  it  will  be  delivered >  What  I  will  do  before  next  Daily  Scrum Results  in  revised  PB  &  probable  PBI's  for  next  Sprint
Plan  only  for  Sprint  and  not  for  entire  project >  Any  impediments  I  am  facing PO  Tracks  total  project  work  remaining

Other  Definitions Other  Notes: Sample  Burndown  Chart

Time-­‐box Scrum  does  not  have  a  role  called  "Project  Manager" nb:  The  Scrum  Guide  no  longer  contains  a  reference  to  Burndown  Charts  but  questions  still  exist  in  the  assessment
The  maximum  time  an  event  can  consume Scrum’s  roles,  artifacts,  events,  &  rules  are  immutable
Sprint  Backlog  Item  (SBI) Scrum  Teams  should  work  at  a  sustainable  pace
PBI  Chosen  by  DT  for  the  current  Sprint ie:  7  to  8  hours  per  day 300  
SBIs  are  owned  by  the  DT,  never  an  individual Planned   Actual  

Work  Remaining  
250  
Product  Backlog  Item  (PBI)
An  item  from  the  Product  Backlog 200  
Tend  to  be  larger  than  corresponding  SBIs 150  
Product  Backlog  grooming
Act  of  adding  detail,  estimates,  and  order  to  PBI's 100  
Done  by  PO  &  DT  usually  for  <=  10%  of  DT  capacity 50  
Estimating  (not  formal  part  of  Scrum  Guide)
Scrum  Teams  often  use  relative  sizing 0  
0   1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20  
Story  Points  are  often  used  rather  than  hours  or  days
Higher  ordered  PBIs  need  better  estimates Scrum.org  Open  Assessment  link Sprint  Number  
DT  is  responsible  for  all  estimates http://http://www.scrum.org/scrumopenassessment

This  document  is  provided  by  webgateinternational.com  to  aid  candidates  sitting  the  Professional  Scrum  Master  I  assessment  delivered  by  Scrum.org