The document discusses the challenges in project management, particularly emphasizing the shortcomings of traditional methodologies like the waterfall model and the benefits of agile practices such as Scrum. It describes the roles within Scrum, including the Product Owner, Scrum Master, and the project team, along with the artifacts produced during sprints. The text highlights the importance of adaptability, self-management, and effective communication among team members to achieve successful project outcomes.

1. SCRUM FOR DEVELOPERS Mohamed Ahmed Meligy Senior Software Engineer SilverKey Technologies, LLC weblogs.asp.net/meligy

2. Project Management Methodologies You heard about them in collage

3. Waterfall Model

4. Does it work ??? Who goes home at 5 PM ? Why did Windows Vista take 5 years ?

5. Every Project Story The customer knows nothing The developer thinks about new technologies The PM thinks about the deadline The analyst thinks he knows everything He got “everything” from the customer, who knows “nothing” ;-)

6. Every Project Story The developer: “I can do it in 3 months ” The PM: “You’ll do it in 2 months ” The project takes 4-5 month

7. Every Project Story 1 st Month: Everybody is happy 2 nd Month: Customer sees “something” 3 rd Month: Customer makes tons of changes The developer screams The project manager blames …. ??? Last Month: Everybody is at office t ill 8-10 PM Every DAY: The PM: Developer, you’re not done yet? LOSER!!

8. Why does it happen? Requirements are not fully understood at the beginning of the process. Requirements change during the process . The process becomes unpredictable when new tools and technologies are used.

9. Other Methodologies Spiral CMMI Rational Rose Agile

10. Agile Who’s this ???

11. Agile Manifesto Individuals and interactions Over processes and tools Working software Over comprehensive documentation Customer collaboration Over contract negotiation Responding to change O ver following a plan

12. Agile Methodologies eXtreme Programming (XP) Pair Programming Test Driven Development Continuous Integration Refactoring, Coding Standards, etc… Adaptive Software Development speculate, collaborate, and learn cycles Scrum

13. SCRUM??

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. Prerequisites Small Team Good People Common Sense

16. Product Backlog List of work items during the entire project

17. Sprint A certain period of time with specific deliverables Lasts for 2-4 weeks – NO MORE NO LESS

18. Sprint Before Start: Sprint Planning Starts with Sprint Backlog Choose highest priority items remaining in product backlog Ends with Deliverables New Features Developed / Old Bugs Fixed Sprint Zero and Sprint One might deliver documents ! Architecture Documents UI Prototype After End: Sprint Review Usually just before next sprint planning

19. Sprint Daily Meetings What did you do Yesterday ? What will you do today ? Do you have any problems ?

20. Sprint Daily Meetings Stand up Meetings 15 Minutes Max. Well, don’t exceed 30 minutes at least Entire Team

21. Scrum Roles Product Owner Scrum Master Project Team

22. Scrum Roles: Product Owner Possibly a Product Manager or Project Sponsor That’s what we call an “analyst” Marketing Internal Customer etc. Not a technical guy, BUT ….

23. Scrum Roles: Scrum Master Responsible for enacting Scrum values and practices Manages the sprint meeting Does the sprint reporting Typically a Project Manager or Team Leader That’s what the books say I have played it a different way

24. Scrum Roles: Project Team Cross-functional QA Developers UI Designers etc 5-10 members (as the books say) I’d rather 5 to 7 MAX per team

25. Scrum Artifacts Product Backlog Sprint Backlog Burndown Chart

26. Burndown Chart

27. SCRUM AND YOU The Developer

28. Self Management 50% for managing yourself 25% for managing your boss 25% for managing everybody else (Dee Hock – Founder of VISA)

29. Accept Flexible Deliverables As this means flexible schedule Try not to hate the customer :-D

30. Be Reliable You are a good guy / gal ;-) Common Sense

31. Be Reliable You’ll make mistakes APOLOGIZE

32. Take Care You have your good day and bad day You have your productive and your slow weeks

33. Take Care Do NOT extend a sprint period Do I have the choice??

34. The Real World Reality has a tendency to make a beautiful project plan ugly

35. Problems! There’s no silver bullet

36. Where to go www.controlchaos.com www.scrumalliance.org My weblog weblogs.asp.net/meligy Ken Schwaber, 2004 ISBN 073561993X