Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.



Published on

Scrum: a new approach for agile product development

Published in: Education, Technology, Business
  • Be the first to comment

  • Be the first to like this


  1. 1. SCRUM!For Agile Product Developmentby: Anton Rifco <>Friday, 7 June, 13
  2. 2. Friday, 7 June, 13
  3. 3. Why Scrum?Because good product is what we really want. And, Great designand thick documentation is NOT the product.Because we don’t want to treat our documentation work as J.R.R.Tolkien treat his “The Hobbit” script.Our master piece is the working productFriday, 7 June, 13
  4. 4. Friday, 7 June, 13
  5. 5. How to Scrum?In Scrum, features are written in the perspective of end users.It’s known as User Stories.The collections of User Stories are called Product Backlog (or,Wish List)And it is the communication medium between business peopleand the development teamThe objective of the Software development activity is simply tofulfill that Wish List into working application.Friday, 7 June, 13
  6. 6. Roles in ScrumProduct Owner, confirms that the Product Backlog matchesthe requirement.Scrum Master, make sure the project is progressing smoothlyand facilitate the team members to finish their tasks. He is alsothe one that assigns User stories to team members.Team Member,Developers: realize and develop the assigned user stories.Testers: plan and execute the test strategy for user stories.Friday, 7 June, 13
  7. 7. Product Owner CustomersTeam MembersGandalf :)Friday, 7 June, 13
  8. 8. Release Planning Process (1)Identifies User stories from the Customer requirement, in thefollowing format:List of User stories is called Product Backlog.Friday, 7 June, 13
  9. 9. Release Planning Process (2)Identify User stories (from Product Backlog) that will beincluded in a particular release.Those chosen stories are called Release Backlog.Friday, 7 June, 13
  10. 10. Release Planning Process (3)Prioritize chosen User stories, break down into tasks andestimate the work to be done for each task.Tasks are estimated into the following choices:See... It’s Fibonacci! (because human tends to estimate better ifthere’s bigger gap for bigger denomination)•1 hour task•2 hours task•3 hours task•5 hours task•8 hours task•2 days task•3 days task•5 days taskFriday, 7 June, 13
  11. 11. Release Planning Process (4)•After we have the Release Backlog, separate the tasks into fewchunks (2 or 3) to make few sprints.•Each sprint is a short duration milestone to get into a shipready state, e.g. every one week sprint.•Each sprint contains homogenous or interdependent tasks.Friday, 7 June, 13
  12. 12. Release Planning Process (5)•Note: Late in Sprint is an indication that the product release willnot be on schedule.•Therefore, it’s important to track Sprint. Burndown chartprovides the day-by-day measure of the amount of works thatremain in a given sprint.Friday, 7 June, 13
  13. 13. Release Planning Process (6)•Using the chart, we can measure the Burndown Velocity to keeptrack of the sprint.•It’s the average productivity each day. From this velocity, teamcan decide whether or not to pace up (adjust) the developmentefforts in order to meet the deadline.Friday, 7 June, 13
  14. 14. Release Planning Process (7)•Each completing a Sprint, there will be a Sprint Retrospectivemeeting.•It’s to analyze what went right and what went wrong and what canbe improved for the next sprint.•Discussion should be objective (not subjective), meaning that itshould focus on the tasks rather than complaining about theperson that worked on them.Friday, 7 June, 13
  15. 15. Release Planning Process (7)•Project is considered done, after all Product Backlog User storiesare finished through few Sprint delivery.•Note: In scrum, it’s important to define the Definition of Done(DoD) within a team. It can be task fully developed, or fullydeveloped and tested, or fully developed and tested anddeployed. It’s up to your team, mate!Friday, 7 June, 13
  16. 16. Friday, 7 June, 13
  17. 17. Daily Scrum•A daily Stand-up meeting (usually in the morning) to haveinformation flows freely within team member.•Each team member will quickly list all the items that have beendone since the last meeting and describe any obstacle in theirway (it’s to allow discussion to tackle the obstacle)•It’s not mandatory to explain what someone will do until thenext Daily stand-up, although it’s commonly used.Friday, 7 June, 13
  18. 18. and thejourneybegins.Friday, 7 June, 13
  19. 19. Good ReferencesThe Elements of Scrum, a book by Chris Sims & Hillary LouseJohnsonThe Scrum Framework in 30 Seconds, an article in to Agile Scrum in Under 10 Minutes, a video in, 7 June, 13