Agile Scrum - AUB 2014


Published on

Intro about agile methodologies and a comparaison with the traditional SDLC, this presentation is about Agile Scrum.
The presentation covers the scrum process, the roles, the ceremonies and the artifacts in addition to how do we scale scrum into more than one team.

Published in: Software, Technology, 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
  • Temporary means having a definite beginning and end. The end is reached when the project’s objectives have been achieved or if the project is terminated for any reason.Temporary does not mean short in nature, and it could well be a 10 years project – for example, sending a man to moon, Building the AUB CampusAn ongoing work effort is generally a repetitive process because it follows an organization’s existing procedures. The ongoing execution of activities that produce the same result or product repetitively is what Operations is all about.
  • Predictive teams in the traditional SDLC models usually work with detailed planning and have a complete forecast of the exact tasks and features to be delivered in the next few months or during the product life cycle.No - the backward scalability - The flexibility to error check under any part of the development stage - hard to adapt to changes
  • Agile is based on the adaptive software development methods where as the traditional SDLC models like waterfall model is based on predictive approach.Agile uses adaptive approach where there is no detailed planning and there is clarity on future tasks only in respect of what features need to be developed.
  • Agile Scrum - AUB 2014

    1. 1. Agile Scrum Hasan Jaffal Head of Project Management Office at ArabiaGIS
    2. 2. Agenda What’s A Project? The Traditional SDLC The Agile Way Agile Scrum
    3. 3. What’s A Project?  PROJECT: According to the PMBOK Guide, Fifth Edition, a Project is a temporary endeavor undertaken to create a unique product, service or result  NOT PROJECT: An ongoing and repetitive work
    4. 4. What’s A Project? Always has a start and end date Produces a unique product, service or result Project Ongoing process of functions Always produces the same product, service, or result Operation
    5. 5. Operations or Projects ?
    6. 6. Traditional SDLC Specify Design Code Test Ship
    7. 7. Agile Development
    8. 8. Agile Methodologies  It’s a method for developing products using short iterations  Each iteration is like a short project in itself  Uses “inspect and adapt” practices to adjust the project plan  It focuses on adding features in a value prioritized way, rather than a resource prioritized way  Agile doesn’t solve problems!
    9. 9. What Are the Agile Methodologies?  Scrum  Kanban  XP  Lean  …
    10. 10. The Agile Manifesto–a statement of values Process and tools Individuals and interactions over Following a planResponding to change over Comprehensive documentation Working software over Contract negotiationCustomer collaboration over
    11. 11. Scrum has been used by •Microsoft •Yahoo •Google •Electronic Arts •High Moon Studios •Lockheed Martin •Philips •Siemens •Nokia •Capital One •BBC •Intuit •Intuit •Nielsen Media •First American Real Estate •BMC Software •Ipswitch •John Deere •Lexis Nexis •Sabre • •Time Warner •Turner Broadcasting •Oce
    12. 12. Agile Scrum Deliver Faster
    13. 13. Agile Scrum Agenda  The Scrum Process  The Scrum Roles  Product backlog  Sprints  Sprint Planning  Sprint Review  Retrospective  Daily Scrum  Sprint burndown chart  Scrum Scalability
    14. 14. The “Scrum” Process Sprint Review Product Backlog Sprint Backlog Potentially Shippable Increment 1 - 4 Weeks 24 Hours
    15. 15. Scrum Cancel Gift wrap Return Sprint 2-4 weeks Return Sprint goal Sprint backlog Potentially shippable product increment Product backlog CouponsGift wrap Coupons Cancel 24 hours
    16. 16. Scrum framework •Product owner •ScrumMaster •Team Roles •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Ceremonies •Product backlog •Sprint backlog •Burndown charts Artifacts
    17. 17. The Scrum Roles  Product owner  ScrumMaster  Team
    18. 18. Product owner  Define the features of the product  Decide on release date and content  Be responsible for the profitability of the product (ROI)  Prioritize features according to market value  Adjust features and priority every iteration, as needed  Accept or reject work results
    19. 19. The ScrumMaster  Represents management to the project  Responsible for enacting Scrum values and practices  Removes impediments  Ensure that the team is fully functional and productive  Enable close cooperation across all roles and functions  Shield the team from external interferences
    20. 20. The team  Typically 5-9 people  Cross-functional:  Programmers, testers, user experience designers, etc.  Members should be full-time  May be exceptions (e.g., database administrator)
    21. 21. The team  Teams are self-organizing  Ideally, no titles but rarely a possibility  Membership should change only between sprints
    22. 22. Product backlog  The requirements  A list of all desired work on the project  Ideally expressed such that each item has value to the users or customers of the product  Prioritized by the product owner  Reprioritized at the start of each sprint This is the product backlog
    23. 23. A sample product backlog Backlog item Estimate Allow a guest to make a reservation 3 As a guest, I want to cancel a reservation. 5 As a guest, I want to change the dates of a reservation. 3 As a hotel employee, I can run RevPAR reports (revenue-per-available-room) 8 Improve exception handling 8 ... 30 ... 50
    24. 24. What is a User Story  Should be focused on the user  Simple and clear  Prioritized  User Story Template “As a <user role>, I want <goal> so that <reason>.”
    25. 25. Sample Stories
    26. 26. Sprints  Scrum projects make progress in a series of “sprints”  Typical duration is 2–4 weeks or a calendar month at most  A constant duration leads to a better rhythm  Product is designed, coded, and tested during the sprint
    27. 27. Sprint planning meeting Sprint prioritization • Analyze and evaluate product backlog • Select sprint goal Sprint planning • Decide how to achieve sprint goal (design) • Create sprint backlog (tasks) from product backlog items (user stories / features) • Estimate sprint backlog in hours Sprint goal Sprint backlog Business conditions Team capacity Product backlog Technology Current product
    28. 28. Sprint planning  Team selects items from the product backlog they can commit to completing  Sprint backlog is created  Tasks are identified and each is estimated (1-16 hours)  Collaboratively, not done alone by the ScrumMaster  High-level design is considered As a vacation planner, I want to see photos of the hotels. Code the middle tier (8 hours) Code the user interface (4) Write test (4) Code the class (6) Update performance tests (4)
    29. 29. The sprint goal  A short statement of what the work will be focused on during the sprint Life Sciences Support features necessary for population genetics studies. Financial services Support more technical indicators than company ABC with real- time, streaming data. Database Application Make the application run on SQL Server in addition to Oracle.
    30. 30. Managing the sprint backlog  Individuals sign up for work of their own choosing  Work is never assigned  Estimated work remaining is updated daily
    31. 31. Managing the sprint backlog  Any team member can add, delete or change the sprint backlog  Work for the sprint emerges  If work is unclear, define a sprint backlog item with a larger amount of time and break it down later  Update work remaining as more becomes known
    32. 32. A sprint backlog Tasks Code the user interface Code the middle tier Test the middle tier Write online help Write the foo class Mon 8 16 8 12 8 Tues 4 12 16 8 Wed Thur 4 11 8 4 Fri 8 8 Add error logging 8 10 16 8 8
    33. 33. No changes during a sprint  Plan sprint durations around how long you can commit to keeping change out of the sprint Change
    34. 34. The sprint review  Team presents what it accomplished during the sprint  Typically takes the form of a demo of new features or underlying architecture  Informal  Whole team participates  Invite the world
    35. 35. Sprint retrospective  Periodically take a look at what is and is not working  Typically 15–30 minutes  Done after every sprint  Whole team participates  ScrumMaster  Product owner  Team  Possibly customers and others
    36. 36. The daily scrum  Parameters  Daily  15-minutes  Stand-up  Not for problem solving  Whole world is invited  Only team members, ScrumMaster, product owner, can talk  Helps avoid other unnecessary meetings
    37. 37. Everyone answers 3 questions  These are not status for the ScrumMaster  They are commitments in front of peers What did you do yesterday? 1 What will you do today? 2 Is anything in your way? 3
    38. 38. A sprint burndown chart Hours
    39. 39. Hours 40 30 20 10 0 Mon Tue Wed Thu Fri Tasks Code the user interface Code the middle tier Test the middle tier Write online help Mon 8 16 8 12 Tues Wed Thur Fri 4 12 16 7 11 8 10 16 8 50
    40. 40. Scalability  Typical individual team is 7 ± 2 people  Scalability comes from teams of teams  Scrum has been used on multiple 500+ person projects
    41. 41. Scaling through the Scrum of scrums
    42. 42. Scrum of scrums of scrums
    43. 43. Where to go next  Some of the slides of this presentation are created by   
    44. 44. Copyright notice  You are free:  to Share―to copy, distribute and and transmit the work  to Remix―to adapt the work  Under the following conditions  Attribution. You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).  Nothing in this license impairs or restricts the author’s moral rights.  For more information see
    45. 45. Thank you @JafTalks