Scrum agile process

Click here to load reader

  • date post

  • Category


  • view

  • download


Embed Size (px)


Scrum process presented by [email protected]

Transcript of Scrum agile process

  • 1. MANAGE YOUR PROJECT DIFFERENTLY Trnh Minh Cng [email protected] [email protected]
  • 2. WHAT IS THIS ? [email protected]
  • 3. I HAVE A DREAM My project o In Time o Within Budget o Meet Requirements Members in my team o Creative & responsive o Not exhausted and not leave team [email protected]
  • 4. Project Management Triangle SCOPE COST TIME [email protected]
  • 5. Typical developer Personal interest is more than team interest Warm up time is long Good at patching but bad at designing (problem solving style) Wait for thing happens but not make thing happen [email protected]
  • 6. Waterfall Analysis Design Develop Test Deploy [email protected]
  • 7. Parkinsons Law Work expands so as to fill the time available for its completion [email protected]
  • 8. Dont assign one week task, Break it into smaller sub tasks ! Gantt chart gets bigger & bigger. No one can read Gantt chart [email protected]
  • 9. Waterfall is easy to understand but it is not effective in real [email protected]
  • 10. WHAT SCRUM CAN HELP? [email protected]
  • 11. Agile Methodologies [email protected]
  • 12. Scrum is an Agile framework Scrum is an iterative, incremental framework for project management and agile software development. Agile is a group of software development methodologies based on iterative and incremental development [email protected]
  • 13. Agile Analysis Design Develop Test Deploy [email protected]
  • 14. Agile Analysis Design Test Develop Deploy Analysis Design Test Develop Deploy Analysis Design Test Develop Deploy ! ? ? ! [email protected]
  • 15. Principles of Agile #1 Deliver valuable software early & continuously Accommodate changes Collaborate with customer or customer proxy Motivate individuals Self-organizing teams Self tuning [email protected]
  • 16. Principles of Agile #2 Enforce effective & transparent communication Measure of progress by working software delivered. Highlight amount of work not done Maintain a development speed Promote technical excellent and good design [email protected]
  • 17. DIFFERENCES Plan Driven Scrum Hierarchy team Self organizing team Lot of document Deliver features Follow plan Response to change Structure Flexible Gantt Chart Burn down chart [email protected]
  • 18. Roles in Scrum Scrum Master Scrum Team Product Owner Stakeholders & Users [email protected]
  • 19. 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 [email protected]
  • 20. The Scrum Master Manage project Enforce Scrum values and practices Help team to focus on tasks Enable close cooperation across all roles and functions Shield the team from external interferences [email protected]
  • 21. The team Typically 5-9 people Cross-functional: Programmers, testers, user experience designers, etc. Teams are self-organizing Ideally, no titles but rarely a possibility Membership should change only between sprints [email protected]
  • 22. MResources = More Velocity? 8 16 12 24 16 [email protected]
  • 23. Scrum of Scrums [email protected]
  • 24. 6 Artifacts Product Vision Product Backlog Release Plan Sprint Backlog Sprint Burndown Impediment List [email protected]
  • 25. Product Sprint Backlog [email protected]
  • 26. Product vs Sprint Backlog Product BackLog Sprint BackLog Level of detail Less detailed Very detailed Item User Story Task Estimation Units Story Points Hours Doc owner Product Owner Team Revised Weekly Daily Duration Project Sprint Workbook Product Backlog Iteration Backlog [email protected]
  • 27. Project Planning Product Backlog 3 Sprint 1 3 1 Product Release 1 3 Backlog Sprint 2 1 3 3 Sprint 3 2 3 3 Release 2 Release Plan Sprint 4 5 Sprint 5 8 [email protected]
  • 28. User Story Independent Negotiable User Story Valuable Task 1 Task 2 Task 3 Estimatable Small Testable As a I need to In order to [email protected]
  • 29. User Story User Story == Use Case MosCow: Must Should Could Wouldnt Write non-functional requirements as user stories Estimate Story Point estimate-points-story-points-and-how-to-measure-them- in-scrum [email protected]
  • 30. Meetings in SCRUM Meeting Purpose Duration Frequency Sprint Determine what work to do in 2 hours per Once per Planning the coming sprint. week sprint Daily Allow team members to 15 minutes Daily Scrum commit, collaborate, and communicate risks. Sprint Show the customer and other 2 hours per Once per Review stakeholders the work that the week sprint team accomplished in the