Scrum - Agile Methodology
•
34 recomendaciones•5,300 vistas
Introduction to the scrum framework: roles, activities and artifacts. Scrum is an agile methodology for project management, to create a high quality product. www.nieldeckx.be
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (20)
Similar a Scrum - Agile Methodology
Similar a Scrum - Agile Methodology (20)
Último
Último (20)
Scrum - Agile Methodology
- 1. NIEL DECKX Freelance iOS Developer Certified ScrumMaster Certified Product Owner www.nieldeckx.be
- 2. HAVE A DECENT PROCESS WHEN CREATING A PRODUCT What’s the main goal?
- 3. HAVE A DECENT PROCESS WHEN CREATING A PRODUCT What’s the main goal? Why? CREATETHE BEST PRODUCT
- 4. SUMMARY - Waterfall -The Agile Manifesto - SCRUM Principles - SCRUM Framework - Roles &Team - Artefacts - Activities
- 5. WATERFALL
- 8. PUSH SYSTEM Input Capacity Delivery overwhelm capacity creating waste and delay
- 9. QUALITY Scope BudgetTime Quality If budget, time and scope are fixed, quality will vary.
- 11. Individuals and Interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- 12. BE AGILE -Team and collaboration - Incremental - Iterative -Value driven - Frequent delivery - Product quality - Inspect and adapt - Self-organisation
- 13. SCRUM PRINCIPLES
- 16. VALUE DRIVEN CONSTRAINTS: ESTIMATES: Scope Time Budget Quality
- 17. PRIORITIZATION MoSCoW Must Have Should Have Could Have Won’t Have Out of scope Buffer In scope
- 18. BENEFITS for business - Quicker ROI - LowerTotal Cost - Respond to Change - Reduce Risk - FasterTime to Market - Stakeholder Relations
- 19. BENEFITS for development -Teaming - A Sense of Done - Quality Work - Rhythm -Visible Progress - Feedback and Iteration
- 20. SCRUM FRAMEWORK Roles,Artefacts and Activities
- 21. ROLES &TEAM - Product Owner - Scrum Master - DevelopmentTeam
- 22. SCRUM TEAM MEMBER a good is focussed has respect for others has courage is committed is open
- 23. 5 - 9 members TEAM Self-organising Cross functional SCRUMTEAM
- 24. - Represents customers and stakeholders - Maximise product value -Track time and budget - Manage product backlog PRODUCT OWNER
- 25. - Bring up impediments - Resolve impediments - Support the Scrum team in implementing Scrum SCRUM MASTER
- 26. - Cross functional - Accomplishing the Sprint goal - Delivers a product increment DEVELOPMENTTEAM
- 27. Scrum MasterProduct Owner DevelopmentTeam Select Features Product Increment Discuss Work on Features Supports ScrumTeam
- 28. ARTIFACTS - Product Backlog - Sprint Backlog - Product Increment - Definition of Done - Progress Monitors
- 29. PRODUCT BACKLOG User Story User Story User Story Epic Story Epic Story
- 30. STORY FORMAT AS A … I WANTTO … SOTHAT … Who? What? Why? User role Action Business goal
- 31. STORY Acts as - Requirement - Planning item - Reminder - Conversation trigger - Shared understanding
- 32. EPIC STORY - Must be split in user stories - Stories which do not satisfy INVEST criteria
- 33. INVEST CRITERIA Independent Negotiable Valuable Estimable Small Testable Can deliver value by itself Details can be worked out by conversation Value to the user is clear Team understands it well to estimate Fits in a sprint Clear test criteria
- 34. PRODUCT BACKLOG Bug User Story User Story Epic Story Epic Story Refactoring
- 35. - Prioritised set of estimated items - Constantly in change as the situation changes - Contains stories, bugs, refactorings, … - Detailed appropriately - Source of work for the Development team PRODUCT BACKLOG
- 36. SPRINT BACKLOG User Story User Story User Story Epic Story Epic Story User Story User Story PRODUCT BACKLOG
- 37. TASK Each user story can be separated into (technical) tasks. As a plan to accomplish the work. AS A … I WANTTO … SOTHAT … Set up the database Create API call …
- 39. TO DO User Story User Story Task TaskTask DOING BLOCKED DONE SPRINT BACKLOG Task Task Dynamic representation of the work during a sprint.
- 40. DEFINITION OF READY Sprint Minimise Waste When is a product backlog item sprintable?
- 41. DEFINITION OF DONE Sprint Product Increment Minimize Risk When is a task really done?
- 42. PRODUCT INCREMENT = Potentially shippable increment of the product. It meets the Definition of Done!
- 43. PROGRESS MONITORS First we have to understand what a sprint and a sprint planning is.
- 45. ACTIVITIES - Sprint - Sprint planning - Daily scrum - Sprint review - Sprint retrospective - Product backlog refinement
- 46. Be adaptive! Iterate! Sprint Fixed timebox in which the Scrum team delivers a product increment according to the Definition of Done. between 1 and 4 weeks
- 47. SPRINT Project progresses in sprints Sprint commitment by Development team No new requirements during the spint Scrum team delivers a product increment
- 48. How do we plan? Sprint Planning Timeboxed meeting for the Scrum Team, to pull work into the Sprint Backlog max 2 hours per week of sprint
- 49. SPRINT PLANNING SPRINT BACKLOG PRODUCT BACKLOG Which items can the team commit to? What is the sprint goal? Which tasks can we identify for each story?
- 50. ITEM ESTIMATES The development team plays planning poker
- 51. RELATIVE ESTIMATES - Story points are more then just time - Compare to reference item - Faster, more accurate planning - Independent of developer skills Fibonacci: 1 2 3 5 8 13 ..
- 52. PLANNING POKER 1 - Product Owner explains item 2 - Developer compares with a reference item 3 - All cards are shown together 4 - Highest and lowest explained 5 -Team gets to a consensus, possible other round
- 53. Track progress during the sprint? Daily Scrum Timeboxed meeting for the Development team to make sure the sprint goal is reached. max 15 minutes
- 54. What did you do yesterday? What will you be doing today? Are there any blocking issues? Everyone. Short.Turn by turn. And take necessary steps after the Daily Scrum
- 55. Sprint improvements? Sprint Retrospective Timeboxed meeting for the Scrum team to discuss the sprint and improve further. max 1 hour per week of sprint
- 56. What did we do good in last sprint? What did we do less in the last sprint? Are there any questions or uncertainties? Are there any open items from last retrospective? Everyone.Write down. Group the items and discuss. Plan and take action.
- 57. Delivered product? Sprint Review Timeboxed meeting for the Scrum team and stakeholders to review the product increment max 1 hour per week of sprint
- 58. Updated backlog! Product Backlog Refinement Scrum team keeps the product backlog up to date, to have a shared understanding of what needs to be done ongoing activity
- 59. Add stories. Remove stories. Split stories. Add detail to stories. Prioritise stories. Estimate stories. Product Backlog Refinement
- 61. PROGRESS MONITORS Now we understand what a sprint and a sprint planning is.
- 62. A story point is more then just time. How do we know how many story points we can handle as a development team? MEASURE!
- 64. VELOCITY used by developers for better sprint estimations and to stabilise progress
- 65. VELOCITY used by the product owner to make forecasts that help to prioritise items
- 66. VELOCITY GRAPH | | | | | | | | LongTerm ? Remaining story points Sprints| | | | | | | | Stability ? Predictability ?
- 67. VELOCITY GRAPH | | | | | | | | Remaining story points Sprints | | | | | | | | Deadline
- 68. VELOCITY GRAPH | | | | | | | | Remaining story points Sprints | | | | | | | | Deadline Will deliver Might deliver Not delivered