Methodologies
Scrum
Kanban
XP (Extreme Programming)
Measurement
Estimations
Velocities
Stories
Lean Development
Benefits
Cadence / Capacity
Prioritization of tasks
Sprint dedicated work time
Deliver value in small chunks
Higher Visibility
Internet quotes
"Writing Tests is being professional" - Bob Martin (Uncle Bob)
Agile Manifesto
Individuals and interaction over process and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Current + Upcoming work
Surfacing blockers / roadblocks
Burndown
Bus Factor
SAFe (Scaled)
Do whatever
Optimize process (Retros)
Customer focues release plan
Priority shippable code every sprint
Eliminate "waste" wherever possible
Visualize Workflow
Limit WIP
Measure Lead Time (Cycle Time)
Ways to estimate
T-Shirt Sizes
"If you adopt only one agile practice, let it be retrospectives. Everything else will follow." - Woody Zuill
Focuses on Pair Programming
True Scrum
Stricter Scrum w/ Engineering Practices
Fibonacci
Roles
Scrum Master
Responsibilities
Retrospectives
The Sailboat
Liked, Lacked, Learned
Straw, Sticks, Bricks
The Starfish ✯
Outcomes of Retros
How deliver value
Sharpen the Axe
Facilitate
Squad
Ownership of code
Releasing product to customer
Working with Product, QA, Arch, Ops, TSE, Support
Not commit to unclear work
How could you plan a release with 12+ teams
No changes to sprint once started
Post Mortem
To measure the speed of a car, the road should not move.
Risks/ Challenges
Sprint
How to estimate Unknowns
Work spills over
Work takes longer than expected
Don't know what I'm commiting to
Release
Introducing a bug
Evaluate and optimize process
Sprint / Project Retro
Toyota
Team performance is directly proportional to team stability. Focus on building and maintaining a stable team. Stability reduces friction and increases credibility and confidence
Unknown > expected
Clarity
Ready Backlog
DoD Definition of Done
Definition of Start
Clear Definitions
Unready work creates
OKR (Objectives & Key Results)
Accountability
Solid understanding of roles
Safety
Agile Testing
TDD Test Driven Development
Quality Vs. Quantity
Inter-team trust
Testing
Focus on deliver the most value
High Transparency
Boards / Spaces to communicate project status
Team commits to work
Measurable Progress
Continual Feedback
Predictable release management
Cummulative Flow Diagram
During a sprint - Burndown
KPI (Key Performance Indicators)
If you don't measure it you don't change it
Leaving with action Items
If a meeting doesn't leave withsomething to do, was it successful?
How do we know what we're doing is right?
Too many problems to fix?
Eliminate Waste, Build Quality In, Create Knowledge, Defer Commitment, Deliver Fast, Respect People, and Optimize the Whole
Coggle defining roles https://coggle.it/diagram/W6n7oTXvFHsqnyi3/t/agile-team
Missing deadline
Agile Transformation https://coggle.it/diagram/WzOJtTCAbmUxop2t/t/agile-transformation-project