Post on 14-Jan-2015
description
transcript
Agile teams
Developer
Business analyst
6
Ideal Project team structure
Tester
Teams structure optimisation
Pure production product support
Kanban
Product development
Scrum
Client implementations
Scrum
For Programs: Virtual, created from product
support
Support & project interface1
2
3
4
1
2
3
4
1
2
3
Sprint 1Sprint 1 Sprint 2Sprint 2
In progressIn progress DoneDone
AnalysisAnalysis DevDev
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
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
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
continue... Focus on
Install continuous integration environment
Automate deployments
Test with in each cycle
continue... Main findings
Future releases
1
2
3
4
1
2
3
4
1
2
3
Sprint 1Sprint 1 Sprint 2Sprint 2 Sprint 1Sprint 1 Sprint 2Sprint 2
1
2
3
4
5
ReleaseRelease UATUAT
2-3 days2-3 daysReleaseRelease UATUAT
2-3 days2-3 days
Questions?