Injustice - Developers Among Us (SciFiDevCon 2024)
Â
Growing Agile Teams Poster
1. Growing Agile Teams team name:
â Specialist knowledge shared
â Acceptance test-driven dev
â Limited manual testing
STEP 4. Scale â Automated testing of NFRs
grow knowledge, share learning, â Communities of Practice
expand capabilities â Shared DeïŹnition of Done
â Stable and veriïŹable builds
â Cross-cutting concerns
â Entire team works on release
â Everyone experiences SM â Business value drives work
â Team owns environment â Visible measure of value
â Velocity guides release â Swarms on committed PBIs
â Owns external dependencies
STEP 3. Maximize Value
organize to deliver maximum value â Reduces technical debt
â Grow engineering practices
â Automated PBI testing
â Team takes 6-10 PBIs â Business value understood
â Predictability over 90% â PBIs done in priority order
â PBIs reviewed as done
STEP 2. Gain
Experience â Shared code ownership
people, process and work all settling
in, focus on learning
â
â
Technical debt identiïŹed
Bugs actively ïŹxed
agile teams ïŹrst focus on
â
â
1-3 improvement actions
Release DeïŹnition of Done
smoothing ïŹow and
enhancing quality, leading to
â Cross-functional Teams
â Regular backlog
â
â
Working Agreement
PBIs for 1-2 sprints
maximizing of value delivery
grooming
â Impediment backlog
STEP 1. Organize â PBIs broken into tasks
â Active Learning Cycle maximizing value
preparing the structures, work and â Transparent team
â DeïŹnition of Done
people capacity
â DeïŹnition of Ready enhancing quality
â Daily stand-ups
â Potentially shippable
â Sprint burndown
â Vision and requirements
smoothing ïŹow
â Focus on 2-3 PBIs
more each stage acts as a scaffold, offering guidance and more
directive support, for different phases of a teamâs agile journey guiding
copyright 2011 agile42 consulting ltd
the accompanying Growing Agile Teams worksheets provide more details behind the checklist for each step