Distributed Scrum and Agile

Not doing Gemba Walks!

Outsourcing the hiring process of new people

Trying to standardize and simplify everything

Doing requirement handowers, not doing validated conversation

Delegate all management to an outsourcing company and not having global alignment.

See people in distributed teams more as resources than highly qualified knowledge workers

Not enough Speaking/Writing in English

Short term project thinking mindset for the distributed work with high WIP

Not having global tools in place

Not focus on quality in every step

Try: Google spreadsheet

OCS (Lynx)

Skype

The Cynefin Framework

A sense-making model

Pitfall

Typical

Story

Agile Coach / QA Manager

Pitfall

10

Common

Pitfalls

Pitfall

@madsth

Distributed Scrum and Agile

dk.linkedin.com/in/MadsTroelsHansen

Distributed Patterns

How to create an optimal balance and maximize VALUE

blog.lean-agile.dk

http://blog.lean-agile.dk/2011/06/22/offshore-patterns/

mth@lean-agile.dk

Global

Technical

Foundation

Team

Structures

Some References

Scrum in

Distributed

Envirorment

Some more about Distributed Patterns

http://blog.lean-agile.dk/2011/06/22/offshore-patterns/

Typical Team Structures

Hard for the PO to lead the Product Vision

Hard for the team to be a team

Challenge

Vision and Business Value

Cynefin

http://ale2011.eu/2011/10/04/ale2011-keynote-dave-snowden/

Global Facilitation

SM

PO

Global

Communication

Global

Global

Collaboration

Try: corkboard.me

Sprint Progress

VIDEO!

Most value with long term managed teams

Innovation Games

Meeting Rooms

Each personal PC

Product Increment

Product Owner

Problem: Don't know where we are?

Feature Injection

Shorter Sprints

Try

Global

This presentation

Shorter release cycles

Problem: Too much time for stabilizing

Problem: Product Vision

Try

User Story Mapping

Team-vote about Quality

Try

Don't: Write more documents

Commulitative Flow Diagram

Continuously talk in team about quality

http://blog.lean-agile.dk/presentations/p2012/

Global Infrastructure

Virtual Test Environments, ie TFS LAB

Try

Global

Scrum

Team

End2End life cycle management, ie. TFS

Global

Global

Scrum

Artifatcs

Problem: Focusing on disciplines not Stories

Facilitate Team Agreements

Sprint Backlog

Managed using a board, virtual/physical (syncronised)

Do shorter Sprints

Create a Virtual Window

Rotate team members between locations

Try

Prepare Scrum meetings more

Don't: Do more controlling and follow up

Global

Distributed Team collaborate to create it

Problem: Low collaboration in Scrum Team

Problem: Not working well together

Don't: Increase focus on technical disciplines

Scrum Master

Definion of Done

Development Team

Improve DoD for Sprint

Global

Use other formats for

Grooming and Planning

Feature Injection

Try

Don't: Stop doing it.

User Story Mapping

Don't: Try only to group the backlog

Sprint Retrospective

Problem: Not getting into the root cause

Problem: Just a long list of User Stories

Change it, learn other techniques

Create shared board with improvement actions

Focus Grooming based on a "Definition of Ready"

Don't: Stop doing grooming!

Product Backlog

Global

Try

Global

Problem: Using too much time "creating solutions"

Grooming

Do onsite retrospectives

Use collaboration tools

+ DoD for US and Sprint

Define á Sprint Goal

Don't: Start controlling and assigning tasks as a traditional PM

Scrum Planning

Try

Problem: Too much process discussion

Global

Scrum

Events

Use recommended Scrum planning agenda

Global

Ask customers to explain how the functionality will be used

Global

Problem: Not constructive feedback

Don't: Stop invite customers for review

Sprint Review

Try

What you don't know you don't know

Ask for help in the team

Try

Visualise problems and ALL work

Don't: Start doing controling status

Use shared task board

Problem: Just 3 questions with no problems

Daily Scrum

Global