Download to read offline
Uploaded byJohn Dobbin
Agile Subcomponents
This document discusses Agile principles and practices that can be applied to any team. It covers the importance of daily meetings and face-to-face interactions. It also discusses techniques like timeboxing, user stories, and retrospectives. Timeboxing uses limited time periods to drive productivity. User stories help reduce problems through stakeholder conversations. Retrospectives aim to continuously improve through reflection. The document recommends keeping an exploratory mindset to keep learning.
More Related Content
Agile Subcomponents
- 1. Agile Fundamentals |Session Three // Agile Principles and Practices for any team AGILE SUBCOMPONENTS
- 2. LEARNING OBJECTIVES DAILY MEETINGSThe importance of short daily meetings and face-to-face interactions AGILE MICRO-PRACTICES Many Agile techniques can be applied anywhere RETROSPECTIVES The discipline of continuous improvement USER STORIES How to reduce “challenged” projects through requirements conversations TIMEBOXING How this enabling constraint drives productivity
- 3. TIMEBOXING a period oftime during which a person or a team works steadily towards the completion of some goal enabling constraint
- 4. Sprint = 1month (max) Sprint Planning = 8 hrs (max) Sprint Review = 4 hrs (max) Daily Scrum = 15 minutes (always) Sprint Retrospective = 3 hrs (max) Development SCRUM TIMEBOXES
- 5. Sprint = 2weeks Sprint Planning ~ 4 hrs Sprint Review ~ 2 hrs Daily Scrum = 15 minutes Sprint Retrospective ~ 1.5 hrs In shorter sprints, event times shrink proportionally with the exception of the daily Scrum which remains 15 minutes Development GO DEEPER
- 6.
- 7. GO DEEPER of thevariation in a team’s performance can be accounted for simply by the number of face-to-face exchanges among team members. 35%
- 8. 3 QUESTIONS What haveyou completed since the last meeting? What do you plan to complete by the next meeting? What is getting in your way?
- 9.
- 10. User Stories vsRequirements Stakeholders analyst conversation Developers Huh ???
- 11. As a <userrole> I want to <do something> because: <reason> Importance < MoSCoW* prioritization > Must haves Should haves Could haves Won’t haves *
- 12. conversation Stakeholders Product Owner Developers Asa current bank account holder, I need to access my account, so that I can withdraw cash. Well-written user stories invoke conversation and shared understanding GO DEEPER
- 13.
- 15. Retrospectives plan ways toincrease quality and effectiveness GO DEEPER what went well ? what didn’t ? ideas ? reflect on assumptions, interactions, processes, tools, etc. commit to action
- 16.
- 17.
- 18. RECAP Use short dailyteam meetings to improve communitication flow Use timeboxing to increase productivity Use retrospectives to drive continuous improvement Use user stories to generate shared understanding Keep exploring, keep improving, keep learning
- 19. SERVICES ENTERPRISE AGILE COACHING IN-HOUSETRAINING & DEVELOPMENT AGILE-AT-SCALE TRANSFORMATION CONSULTING CONTACT john@johndobbin.com.au
- 20. LinkedIn : johndobbin Twitter: @johndobbin