managing projects using distributed teams with agile scrum
Post on 18-Sep-2014
32 views
DESCRIPTION
TRANSCRIPT
www.hawkeyechannel.comwww.hawkeyechannel.com
Managing Distributed Scrum Projects
March 10, 2010
Vaughn AustVP – Product Management
www.hawkeyechannel.com
Presentation Focus
2
DISTRIBU
TED SCRU
M
© 2010 hawkeye, all rights reserved.
www.hawkeyechannel.com
Agenda
Challenges with Distributed ScrumScrum BasicsDistributed Scrum Best Practices
DISTRIBU
TED SCRU
M
www.hawkeyechannel.com 4
CHALLENGES WITH DISTRIBUTED SCRUM
© 2010 hawkeye, all rights reserved.
www.hawkeyechannel.com
Challenges with Distributed Scrum
5
Communication Scrum focuses on person-to-person communication, which is best when there is
trust and shared social experiences Noisy communication channels Different time zones, availability Language
Knowledge transfer
Culture Conflicting behaviors and processes
DISTRIBU
TED SCRU
M
© 2010 hawkeye, all rights reserved.
www.hawkeyechannel.com 6
SCRUM BASICS
6© 2010 hawkeye, all rights reserved.
www.hawkeyechannel.com 7© 2010 hawkeye, all rights reserved.
Scrum RolesD
ISTRIBUTED
SCRUM
www.hawkeyechannel.com 8© 2010 hawkeye, all rights reserved.
Scrum Roles
Roles Responsibilities
Scrum MasterSchedules/runs all Scrum MeetingsRemoves Blocking issuesSet-up/maintains standard reports , backlog and tasks
Lead EngineerEngineer
Architecture direction, translates features to designLeads Sprint Design meetingCode reviews (peer or lead)Time estimationCode, unit testing and technical documentationDemo functionality as tasks are completed
Quality AssuranceTest execution, test plan, test cases, regressionApprove and demo functionality during Sprint Review
Product OwnerSpeaks for customer (prioritization, features, etc.)Creates backlogsUser documentation
CustomerRequest featuresCannot change current backlog once it startsChange future backlog at any time
ManagementRemoves Blocking issues
DISTRIBU
TED SCRU
M
www.hawkeyechannel.com 9© 2010 hawkeye, all rights reserved.
Agile Factors
Agile
Success
Team
Process
Tools
Communication
DISTRIBU
TED SCRU
M
www.hawkeyechannel.com
Agile is a frame of mind, not a one size fits all project process
10
Agile framework Focus is on shipping working code, faster Continuous improvement and delivery are everyone's responsibility Self organized and self directed teams
• Use the framework and best practices that work best for your team• Velocity will increase over time, as the team gels around strengths/weaknesses
and process is improved Structure for managing change – the one certainty in software
development• Users do not know what they want until they see or use software• It is not possible to completely specify an interactive system
Just enough mentality Refactoring is a way of life
DISTRIBU
TED SCRU
M
© 2010 hawkeye, all rights reserved.
www.hawkeyechannel.com 11© 2010 hawkeye, all rights reserved.
Agile is a frame of mind, not a one size fits all project processD
ISTRIBUTED
SCRUM
Agile Backlog•Prioritization is owned by the Product Owner (reserve a %
for refactoring)•Team estimates and commits during Sprint Planning and
Sprint Design
Agile Sprints•Iterations of fixed length•One the sprint has started, no new tasks (choice to scrap
and start over)•Determine the process and then stick to it (make changes
during the Retrospective)
Agile Daily Scrum•15 minutes max or Scrum Master is fired•3 questions = Yesterday, Today, Blocking issues•All Pigs attend everyday
www.hawkeyechannel.com 12© 2010 hawkeye, all rights reserved.
Agile is a frame of mind, not a one size fits all project processD
ISTRIBUTED
SCRUM
Agile Artifacts•Requirements•Technical Requirements•Business Requirements•Workflow•Wireframes/Mock-ups
•Functional Specs (Custom only)•Specs/Requirements translated to backlogs•Test plan
Agile Sprint Tasks•1 day max in length•Understood “work lanes” thru TFS task status, separate
tasks for QA•Task includes Owner, Estimate, Work Completed, Work
Remaining
Agile Schedule•Backlog “pre-estimates” are in Days, Task estimates are in Hours•Determine Sprint deployment dates ahead of time, usually 3-4
weeks apart•Production includes 3 days of regression•Use ideal days (85%) and subtract any expected holidays,
regression testing and configuration days•Label bottom 10% of tasks as Optional
www.hawkeyechannel.com
Reaching Backlog Agreement – how much documentation?
13
DISTRIBU
TED SCRU
M
© 2010 hawkeye, all rights reserved.
Detailed User Stories
Descriptive User Stories
Simple User Stories
www.hawkeyechannel.com 14© 2009 hawkeye, all rights reserved.
DISTRIBUTED SCRUM BEST PRACTICES
www.hawkeyechannel.com
Scrum Best Practices
15
The backlog is the single source of truthStandard Meetings Sprint planning Sprint design Pre-planning Meeting Ongoing Engineer demos (at least 2 times a week) Sprint review by QA Sprint retrospectives
Ongoing communication In-person is best, Instant messenger, Email, live meetings
Continuous integration, continuous testing and one-click deployment Functionality is not done until QA says so
Automated quality checksAutomated sprint burn-down reportsNo distinction between developers at different sites (designers and coders)
DISTRIBU
TED SCRU
M
© 2010 hawkeye, all rights reserved.
www.hawkeyechannel.com 16© 2010 hawkeye, all rights reserved.
Best Practices Hierarchy
Engineer Demos, Technical Wiki
Quality Automation, Sprint Review, Pre-Planning Meeting
Continuous Builds, Code Quality Testing, Automated Burn-downs, One-
click Deployment
Daily Scrum, TFS Backlog, Sprint Planning, Sprint Design , Sprint Retrospectives, Code Reviews
DISTRIBU
TED SCRU
M
Mature Teams
www.hawkeyechannel.com 17© 2009 hawkeye, all rights reserved.
DISCUSSION