Brandon Huff has almost 20 years of experience managing large software projects for Fortune 500 companies. He will discuss how Atlassian tools can be used to support SAFe 4.5, an iterative framework for scaling Agile development across teams and organizations. SAFe 4.5 aims to test ideas faster, deliver more quickly through continuous delivery, and simplify governance. Key elements include iterative planning and delivery, cross-team and cross-organization planning, centralized planning and decentralized decision making, and reporting on features and progress. Atlassian products like JIRA and Confluence can be used at the portfolio, program, and team levels to support the needs of each level in planning, tracking work, and managing dependencies.

1. © 2017 cPrime Inc., All Rights Reserved

2. Atlassian SAFe® 4.5 Solution
Leveraging Atlassian to support SAFe® 4.5

3. Presenter Background
Brandon Huff - Vice President Professional Services
PMP, PMI-ACP, SPC4, CSM, CSPO, Atlassian ACP
Brandon Huff has almost 20 years of experience managing large software
development, infrastructure,and process improvement projectsfor Fortune
500 companies. His experience as an Agile Coach has driven large
enterprise transformations with lasting Agile COE’s. Brandon has designed
and configured hundreds of Atlassian instances, pioneered the first
Atlassian University courses, and created the first JIRA SAFe solution.
He has helped companieslike Apple, Cisco, Oracle, NetApp, Ericsson,
VISA, Hitachi, Target, and more.
3

4. SAFe® 4.5 Big Picture
4
PROVIDED BY

5. SAFe® 4.5 Goals
5
• Test ideas more quickly
• Using the Lean Startup Cycle and Lean User Experience (Lean UX)
• Deliver much faster
• With Scalable DevOps and the Continuous Delivery Pipeline
• Simplify governance and improve portfolio performance
• With Lean Portfolio Management (LPM) and Lean Budgets

6. Key SAFe® Elements
SAFe®
Foundation
based on
iterative
planning and
delivery
Cross-team
and Cross-
organization
Planning
Centralized
planning and
decentralized
decision
making
Reporting on
features and
progress
Alignment of
requirements
and
traceability
Focus on
delivery of
business
value
6

7. Delivery &
Support
Planning &
Reporting
Strategy
SAFe® Organization & Hierarchy
Features
Portfolio Team
Program Team
Delivery Team
7
Large Solution
Team
Product &
Alignment
CapabilitiesStoriesEpic

8. Atlassian SAFe® 4.5 Approach
Exploration Implementation Deployment
Solution Kanban
Large Solution
Level Project
Portfolio
Level Project
1 2 3 4 5
Portfolio Kanban
Epic Issue Type
Capability Issue Type
Solution
Train
1 2 3
Team Scrum/Kanban
Story Bug
RiskSpike
Team
Level Projects
Exploration Implementation Deployment
Program Kanban
Program
Level Project
Feature Issue Type
Release on Demand
Confluence
Portfolio
Level Space
JIRA
Large Solution
Level Space
Program
Level Space
Team
Level Spaces
Reporting&Tracking
Roadmaps,Vision,
ValueStatement,
BusinessCases
Release
Trains
SolutionIntent,
SolutionContextPIObjectivies
PI 2 PI 3 PI n+1PI 1

9. Portfolio Team Needs
View, plan and track your organizations
most important initiatives across all strategic themes
Are we working on
the right things?
Where are we in
process of delivering
our initiatives?
Are we ready to start
on next initiative?
Where can
I find the business plan of
the initiative?
What are our
initiatives for ourmain
investment theme?
Can I see dashboard of
most importantmetrics?
9

10. Identify customer needs, prioritize/align features, and
develop the program Vision & Roadmap
Large Solution Team Needs
Any cross-team
dependenciesgetting
in the way?
What is in our next
solution demo?
Which features are we
deliveringin the next PI?
What functionality doare our
customers need?
Have we included key
teams in the context for
this solution?
What are we building?
10

11. Program Team Needs
Determine if the release date will be met,
test what-if scenarios, ensure the release date is met
Which cross-team
dependenciesare getting
in the way?
Where are we in
process of delivering
our features?
Are we going to
deliver in budgetand
on-time?
What are the detailsof this
feature? Are there multiple teams
working on it?
Can I see Program
dashboardof most
importantmetrics?
What percent of the
feature is complete?
11

12. Delivery Team Needs
Track and manage sprint commitments,
work assignment, and impediments to optimize velocity
Any cross-team
dependencies
getting in the way?
We have roomin the
sprint to take on next
item? Which one?
What have we
completed?
Do we have capacity to
take on more in this sprint?
What is our
remaining ToDo?
What discussionsdidour
offshore teamhave
yesterday?
What is our
velocity?
Let’s break thiswork
down…..what dowe need to
do and who is takingit?
12

13. THANK
YOU!
Contact us at:
atlassian@cprime.com
15