Agile teams
This document discusses optimizing agile team structures. It recommends focusing on having one business analyst for every 4-5 developers on a team. Teams should rotate development work through support roles and separate project and production work. Cross-product teams should be focused on client implementations. Technical analysts should transition to support developer or business analyst roles. Developers should be responsible for quality control during development and automate user stories with unit tests. Business analysts are responsible for testing during sprints while focusing on one project at a time. Work should be rolled up across frontend and backend into single user stories. Offshore teams use video conferencing for standups, planning and reviews. Client owners bring requirements to product owners and are stakeholders. Product forums are organized
Agile teams
- 1. Agile teams
- 2. Ideal Project team structure Developer Business analyst Tester 6
- 3. Teams structure optimisation For Programs: Virtual, created from product support Pure production product support Kanban Product development Scrum Client implementations Scrum
- 4. Support & project interface 1 1 1 2 2 2 3 3 3 4 4 Sprint 1 In progress Analysis Dev Done Sprint 2
- 5. Focus on 1 business analyst to 4/5 developers Rotate development through support Separate project (product) & production work Focused cross-product teams for client implementations Transition technical analysts into support developers or business analysts
- 6. continue... Focus on Developers responsible for QC during development cycle Developers automate on user stories = unit tests Business analyst responsible for testing during sprint Focused on 1 project @ a time Rollup work across layers (front-end & back-end) into 1 user story Off-shore teams: VC for standups, planning & review
- 7. continue... Focus on Client owner responsible for bringing requirements to product owner of a product. Client owner is a stakeholder to the product owner Product forum per product Upgrade technology stacks Move to single web solution
- 8. continue... Main findings Install continuous integration environment Automate deployments Test with in each cycle
- 9. Future releases 1 1 1 1 2 2 2 2 3 3 3 3 4 4 4 5 Sprint 2 Sprint 1 Release Sprint 1 Sprint 2 UAT 2-3 days Release UAT 2-3 days
- 10. Questions?