#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.

Nate Van Dusen • Engineering Program Management Director • Trul ia •

Preparing Agile for Scale

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

Agile Is for Everyone

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Agi le is for Everyone

“Enterprise” Agile is for companies of ALL sizes

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Agi le is for Everyone

• Enterprise Agile is for the entire company, not just Engineering

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Agi le is for Everyone

• Companies of any size can employ Agile principles to:

• Ensure success as the company, projects, and teams grow

• Optimize entire organizations, from the top down

Engineering

CTO

Dev VP’s

Finance

CFO

Finance Leads

Product

Business Unit VP’s

Product Managers

The key to success is creating scalable Agile

methodologies that development teams and the business can sustain as they

grow.

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

Familiar Challenges

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Famil iar Chal lenges

• Dependency Tracking •  Cross-team planning is difficult. •  Scrum of Scrums must be held! •  Facilitator and Team Reps must attend.

Team 1 Team 2 Team 3 Team 4

Scrum o f Scrums

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Famil iar Chal lenges

• Proper Breakdown of Work

• You must create the ability to track from highest level business goal to sub-tasks.

Theme!

Epic!

Story/ Bug!

Task!

Managing Larger or Longer-Running Projects

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Famil iar Chal lenges

The Theme provides the opportunity, business

value and high level sizing.

The Epic breaks the opportunities into

independent capabilities and are prioritized

based on business value.

The Story breaks the Epic into smaller

features, functions that can be delivered

within a sprint.

Stories also describe dependencies.

Theme

Story 1 Story 2 Story 4 Story 3

Epic 1 Epic 2

Task The Sub-Task break the Story into work

that can be accomplished by a single engineer.

Breaking down the work

Task Task

Task Sub-Task

Task Task

Task Task Sub-Task

Task Task

Task Task Sub-Task

Task Task

Task Task Sub-Task

In order to surmount the challenges, businesses must plan ahead. Don’t

wait till it’s too late!

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

Lay the Foundation

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Lay the Foundation

Identify Persons to Fulfill Proper Roles

Product Owner

Scrum Master Team Member

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Lay the Foundation

Healthy Agile Ceremonies

•  It’s important to ensure your teams have and respect required ceremonies •  Backlog Grooming •  Sprint Planning •  Daily Scrum •  Sprint Review •  Retrospective

Expansion of development cycles and implementation

of product and business Agile cycles are required for

success.

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

Prepare to Scale

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Prepare to Scale

Consider Adding Additional Role

Product Owner

Scrum Master Team Member

Area Product Owner

Area Product Owners can be useful when a business unit has a product or

products that contain many subject areas.

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Prepare to Scale

Healthy Product Creation and Ideation

•  It’s important to ensure your Product teams have healthy process •  Product Backlog creation •  This should be a backlog separate from the sprint/development backlog •  This should be a place to record all product ideas regardless of whether they will be

released or not (protects IP and reduces rework) •  This backlog should feed the sprint backlog in a frictionless way •  Many tools are about to come to market for a product/portfolio backlog •  Data from this backlog should be able to create a company roadmap to be used

everywhere in the business •  Quarterly Planning •  Quarterly planning cycles should exist to review work and present new ideas •  Ideas presented should be at the Theme and Epic level •  Engineering should be exposed to ideas presented ahead of time

Feed the Sprint backlog with actionable Epics and

Stories.

NOTES:

• If you want to divide your talk

into chapters, use this slide for

Chapter titles

Leveraging the Atlassian Suite

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

SECTION TITLE 1

Let the tools help you!

• Using Epic’s is Vital •  Using epics and epic linking will let you distribute stories with across multiple teams while

maintaining visibility •  Use JIRA’s new Epic reporting to track Epic burndown •  Using Epics properly allows you to create valuable reporting for look backs and financial

reporting needs

• Use JIRA Agile!

• Utilize JIRA Reporting •  If you give JIRA the right data input the reporting you get out is valuable

•  Track your teams burndown and use the new reporting to track quarterly trends

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Leveraging the At lassian Suite

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Leveraging the At lassian Suite

Let the tools help you!

• JIRA Auto Triggers Save Time! •  If your company uses Stash, using the new Auto Triggers saves a lot of time •  Auto Triggers can be set on many things, but the most simple and valuable is auto ticket

transitions •  Developers don’t have to go back and forth between tools •  Tickets transition automatically after pull request

NOTES:

• If you use the Chaper Title with

sections system, you can place

a lozenge at the top of the page

to indicate the section, like this

example

• Use this only if it’s important to

remind people of where they’re

at in the Chapter sequence.

Leveraging the At lassian Suite

Agile needs to be a mindset valued and embraced by all

aspects of the business. Scaling Agile successfully

takes everyone.

Thank you!

Nate Van Dusen • Engineering Program Management Director • Trul ia