Managing projects using distributed teams with agile scrum
Upcoming SlideShare
Loading in...5
×
 

Managing projects using distributed teams with agile scrum

on

  • 2,618 views

 

Statistics

Views

Total Views
2,618
Views on SlideShare
2,606
Embed Views
12

Actions

Likes
2
Downloads
73
Comments
0

2 Embeds 12

http://www.linkedin.com 10
https://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Managing projects using distributed teams with agile scrum Managing projects using distributed teams with agile scrum Presentation Transcript

    • Managing Distributed Scrum Projects
      March 10, 2010
      Vaughn Aust
      VP – Product Management
    • Presentation Focus
      2
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
    • Agenda
      Challenges with Distributed Scrum
      Scrum Basics
      Distributed Scrum Best Practices
      DISTRIBUTED SCRUM
    • 4
      Challenges with Distributed Scrum
      © 2010 hawkeye, all rights reserved.
    • Challenges with Distributed Scrum
      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 behaviorsand processes
      5
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
    • Scrum Basics
      6
      © 2010 hawkeye, all rights reserved.
    • Scrum Roles
      7
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
    • Scrum Roles
      8
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
    • Agile Factors
      9
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
    • Agile is a frame of mind, not a one size fits all project process
      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
      10
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
    • Agile is a frame of mind, not a one size fits all project process
      11
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
    • Agile is a frame of mind, not a one size fits all project process
      12
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
    • Reaching Backlog Agreement – how much documentation?
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
      Detailed User Stories
      Descriptive User Stories
      Simple User Stories
      13
    • 14
      DISTRIBUTED Scrum Best Practices
      © 2009 hawkeye, all rights reserved.
    • Scrum Best Practices
      The backlog is the single source of truth
      Standard 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 checks
      Automated sprint burn-down reports
      No distinction between developers at different sites (designers and coders)
      15
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
    • Best Practices Hierarchy
      16
      DISTRIBUTED SCRUM
      © 2010 hawkeye, all rights reserved.
      Mature Teams
    • Discussion
      17
      © 2009 hawkeye, all rights reserved.