Scrum For Developers


Published on

A session on what a developer needs to know when applying to a company where the PM says "we work with Scrum"

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

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

No notes for slide
  • Scrum For Developers

    1. 1. SCRUM FOR DEVELOPERS <ul><li>Mohamed Ahmed Meligy </li></ul><ul><li>Senior Software Engineer </li></ul><ul><li>SilverKey Technologies, LLC </li></ul><ul><li> </li></ul>
    2. 2. Project Management Methodologies You heard about them in collage
    3. 3. Waterfall Model
    4. 4. Does it work ??? Who goes home at 5 PM ? Why did Windows Vista take 5 years ?
    5. 5. Every Project Story <ul><li>The customer knows nothing </li></ul><ul><li>The developer thinks about new technologies </li></ul><ul><li>The PM thinks about the deadline </li></ul><ul><li>The analyst thinks he knows everything </li></ul><ul><ul><li>He got “everything” from the customer, who knows “nothing” ;-) </li></ul></ul>
    6. 6. Every Project Story <ul><li>The developer: “I can do it in 3 months ” </li></ul><ul><li>The PM: “You’ll do it in 2 months ” </li></ul><ul><li>The project takes 4-5 month </li></ul>
    7. 7. Every Project Story <ul><li>1 st Month: Everybody is happy </li></ul><ul><li>2 nd Month: Customer sees “something” </li></ul><ul><li>3 rd Month: Customer makes tons of changes </li></ul><ul><ul><li>The developer screams </li></ul></ul><ul><ul><li>The project manager blames …. ??? </li></ul></ul><ul><li>Last Month: Everybody is at office t ill 8-10 PM </li></ul><ul><li>Every DAY: </li></ul><ul><ul><li>The PM: Developer, you’re not done yet? LOSER!! </li></ul></ul>
    8. 8. Why does it happen? <ul><li>Requirements are not fully understood at the beginning of the process. </li></ul><ul><li>Requirements change during the process . </li></ul><ul><li>The process becomes unpredictable when new tools and technologies are used. </li></ul>
    9. 9. Other Methodologies <ul><li>Spiral </li></ul><ul><li>CMMI </li></ul><ul><li>Rational Rose </li></ul><ul><li>Agile </li></ul>
    10. 10. Agile Who’s this ???
    11. 11. Agile Manifesto <ul><li>Individuals and interactions </li></ul><ul><ul><li>Over processes and tools </li></ul></ul><ul><li>Working software </li></ul><ul><ul><li>Over comprehensive documentation </li></ul></ul><ul><li>Customer collaboration </li></ul><ul><ul><li>Over contract negotiation </li></ul></ul><ul><li>Responding to change </li></ul><ul><ul><li>O ver following a plan </li></ul></ul>
    12. 12. Agile Methodologies <ul><li>eXtreme Programming (XP) </li></ul><ul><ul><li>Pair Programming </li></ul></ul><ul><ul><li>Test Driven Development </li></ul></ul><ul><ul><li>Continuous Integration </li></ul></ul><ul><ul><li>Refactoring, Coding Standards, etc… </li></ul></ul><ul><li>Adaptive Software Development </li></ul><ul><ul><li>speculate, collaborate, and learn cycles </li></ul></ul><ul><li>Scrum </li></ul>
    13. 13. SCRUM??
    14. 14. Scrum Model 2-4 weeks 7-8 hours Product Backlog As prioritized by Product Owner Sprint Backlog Backlog tasks expanded by team Potentially Shippable Product Increment Daily Scrum Meeting Source: Adapted from “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle.
    15. 15. Prerequisites <ul><li>Small Team </li></ul><ul><li>Good People </li></ul><ul><li>Common Sense </li></ul>
    16. 16. Product Backlog List of work items during the entire project
    17. 17. Sprint A certain period of time with specific deliverables Lasts for 2-4 weeks – NO MORE NO LESS
    18. 18. Sprint <ul><li>Before Start: Sprint Planning </li></ul><ul><li>Starts with Sprint Backlog </li></ul><ul><ul><li>Choose highest priority items remaining in product backlog </li></ul></ul><ul><li>Ends with Deliverables </li></ul><ul><ul><li>New Features Developed / Old Bugs Fixed </li></ul></ul><ul><ul><li>Sprint Zero and Sprint One might deliver documents ! </li></ul></ul><ul><ul><ul><li>Architecture Documents </li></ul></ul></ul><ul><ul><ul><li>UI Prototype </li></ul></ul></ul><ul><li>After End: Sprint Review </li></ul><ul><ul><li>Usually just before next sprint planning </li></ul></ul>
    19. 19. Sprint Daily Meetings What did you do Yesterday ? What will you do today ? Do you have any problems ?
    20. 20. Sprint Daily Meetings <ul><li>Stand up Meetings </li></ul><ul><li>15 Minutes Max. </li></ul><ul><ul><li>Well, don’t exceed 30 minutes at least </li></ul></ul><ul><li>Entire Team </li></ul>
    21. 21. Scrum Roles Product Owner Scrum Master Project Team
    22. 22. Scrum Roles: Product Owner <ul><li>Possibly a Product Manager or Project Sponsor </li></ul><ul><ul><li>That’s what we call an “analyst” </li></ul></ul><ul><li>Marketing </li></ul><ul><li>Internal Customer </li></ul><ul><li>etc. </li></ul><ul><ul><li>Not a technical guy, BUT …. </li></ul></ul>
    23. 23. Scrum Roles: Scrum Master <ul><li>Responsible for enacting Scrum values and practices </li></ul><ul><ul><li>Manages the sprint meeting </li></ul></ul><ul><ul><li>Does the sprint reporting </li></ul></ul><ul><li>Typically a Project Manager or Team Leader </li></ul><ul><ul><li>That’s what the books say </li></ul></ul><ul><ul><li>I have played it a different way </li></ul></ul>
    24. 24. Scrum Roles: Project Team <ul><li>Cross-functional </li></ul><ul><ul><li>QA </li></ul></ul><ul><ul><li>Developers </li></ul></ul><ul><ul><li>UI Designers </li></ul></ul><ul><ul><li>etc </li></ul></ul><ul><li>5-10 members (as the books say) </li></ul><ul><ul><li>I’d rather 5 to 7 MAX per team </li></ul></ul>
    25. 25. Scrum Artifacts Product Backlog Sprint Backlog Burndown Chart
    26. 26. Burndown Chart
    27. 27. SCRUM AND YOU <ul><li>The Developer </li></ul>
    28. 28. Self Management 50% for managing yourself 25% for managing your boss 25% for managing everybody else (Dee Hock – Founder of VISA)
    29. 29. Accept Flexible Deliverables As this means flexible schedule Try not to hate the customer :-D
    30. 30. Be Reliable You are a good guy / gal ;-) Common Sense
    31. 31. Be Reliable You’ll make mistakes APOLOGIZE
    32. 32. Take Care You have your good day and bad day You have your productive and your slow weeks
    33. 33. Take Care Do NOT extend a sprint period Do I have the choice??
    34. 34. The Real World Reality has a tendency to make a beautiful project plan ugly
    35. 35. Problems! There’s no silver bullet
    36. 36. Where to go <ul><li> </li></ul><ul><li> </li></ul><ul><li>My weblog </li></ul><ul><ul><li> </li></ul></ul>Ken Schwaber, 2004 ISBN 073561993X