Agile Pod Methodology
Dedicated Multidisciplinary Agile teams to deliver desired outcomes
How it works?
A Pod becomes either an extended Tech team to current setup or can own specific outcomes.
Reporting to Initiative/Project Owner
Extended Tech arm for faster product roadmap achievement
Pod led by Pod Owner who reports to the Client Initiative/Project Owner
Outcome Ownership Model with control on Requirements & Priorities
How we set it up?
1
Ideate
- Define Key attributes and OKRs
- Setup team, define budget, duration and skillset
2
Plan
- KT and Requrements gathering
- Governance of communication candence
- Project planning and workflow
3
Execute
- Architecture, coding,testing,VAT and deployment
- Quarterly and monthly reviews
- Retrospection
Key Benefits & Differentiators
-
Fungible
Built to scale, size can be changed based on Requirements due to limited dependency on individuals
-
Knowledge Retention
Overlap across Pods, Existing Pod members in spin off Pod for hitting the ground running
-
Autonoumous
Multiple roles in a single team based on Requirements, in a team that can own work with limited oversight if required
-
Optimal Sized Teams
Nimble team in a pod ideally less than 10-12 in size for faster collabration & achievement of outcomes