Managing projects using distributed teams with agile scrum
Download as PPTX, PDF2 likes1,926 views
The document discusses managing distributed scrum projects. It outlines challenges with distributed scrum including communication issues due to different time zones and languages. It then reviews scrum basics like roles of product owner, scrum master, and development team. The document discusses agile principles and factors like continuous delivery. It also provides best practices for distributed scrum projects such as standard meetings, continuous integration, and no distinction between developers at different sites.
Managing projects using distributed teams with agile scrum
- 1. Managing Distributed Scrum ProjectsMarch 10, 2010Vaughn AustVP – Product Management
- 2. Presentation Focus2DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved.
- 3. AgendaChallenges with Distributed ScrumScrum BasicsDistributed Scrum Best Practices DISTRIBUTED SCRUM
- 4. 4Challenges with Distributed Scrum© 2010 hawkeye, all rights reserved.
- 5. Challenges with Distributed ScrumCommunicationScrum focuses on person-to-person communication, which is best when there is trust and shared social experiencesNoisy communication channelsDifferent time zones, availabilityLanguageKnowledge transferCultureConflicting behaviorsand processes5DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved.
- 6. Scrum Basics6© 2010 hawkeye, all rights reserved.
- 7. Scrum Roles7DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved.
- 8. Scrum Roles8DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved.
- 9. Agile Factors9DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved.
- 10. Agile is a frame of mind, not a one size fits all project processAgile frameworkFocus is on shipping working code, faster Continuous improvement and delivery are everyone's responsibilitySelf organized and self directed teamsUse the framework and best practices that work best for your teamVelocity will increase over time, as the team gels around strengths/weaknesses and process is improvedStructure for managing change – the one certainty in software developmentUsers do not know what they want until they see or use softwareIt is not possible to completely specify an interactive systemJust enough mentalityRefactoring is a way of life10DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved.
- 11. Agile is a frame of mind, not a one size fits all project process11DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved.
- 12. Agile is a frame of mind, not a one size fits all project process12DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved.
- 13. Reaching Backlog Agreement – how much documentation?DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved. Detailed User StoriesDescriptive User StoriesSimple User Stories13
- 14. 14DISTRIBUTED Scrum Best Practices© 2009 hawkeye, all rights reserved.
- 15. Scrum Best PracticesThe backlog is the single source of truthStandard MeetingsSprint planningSprint designPre-planning MeetingOngoing Engineer demos (at least 2 times a week)Sprint review by QASprint retrospectivesOngoing communicationIn-person is best, Instant messenger, Email, live meetingsContinuous integration, continuous testing and one-click deploymentFunctionality is not done until QA says soAutomated quality checksAutomated sprint burn-down reportsNo distinction between developers at different sites (designers and coders)15DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved.
- 16. Best Practices Hierarchy16DISTRIBUTED SCRUM© 2010 hawkeye, all rights reserved. Mature Teams
- 17. Discussion17© 2009 hawkeye, all rights reserved.