Brief intro to SCRUM


Published on

A short description to developing software projects using Scrum agile methodology.

Published in: Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Brief intro to SCRUM

  1. 1. SCRUM or a meal at “Ham and Eggs” by Vladimir Vassilev
  2. 2. What will you learn? <ul><li>Product backlog </li></ul><ul><li>Sprint backlog </li></ul><ul><li>Product burndown chart </li></ul><ul><li>Sprint burndown chart </li></ul><ul><li>Product owner </li></ul><ul><li>SCRUM master </li></ul><ul><li>SCRUM team </li></ul><ul><li>Sprint planning meeting </li></ul><ul><li>Sprint review meeting </li></ul><ul><li>Scrum (stand-up) meeting </li></ul><ul><li>Time-boxing </li></ul>
  3. 3. Process description Used under
  4. 4. Pig roles <ul><li>SCRUM master </li></ul><ul><ul><li>responsible for the SCRUM process </li></ul></ul><ul><ul><li>leads the SCRUM meeting. </li></ul></ul><ul><ul><li>organizes the sprint backlog. </li></ul></ul><ul><ul><li>major actor in sprint planning and preview meetings. </li></ul></ul><ul><li>SCRUM team </li></ul><ul><ul><li>responsible for the development process (developers, designers, analysts) </li></ul></ul><ul><li>Product owner </li></ul><ul><ul><li>the voice of the customer. </li></ul></ul><ul><ul><li>sets up the Product backlog. </li></ul></ul><ul><ul><li>major actor in the Sprint planning meeting. </li></ul></ul>
  5. 5. Chicken roles <ul><li>Users </li></ul><ul><li>Stakeholders </li></ul><ul><ul><li>People directly interested in the development of the product </li></ul></ul><ul><li>Consulting experts </li></ul><ul><li>… and others not taking part in the development process. </li></ul>
  6. 6. Documents <ul><li>Product backlog </li></ul><ul><ul><li>broad descriptions of all required features, by the Product owner. </li></ul></ul><ul><ul><li>priorities by the Product owner. </li></ul></ul><ul><ul><li>time estimation for each feature. </li></ul></ul><ul><li>Sprint backlog </li></ul><ul><ul><li>broken down features into tasks by the SCRUM master. </li></ul></ul><ul><ul><li>SCRUM members select and estimate tasks. </li></ul></ul><ul><ul><li>Every day each member estimates the effort left for finishing the tasks that are distributed to them. </li></ul></ul> <ul><li>Product burndown chart </li></ul><ul><li>shows the progress and effort left for the development of the product through the defined Sprints (Iterations). </li></ul><ul><li>Sprint burndown chart </li></ul><ul><li>the remaining effort till the end of the Sprint (Iteration) </li></ul>
  7. 7. Sprint meetings <ul><li>Sprint planning meeting </li></ul><ul><li>at the beginning of a Sprint. </li></ul><ul><li>Participants are the Pigs (Product owner, SCRUM master, the entire SCRUM team). </li></ul><ul><li>The Product owner selects the highest priority features. </li></ul><ul><li>The SCRUM master brakes each feature into tasks. </li></ul><ul><li>The SCRUM team distributes the tasks among the members. </li></ul><ul><li>The Master and the Team discuss and estimate the time needed for each task. </li></ul> <ul><li>Sprint review meeting </li></ul><ul><li>at the end of a Sprint. </li></ul><ul><li>Participants are the Pigs + management, customers, and engineers from other projects. </li></ul><ul><li>takes the form of a demo of the new features. </li></ul><ul><li>intentionally kept very informal (not to become a distraction for the development process) </li></ul><ul><li>no presentations allowed </li></ul><ul><li>a natural end of the sprint </li></ul>
  8. 8. Stand-up meeting <ul><li>Stand-up meetings </li></ul><ul><ul><li>intended to be quick, not consuming time </li></ul></ul><ul><ul><li>… but giving information for the current state of the Sprint and changes in Sprint end date </li></ul></ul><ul><ul><li>answer the questions: </li></ul></ul><ul><ul><ul><li>What have you done since yesterday? </li></ul></ul></ul><ul><ul><ul><li>What are you planning to do by tomorrow? </li></ul></ul></ul><ul><ul><ul><li>Do you have any problems preventing you from accomplishing your goal? </li></ul></ul></ul><ul><ul><li>time-boxing is vital for the effective stand-up meeting – each member of the SCRUM team has strictly limited time for answering the three questions </li></ul></ul>
  9. 9. Process description (once again!) Used under
  10. 10. What was that about the pigs and chicken?! <ul><li>There was the story of a chicken and a pig walking down the street… </li></ul><ul><li>The Chicken said: </li></ul><ul><li>- Why don’t we open a restaurant? </li></ul><ul><li>- Why not? – agreed the Chicken. </li></ul><ul><li>- But how should we call it? </li></ul><ul><li>- “Ham and Eggs” sounds nice to me! – answered the Chicken. </li></ul><ul><li>… SCRUM is that restaurant. Pigs are those, committed to the project, whereas Chicken are only involved. Only Pigs have the right to speak at the Stand-up meeting. </li></ul>
  11. 11. Thanks for staying awake! <ul><li>Author: </li></ul><ul><li>Vladimir Vassilev </li></ul><ul><li>Contacts: </li></ul><ul><li>[email_address] </li></ul><ul><li>(+359)885 44 84 75 </li></ul><ul><li>286-711-630 </li></ul><ul><li>Position: </li></ul><ul><li>init Lab's captain </li></ul><ul><li>init Lab @ StartUP </li></ul><ul><li> </li></ul><ul><li>[email_address] </li></ul><ul><li>(+359) 885 44 84 75 </li></ul>