Your SlideShare is downloading. ×
0
Agile teams
Agile teams
Agile teams
Agile teams
Agile teams
Agile teams
Agile teams
Agile teams
Agile teams
Agile teams
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile teams

383

Published on

The importance of structuring your teams correctly when doing agile can not be

The importance of structuring your teams correctly when doing agile can not be

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
383
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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?

×