scrum in the enterprise - making it work with distributed teams - liz heier

#atlassian

NOTES:

• Your main title goes in the large blue

font.

• If you have a title that naturally splits

into a subtitle, use the smaller green

font for the subtitle. If not, delete the

subtitle

PHOTO

1. Place your photo at around the

same size as the example photo

2. (Keynote users:) Move your photo

onto the blue shape below Select both

photo and shape and then choose

“Mask with selected shape” from the

menu. Double click the photo to edit

the scale and crop position.

LIZ HEIER • WEB APPLICATIONS DEVELOPMENT MANAGER • GARMIN • @lizheier

Scrum in the Enterprise

Making it work with distributed teams

NOTES:

• Photos that fill up the entire

screen have a great visual

impact.

Does she know her stuff?!!   14+ years in Web Development

!   Certified Scrum Master

!   JIRA Administrator, Confluence Guru, and all-around Atlassian fan

!   55 developers on 2 continents

!   6 Cross-Continent Scrum Teams

!   Stakeholders located in 62 offices scattered around the globe

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

co·lo·cate : to locate together; especially : to place (two or more units) close together so as to share common facilities!

Sounds great! Oh wait…!

Our focus groups like blue buttons!

What color should this button be?

Project knowledge is scattered!

Opportunities to collaborate are limited!

Time to get my day started!

Time to go home!

Standard collaboration tools don’t work!

I created this great UX mockup on the whiteboard!

I wish I had a mockup for this page.

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

ef·fec·tive : producing a result that is wanted : having an intended effect!

But how do I do that?!

You need these 3 things…!

The

Right Process

The

Right People

The

Right Tools

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

pro·cess : a series of actions that produce something or that lead to a particular result!

Rinse. Lather. Adjust. Repeat.!

I love Scrum!

Sound familiar?!

When will you be done?

Where is your requirements document?

What do you mean we have 2 hours to close that code review?

Where are your design diagrams?

When will you be done?!

Estimate the backlog

Identify the MVP

Monitor scope

Use���burn-up charts Target Launch Date

=

Sample Burn-up Chart!

0

100

200

300

400

500

600

700

800

900

1000

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

Projection

Scope

Actual

Internal Beta Public Launch (MVP)

Where is your requirements document?!

The stories are your requirements!

We can’t do that…can we?!Don’t let “we’ve always done it this way” derail your project!

Review your processes and controls!

Don’t let them be an excuse on your quest to be agile.

Code reviews should be completed in hours, not days

Create living design documents that grow with your project

Why it works for us!

Surprises

!   Clarity across the team.

!   No Surprises.

!   Everyone is invested.

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

peo·ple : humans making up a group or assembly or linked by a common interest!

How do I know which are the right ones?!

Scrum Master Owns the Process

Product Owner Owns the value

Dev Team Owns the implementation

So many titles…!

SCR

UM

TEA

M Business Analyst

Technical Lead

Quality Assurance

Project Manager

Program Manager

Architect

Security

…and only 3 roles!

Who is your Scrum Master?!

ANYONE

Who is your Product Owner?!

Primary Stakeholder

Business Analyst

Project Manager

Who is on your Scrum Team?!

Solution Architect Developers QA + +

Know your people!

!   Everyone involved must communicate, communicate, communicate.

!   Leave egos at home.

!   Independent spirits that can be team players.

!   Dust off the passports now and then.

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

tool : something used in performing an operation or necessary in the practice of a vocation or profession !

A developer is only as good as her tools.!

Stories, Requirements,

Priorities, Decisions, Scope,

Status

Design discussions,

diagrams & documents,

Meeting notes, &

Retrospectives

Code Reviews,

Implementation discussions,

Collaboration

Email has a time and a place!

!   Email is a communication tool not a documentation system.

!   Decisions made in email should be immediately captured in JIRA or Confluence.

!   Create project mailing lists. Always send communication to everyone on the team for transparency.

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

!Successful Scrum in the Enterprise with distributed teams!

Thank you!!

The

Right Process

The

Right People

The

Right Tools + +

=

Thank you!

LIZ HEIER • WEB APPLICATIONS DEVELOPMENT MANAGER • GARMIN • @lizheier