pmi-agile for distributed teams

1

Agile in Distributed Teams?June 25, 2016

Shuchi Singla, AKT, SPC, PMI-ACP

2

Introduction

3

What makes Agile Successful?

• Constant focus on business value

• Quality

• Overcoming common challenges

• Experience

• Collaboration!!

2/12/14

4

“Richness” Scale

Face-to-face conversation with a physical whiteboard

High-resolution, large-screen videoconference with a virtual whiteboard

High-resolution, large-screen videoconference

Low-resolution, small-screen videoconference

Telephone call using high quality phone hardware and a land line (=clear connection)

Telephone call using poor quality phone hardware and VOIP (=noisy connection)

Instant messaging and real-time text chat

Wikis and electronic discussion boards

Email

“Richer” Communication

“Poorer” Communication

5

Distributed TeamsYou can be distributed while working in the same room

If you don’t talk face to face, you are distributed

6

Complications

Strategic

Communication

Cultural

Team dynamics

Security

7

Complications

Time zones

By TimeZonesBoy (Own work) [CC-BY-SA-3.0 (http://creativecommons.org/licenses/by-sa/3.0)], via Wikimedia Commons

8

Why are you communicating?

Privacy

Team Collaboration

Collective Wisdom

Documentation

Code

Test Cases

Process

9

Lets Play Negation game

Description - This is a game of discovery.  

Instead of asking how we can make things better, we'll ask how we can make things horrible.  Sometimes it's easier and can even be a little fun to be negative.  

10

Example

How can we make our pair programming partner miserable?

We can refrain from taking a bath.

We won't brush our teeth.

11

Negation

Our original horrible ideas…

We can refrain from taking a bath

We won't brush our teeth

Become good rules…

We will take a bath

We will brush our teeth

12

Negation

After Negation

Establish “rules”

Try to get to a shared understanding or state

Prioritize the shared understanding

Could produce action

13

Sprint Planning

Sprint Planning Part 1 - (1 hour timeboxed) - Weds 8am New York / 6:30pm India. Product Owner walks the team through the items at the top of the Product Backlog, team asks questions, clarifies their understanding, and make suggestions.

Sprint Planning Part 2a - (2-3 hours) - Thurs India workday hours. Team starts doing an initial analysis, task breakdown, and estimation of the items at the top of the Product Backlog. They come up with a list of questions for the Product Owner.

Sprint Planning Part 2b - (1 hour timeboxed) - Thurs 8am New York / 6:30pm India. Team and Product Owner discuss the team's open questions, and the team decides their commitment for the Sprint

Sprint Planning Part 2c - (1 hour timeboxed) – Fri 8am New York / 6:30pm India. Team and Product Owner discuss the team's open questions, and the team decides their commitment for the Sprint

Work begins – Monday India workday hours.

14

Agile ceremonies – daily scrum

15

Collaboration Call

45 minutes can be used to ask questions/get answers on current sprint work, groom the backlog, size a handful of new stories that have been added to the Product Backlog, or any other activity.

16

Some Cool Tools

planningpoker.com (everyone should have this)

ScribLink.com (Online white board)

Mural.ly (sticky notes, images, go visit, it’s cool)

Board.net (Collaborative writing with etherpad.org)

Scribblar.com (Online white board) -free for 2 users

LisThings.com (Free corkboard)

Coggle.it (Collaborative mind mapping)

172/12/14

@singlashuchi or shuchi.singla@bafflesol.com