One product multiple component teams
This pictures shows one product backlog with features that are being split across three component teams.
Resources
Related Content:
Courses
Blog
- System Access Rights Can Be an Impediment to Creating Feature Teams
- Stakeholders Missing at Sprint Reviews – Part One: Nothing to See Here
- Restructuring Teams to Do Agile at Scale: The Fallacy of Magical Thinking
- Patterns for Engaging Specialists in Agile Development
- Demystifying Product Backlog Concepts
- Distinguishing Between Feature & Component Teams
Presentations
Visual AGILExicon
- Scrum framework—Refinement
- Sprint review activity—refined
- Sprint review activity
- Sprint-planning activity
- Fixed-date-release burnup chart
- Sprint mapping
- Release-planning activity
- Envisioning (product planning) activity
- Hierarchical scrum planning
- Roadmap and product backlog
- Release line in product backlog
- Two products multiple component teams
- Product owner manages economics
- Who does estimating
- What and when we estimate
- Product backlog pipeline
- Product backlog (in context)
- Scrum framework
- Scrum practices
- Agile development overview
- Component
- Product backlog
- Product backlog grooming