Your SlideShare is downloading. ×
Deep dive into scrum meetings
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Deep dive into scrum meetings

1,492

Published on

These slides talk about the four Scrum Meetings: The SprintPlanning Meeting,The DailyScrum,The DailyScrum,The SprintRetrospective Meeting …

These slides talk about the four Scrum Meetings: The SprintPlanning Meeting,The DailyScrum,The DailyScrum,The SprintRetrospective Meeting
effective.

Published in: Technology, Sports
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,492
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
64
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. DEEP  DIVE  INTO  SCRUM  MEETINGS   By  Bachan  Anand   Prepared  by  Indu  Menon   Dial-in Number: +17759963560Room #: 699601 and press the # key.
  • 2. Agenda  •  Overview  of  Scrum  •  Mee7ngs  in  Scrum   – Sprint  Planning   – Daily  Scrum  or  Standup   – Sprint  Review   – Sprint  Retrospec7ve   Dial-in Number: +17759963560 Room #: 699601 and press the # key. h?p://agile.conscires.com/  
  • 3. Scrum  -­‐  Characteris7cs  •  Self-­‐organizing  teams  •  Product  progresses  in  a  series  of   sprints  •  Requirements  are  captured  as  items  in  a  list  of   product  backlog  •  No  specific  engineering  prac7ces  prescribed  •  Uses  genera7ve  rules  to  create  an  agile   environment  for  delivering  projects  •  One  of  the  Agile  Framework   h?p://agile.conscires.com/  
  • 4. The  Agile  Manifesto–a  statement  of  values   h?p://agile.conscires.com/  
  • 5. PuPng  it  all  together   Image  available  at   www.mountaingoatsoRware.com/scrum   h?p://agile.conscires.com/  
  • 6. Sprints  •  Scrum  projects  make  progress  in  a  series  of   sprints   – Analogous  to  Extreme  Programming  itera7ons  •  Typical  dura7on  is  2–4  weeks  or  a  calendar   month  at  most  •  A  constant  dura7on  leads  to  a  be?er  rhythm  •  Product  is  designed,  coded,  and  tested  during   the  sprint   h?p://agile.conscires.com/  
  • 7. No  changes  during  a  sprint   Change•  Plan  sprint  dura7ons  around  how  long  you  can   commit  to  keeping  change  out  of  the  sprint   h?p://agile.conscires.com/  
  • 8. Scrum  framework  Roles  •  roduct  owner   P•  crumMaster   S•  eam   T Ceremonies   •  print  planning   S •  print  review   S •  print  retrospec7ve   S •  aily  scrum  mee7ng   D Ar7facts   •  roduct  backlog   P •  print  backlog   S •  urndown  charts   B
  • 9. Scrum  framework  Roles  •  roduct  owner   P•  crumMaster   S•  eam   T Ceremonies   •  print  planning   S •  print  review   S •  print  retrospec7ve   S •  aily  scrum  mee7ng   D Ar7facts   •  roduct  backlog   P •  print  backlog   S •  urndown  charts   B
  • 10. Product  owner  •  Define  the  features  of  the  product  •  Decide  on  release  date  and  content  •  Be  responsible  for  the  profitability  of  the   product  (ROI)  •  Priori7ze  features  according  to  market  value    •  Adjust  features  and  priority  every  itera7on,   as  needed      •  Accept  or  reject  work  results  
  • 11. The  ScrumMaster   •  Represents  management  to  the  project   •  Responsible  for  enac7ng  Scrum  values  and   prac7ces   •  Removes  impediments     •  Ensure  that  the  team  is  fully  func7onal  and   produc7ve   •  Enable  close  coopera7on  across  all  roles  and   func7ons   •  Shield  the  team  from  external  interferences  
  • 12. The  team  •  Typically  5-­‐9  people  •  Cross-­‐func7onal:   – Programmers,  testers,  user  experience  designers,   etc.  •  Members  should  be  full-­‐7me   •  May  be  excep7ons  (e.g.,  database  administrator)   Dial-in Number: +17759963560 Room #: 699601 and press the # key.
  • 13. The  team  •  Teams  are  self-­‐organizing   – Ideally,  no  7tles  but  rarely  a  possibility  •  Membership  should  change  only  between   sprints   Dial-in Number: +17759963560 Room #: 699601 and press the # key.
  • 14. Mee7ngs  in  Scrum  •  Sprint  Planning  Mee7ng  •  Daily  Scrum  or  Standup  Mee7ng  •  Sprint  Review  Mee7ng  •  Sprint  Retrospec7ve  Mee7ng     Dial-in Number: +17759963560 Room #: 699601 and press the # key.
  • 15. Sprint  Planning  Mee>ng   Dial-in Number: +17759963560 Room #: 699601 and press the # key.
  • 16. Whats  it?  •  The  first  mee7ng  which  kick-­‐starts  a  team   into  the  Scrum  cycle   Dial-in Number: +17759963560 Room #: 699601 and press the # key. h?p://agile.conscires.com/  
  • 17. Why?  •  What  are  we  going  to  build?    •  How  are  we  going  to  build  it?   Dial-in Number: +17759963560 Room #: 699601 and press the # key. h?p://agile.conscires.com/  
  • 18. Who  A?ends?  •  Product  Owner  •   Scrum  Master  •  Team  •  Any  interested  and  appropriate  management   or  customer  representa7ves.     h?p://agile.conscires.com/  
  • 19. Technicali7es  •  Product  Owner  describes  highest  priority   features  to  the  Team    •  Team  decides  what  the  can  commit  to   delivering  in  the  Sprint  •  Sprint  backlog  is  created   – Tasks  are  iden7fied  and  each  is  es7mated   – Collabora7vely,  not  done  alone  by  the   ScrumMaster   h?p://agile.conscires.com/  
  • 20. Daily  Scrum  or  Stand  up  
  • 21. What  is  This  For?  •  Synchronize  the  various  team  members  •  Iden7fy  required  help  and  common  areas  of  work  •  Raise  Impediments  •  Not  used  as  a  problem-­‐solving  or  issue  resolu7on   mee7ng  •  The  Daily  Scrum  adds  value  –  it  is  not  a  spectacle   h?p://agile.conscires.com/  
  • 22. Who  A?ends?  •  The  Team   – Both  the  ScrumMaster  and  Product  Owner  are   commi?ed  team  members  •  Anyone  Else   – Others  can  a?end  but  cannot  speak  or  interfere   – Keep  a?endance  to  a  minimum   – Other  a?endees  must  follow  Scrum  rules   – Other  a?endees  stand  in  the  background,  not   with  the  team   h?p://agile.conscires.com/  
  • 23. The  Technicali7es  •  Same  7me  and  place  each  day   – Have  the  team  find  a  7me  which  best  suits  them   – No  tardiness  (one  minute  late  is  s7ll  late)   – 15  minute  7mebox  •  Only  Scrum  team  members  speak  •  Follow  the  three  mantras  (done,  to  be  done   and  impediments)   h?p://agile.conscires.com/  
  • 24. Ground  Rules  •  Come  prepared  •  Par7cipate,  ScrumMaster  enforces  par7cipa7on  •  Decide  but  don’t  discuss   – Parking  Lot  -­‐  Capture  items  for  discussion    •  Tackle  impediments  aggressively   h?p://agile.conscires.com/  
  • 25. Sprint  Review  Mee>ng   Dial-in Number: +17759963560 Room #: 699601 and press the # key.
  • 26. Why  do  Sprint  Reviews?  •  Visibility  •  Generate  feedback   – Gets  added  to  Product  Backlog  •  Discussion  •  Course  Correc7on   h?p://agile.conscires.com/  
  • 27. Whos  Coming?  •  Team  •  Product  Owner  or  Customers    •  Stakeholders  •  Invite  whole  world!   h?p://agile.conscires.com/  
  • 28. What  are  they  interested  in  seeing?  • Demos   – Of  stuff  that’s  done  and  poten7ally  release-­‐able  
  • 29. Ground  Rules  •  The  mee7ng  is  kept  very  informal.     – The  team  should  not  have  to  spend  7me   preparing  for  the  same  beyond  gePng  working   soRware  ready.  •  Not  allowed  -­‐  Powerpoints,  presenta7ons,   speeches,lectures   – Only  demonstrate  working  soEware.  •  The  prepara7on  [working  environment,   arranging  room]  -­‐done  by  the  Scrum  Master.   h?p://agile.conscires.com/  
  • 30. Sprint  Retrospec>ve  
  • 31. Whats  It?  •  Mee7ng  to  reflect  on  the  past  sprint  •  Not  a  survey  •  Team  ac7vity  •  Ask  and  Check   h?p://agile.conscires.com/  
  • 32. Why  is  it  necessary?  •  Opportunity  to  iden7fy  needs  from  inside  •  Catalysts  for  change  •  Generate  ac7ons  
  • 33. Whos  in  the  Retrospec7ve?  •  Team  •  ScrumMaster  •  Product  Owner  is  not  necessary  •  Management  should  not  a?end  
  • 34. Ground  Rules  •  No  Interrup7ons  •  No  raising  of  voice  or  tempo  •  Safety  check  •  Silent  zone   h?p://agile.conscires.com/  
  • 35. Summary  •  These  four  mee7ngs  of  Scrum   ...  provide  clarity  and  transparency  on  the  work   ...  help  clear  obstacles     ...  reinforces  team  bonding   ...  ensures  that  the  team  can  adapt  to  changes   easily   h?p://agile.conscires.com/  
  • 36. 1  Day  Training  in  India   •  When:  Nov  5,  2011  9AM  –6PM   IST   •  Where:  Times  of  India  Office,           M  G  Road,  Bangalore,  India   •  Register  here:    h?p:// agile.conscires.com/1-­‐day  agile-­‐ scrum-­‐training-­‐bangalore-­‐01/   •  Early  Bird  Discount:  Ends  Oct  21   •  Group  Discount:  Rs.1000/-­‐  off  on   regular  price  (Discount  per   person,  if  4  or  more  register)  
  • 37. h?p://agile.conscires.com/  
  • 38. h?p://agile.conscires.com/  
  • 39. QUESTIONS?   h?p://agile.conscires.com/  
  • 40. h?p://agile.conscires.com/  
  • 41. h?p://agile.conscires.com/  

×