Team management roles: Scaling your Scrum practices
Efficiently manage and coordinate multiple teams, both Agile and traditional
Andrea, Release Manager
Responsibility: Controls the release path to production
Solution:
- Define custom metrics for Burn-downs, Scope changes, Bugs and other KPIs across one or multiple teams and sprints
- Get accurate forecast & treding information on completion dates
- Take corrective actions in advance to ensure timely delivery
Stephen, Release Train Engineer
Responsibility: Coordinates multiple ARTs
Solution:
- Define Program Increments (PI) and ARTs
- Track statuses, coordinate activities and dependencies from PI Planning to PI Release
Donna, Product Owner/Manager
Responsibility: Creates & maintains Roadmaps and Backlogs
Solution:
- Create Product Roadmaps
- Visualize your Release scope, Roadmaps, execution progress and status
- Better visualization of sub-tasks, linked issues & user stories linked to Epics
Tom, QA Manager
Responsibility: Ensures the Release Process & Quality Standards are met
Solution:
- Manage quality standards with milestones & quality gates
- Define own process and metrics
- Easily track & manage the release process
Dave, Scrum Master
Responsibility: Leads multiple Scrum teams
Solution:
- Gain visibility beyond the current iteration, across multiple teams & sprints
- Create custom metrics and goals across multiple Agile boards, Epics & sprints
Kate, Engineering Manager
Responsibility: Manages team operations & ensures objectives are met
Solution:
- Get accurate forecasting of delivery date
- Easily collect low and high-level metrics such as reported and resolved bugs
- Coordinate across multiple teams and sprints
Clare, Program Manager
Responsibility: Monitors program status & progress
Solution:
- Visualize your program roadmaps, execution progress & status
- Create multi-team programs
- Get actionable data from custom metrics, ensure visibility and control for multiple iterations
Jack, VP of Engineering
Responsibility: Reviews the status of multiple releases
Solution:
- Unify visibility across multiple Jira projects or releases
- Attain clear, concise definition of scope and status
- Understanding of red status and high risk