Your SlideShare is downloading. ×
0
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
Managing projects using distributed teams with agile scrum
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

Managing projects using distributed teams with agile scrum

2,657

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,657
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
80
Comments
0
Likes
2
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. Managing Distributed Scrum Projects<br />March 10, 2010<br />Vaughn Aust<br />VP – Product Management<br />
  • 2. Presentation Focus<br />2<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />
  • 3. Agenda<br />Challenges with Distributed Scrum<br />Scrum Basics<br />Distributed Scrum Best Practices <br />DISTRIBUTED SCRUM<br />
  • 4. 4<br />Challenges with Distributed Scrum<br />© 2010 hawkeye, all rights reserved. <br />
  • 5. Challenges with Distributed Scrum<br />Communication<br />Scrum focuses on person-to-person communication, which is best when there is trust and shared social experiences<br />Noisy communication channels<br />Different time zones, availability<br />Language<br />Knowledge transfer<br />Culture<br />Conflicting behaviorsand processes<br />5<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />
  • 6. Scrum Basics<br />6<br />© 2010 hawkeye, all rights reserved. <br />
  • 7. Scrum Roles<br />7<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />
  • 8. Scrum Roles<br />8<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />
  • 9. Agile Factors<br />9<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />
  • 10. Agile is a frame of mind, not a one size fits all project process<br />Agile framework<br />Focus is on shipping working code, faster <br />Continuous improvement and delivery are everyone&apos;s responsibility<br />Self organized and self directed teams<br />Use the framework and best practices that work best for your team<br />Velocity will increase over time, as the team gels around strengths/weaknesses and process is improved<br />Structure for managing change – the one certainty in software development<br />Users do not know what they want until they see or use software<br />It is not possible to completely specify an interactive system<br />Just enough mentality<br />Refactoring is a way of life<br />10<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />
  • 11. Agile is a frame of mind, not a one size fits all project process<br />11<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />
  • 12. Agile is a frame of mind, not a one size fits all project process<br />12<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />
  • 13. Reaching Backlog Agreement – how much documentation?<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />Detailed User Stories<br />Descriptive User Stories<br />Simple User Stories<br />13<br />
  • 14. 14<br />DISTRIBUTED Scrum Best Practices<br />© 2009 hawkeye, all rights reserved. <br />
  • 15. Scrum Best Practices<br />The backlog is the single source of truth<br />Standard Meetings<br />Sprint planning<br />Sprint design<br />Pre-planning Meeting<br />Ongoing Engineer demos (at least 2 times a week)<br />Sprint review by QA<br />Sprint retrospectives<br />Ongoing communication<br />In-person is best, Instant messenger, Email, live meetings<br />Continuous integration, continuous testing and one-click deployment<br />Functionality is not done until QA says so<br />Automated quality checks<br />Automated sprint burn-down reports<br />No distinction between developers at different sites (designers and coders)<br />15<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />
  • 16. Best Practices Hierarchy<br />16<br />DISTRIBUTED SCRUM<br />© 2010 hawkeye, all rights reserved. <br />Mature Teams<br />
  • 17. Discussion<br />17<br />© 2009 hawkeye, all rights reserved. <br />

×