Leffingwell et al. 2015 Scaled Agile Inc.

SAFe ART Launch Pack: Organizational Readiness

No.

Item

Description

1.1

Planning Scope and Context

Is the scope (product, system, technology domains) of the

planning process understood? Have we identified our
Value Stream(s) and Agile Release Trains?

1.2

Release Train Engineer

Have we identified the Release Train Engineer? Does

he/she understand the scope of the role in preparing the
organization and preparing for the Release Planning
Meeting?

1.3

Planning Timeframe, iteration and release

cadence

Have we identified the release planning dates, the sprint

cadence, and the release (PI) cadence?

1.4

Agile Teams (SMs, POs)

Does each feature/component team have an identified

ScrumMaster and Product Owner?

1.5

Team makeup/ commitment

Are there dedicated developers and testers on every team?

1.6
1.7

System Team
Shared Program Resources

Has the System Team been identified and formed?

Have the Program Resources (DevOps, UX, Architecture,
etc.) who are part of the Release Train been identified?

1.8

Other Attendees

Do we know what other key stakeholders (IT, infrastructure

etc) should attend?

1.9

Agile Team Attendance

Are all team members present in person or are

arrangements made to involve them remotely?

1.10

Executives, Business Owners Participation

Do we know who will set the business context and present

the product/solution vision?

1.11

Business alignment

Is there reasonable agreement on priorities amongst the

business owners and product management?

1.12

Agile Project Management Tooling

Do we know how & where iterations, releases, stories,

tasks, status, burn down etc. will be maintained?

1.13

Development Infrastructure

Do we understand impact and/or plans on SCM continuous

integration and build environments?

1.14

Agile Technical Practices

Is there a strategy for unit testing and test automation?

Any other practice guidelines?

Leffingwell et al. 2015 Scaled Agile, Inc.

Y/N

Notes, Risks, Mitigations, etc.

Page 1 of 11

Leffingwell et al. 2015 Scaled Agile Inc.

SAFe ART Launch Pack: Team Summary

Team # Table #
1
2
3
4
5
6
7
8
9
10
11
12
n/a

Team Name

System Team
Shared Resources
(Architecture, UX,DevOps,
etc.)

Scrum Master

n/a
n/a

Product Owner

# On-Site Attendees # Off-Site Attendees

Breakout Room

n/a
n/a

n/a
Business Owners
n/a
n/a
n/a
Product Managers
n/a
n/a
Notes:
1.
Limit : 125 people, 12 teams maximum. More typically 50-75 people in 7-10 teams
2.
Breakout rooms may require teleconference equipment for remote team members
3.
Can typically keep 7-8 teams in the plenary session (auditorium) unless they have remote attendees that require video and audio

Leffingwell et al. 2014 Scaled Agile, Inc.

Page 2 of 11

Leffingwell et al. 2015 Scaled Agile Inc.

SAFe ART Launch Pack: Team Roster

Team #
1
Team A
1
Team A
1
Team A
1
Team A
1
Team A
1
Team A
1
Team A
1
Team A
1
Team A
2
Team B
2
Team B
2
Team B
2
Team B
2
Team B
2
Team B
2
Team B
2
Team B
2
Team B

Team Name

Leffingwell et al. 2014 Scaled Agile, Inc.

Role
Scrum Master
Product Owner
Developer
Developer
Developer
Tester
Tester
<role>
<role>
Scrum Master
Product Owner
Developer
Developer
Developer
Tester
Tester
<role>
<role>

Team Member Name

LastName, FirstName
LastName, FirstName

Geographic Location
City, Country
City, Country

LastName, FirstName
LastName, FirstName

City, Country
City, Country

Page 3 of 11

Leffingwell et al. 2015 Scaled Agile Inc.

SAFe ART Launch Pack: Program Roster

PI #
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
PI #
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2

Role
Release Train Engineer
Product Manager
Product Manager
Business Owner
Business Owner
System Team
System Team
System Team
System Team
DevOps
DevOps
DevOps
DevOps
System Architect
UX
Development Manager
Release Management
Executive (presenter)
Role
Release Train Engineer
Product Manager
Product Manager
Business Owner
Business Owner
System Team
System Team
System Team
System Team
DevOps
DevOps
DevOps
DevOps
System Architect
UX
Development Manager
Release Management
Executive (presenter)

Leffingwell et al. 2014 Scaled Agile, Inc.

Team Member Name

LastName, FirstName

Team Member Name

LastName, FirstName

Geographic Location
City, Country

Geographic Location
City, Country

Page 4 of 11

Leffingwell et al. 2015 Scaled Agile Inc.

SAFe ART Launch Pack: Content Preparation

No.

Item

Description

Responsibility

2.1

Scope, Context and

Organizational readiness
Established

Review items from Part 1

2.2

Final agenda

Final agenda with start and stop times, timeboxes, Release Train Engineer
speaker callouts, etc. Take into account timezone
differences if the planning meeting is spread
across multiple locations

2.3

Facilitator preparation

Facilitator understand context and mechanics of

event, and facilitator guidelines. For the first
Release Planning meeting, if the Release Train
Engineer is not an SPC, he or she will need to be
paired with and SPC in order to use the ART
Launch Pack

Facilitator/ Release Train

Engineer

2.4

Introductory Briefing

Establishes schedule, objectives, context,

requirements for session

Facilitator/ Release Train

Engineer

2.5

Executive Briefing

Defines current business context and investment

themes

Executive identified

2.6

Product Vision Briefing(s)

Briefings prepared by product managers.

Product Managers and
Handouts/backlogs prepared with supporting detail Business owners
(features, priorities, market reports, use cases, UX
guidelines, etc.)

2.7

Program Backlog

Top 10 features per product manager/owner. To

prepare, review Vision Storyboard training,
understand investment themes, and gain
alignment with product strategies.

Product Managers and

Product Owners

2.8

Architectural Vision Briefing

Communicate any new architectural epics and

system quality (nonfunctional) requirements

CTO/Architects, Security
Directors etc.

2.9

Development Practices Briefing Changes to standard practices, new tools (agile

project management tool, test automation,
continuous integration), expectations for the
"definition of done," etc.

Sr. Development
Management

2.10

Meeting notice

Release Train Engineer

2.11

Sprint and PI Meeting Schedule Based on Sprint and PI cadence, finalize calendar. Release Train Engineer
Teams Level: Sprint Planning, Demo, and Retro;
Program Level: PI Planning, Demo, Inspect &
Adapt, and Scrum of Scrums

Leffingwell et al. 2014 Scaled Agile, Inc.

Finalize agenda and send meeting notice to

attendees with venue, access requirements, etc.

Due Date

Status

Notes

All

Page 5 of 11

No.

Item

Description

Responsibility

Due Date

Status

Notes

Facilities Checklist for Each Location

3a.1

Facility Room(s)

Facilities roomy enough for all attendees with

separate breakout rooms if necessary (depending
on size of group). Note: ideally, some teams can
remain in the plenary session room

3a.2

Room Arrangement

Workshop setting. Tables seating entire teams (7+2). One table near the front for business owners.
Seats in back for observers.

3a.3

Facilities and Tech Support

Have contact information and service level

agreement for primary and secondary facilities
and tech support people.

3a.4

Room accessibility/security

Confirm room security protocol. If possible, have a

process for facility access before and after hours in
case teams stay to continue planning. It is highly
recommended to have access to the facility the
day before for setup.

3a.5

Refreshments and meal

arrangements

As appropriate based on venue, time, culture

3a.6

Internet access for participants If participants have internet access, establish

working agreements for laptop and tablet usage.
Note that powerstrips may be required depending
on internet access needs.

3a.7

Projection equipment

Projector available and tested. Screen large

enough and placed for easy viewing by all
attendees. Backup projector bulbs recommended

3a.8

Audio System

If there are more than 30-40 attendees, a tested

audio system is required. The system should also
have an input for PC audio (used for ART Launch
training videos).

3a.9

Microphones

When an audio system is used, at least one lapel

and one handheld microphone are required. Two
handheld microphones are highly recommended
for larger groups.

Easels

Two easels for the presenter. If teams do not have

wall space to adhere flipchart paper (3 sheets wide
by 2 sheets high) they will need easels or other
surfaces.

3a.10

Additional Communication Checklist Items if Multiple Locations

Leffingwell et al. 2014 Scaled Agile, Inc.

Page 6 of 11

No.

Item

Description

3b.1

Internet connectivity

If meeting is distributed, a dedicated high

bandwidth internet connection is highly
recommended for full group and team video
conferencing. A wireless access point will be
needed for teams using PCs and tablets for
videoconferencing with remote team members.

3b.2

Remote communications
arrangement

Multiple connectivity options to fully engage

remote participants (phone, Skype, FaceTime,
WebEx, etc.)

3b.3

Video channel

Reliable, thoroughly tested video channel between

locations. Video channel should allow for
simultaneous two-way video between two
locations. Each should be available 1 hour before
the start of each day for testing and
troubleshooting.

3b.4

Audio channel

Reliable, thoroughly tested audio channel between

locations. As with video, it should be available 1
hour before the start of each day for testing and
troubleshooting.

3b.5

Hardware for video

conferencing with remote
location(s)

Videoconferencing between locations often

requires a separate computer, video camera,
projector, and screen to allow each location to be
seen by the other party. Some facilities may have
dedicated videoconferencing equipment.

3b.6

Additional microphones

Additional handheld microphones will be needed

for passing. Keep in mind polite protocol for
distributed meetings: participants should not
speak unless they have a microphone.

3b.7

Presenting channel

Webex or other tool used to share applications or

screens between locations. Not to be confused
with the video channel for videoconferencing this
totally separate channel.

3b.8

Emergency audio channel

Reliable phone/polycom or other connection

(preferably NOT via internet) to ensure
communication in case nothing else works.
Important: know the exact phone numbers and
keep the devices running and available.

3b.9

Session connectivity protocol

Set of arrangements between Tech people on both

ends allowing to ensure timely readiness of all
equipment and issue communication/resolution in
case of failure.

Leffingwell et al. 2014 Scaled Agile, Inc.

Responsibility

Due Date

Status

Notes

Page 7 of 11

No.
3b.10

Item

Description

Dedicated IT personnel

Dedicated IT personnel available on each end that

fully understand, own and manage the setup so
that the facilitators and the groups may fully
concentrate on process objectives only. IT
personnel should be available 1 hour before the
start of each day for testing and troubleshooting.

Leffingwell et al. 2014 Scaled Agile, Inc.

Responsibility

Due Date

Status

Notes

Page 8 of 11

Leffingwell et al. 2015 Scaled Agile Inc.

SAFe ART Launch Pack: Supplies

Team Items

(numbers generated from "Parameters" worksheet tab)

Number Notes

Unprinted Comments

3M Post-it Super Sticky Meeting Flip Chart Paper

(White)

22

2 per team and 2 for the presenter and program board.

Post-it pack: 3x5, Blue

20

Super Sticky Ultra Notes (and not the dispensor "accordian" style)

Post-it pack: 3x5, Red or Pink

20

Super Sticky Ultra Notes (and not the dispensor "accordian" style)

Post-it pack: 3x5, Orange

20

Super Sticky Ultra Notes (and not the dispensor "accordian" style)

Post-it pack: 3x5, Green

20

Super Sticky Ultra Notes (and not the dispensor "accordian" style)

Post-it pack: 3x5, Yellow

20

Super Sticky Ultra Notes (and not the dispensor "accordian" style)

Post-it pack: 3x5, Purple

20

Super Sticky Ultra Notes (and not the dispensor "accordian" style)

Planning Poker Card Sets

100

There are usually multiple sets in a pack. Typically ordered by

instructor from
http://store.mountaingoatsoftware.com/products/planning-pokercards-burndown-design

Sharpie Markers (fine point)

Flip chart marker set (various colors)
Name tents

50
11
100

5 per table
1 per table plus 1 for the facilitator
1 per person

Shared Items
Program Feature Board
Spool of Red Yarn
Scissors
Rolls of blue painters tape

Number
1
1
3
3

Notes

Unprinted Comments

Can be created with flipchart paper, printed, etc.

For program board dependencies
Shared
For taping the program board and other miscellaneous things

Unprinted Comments

Game Supplies
Scrum Balls for the Scrum Ball Game

100

Typically ordered by instructor from http://www.identitylinks.com/stress-relievers/sports/rugby-ball-stress-reliever

These are if you are teaching SAFe ScrumXP

Pennies for the lean flow Penny Game

100

10 pennies per table are needed. Consider putting in a Zip Lock

Bag for easy distribution

These are if you are teaching SAFe ScrumXP

Leffingwell et al. 2014 Scaled Agile, Inc.

Page 9 of 11

Leffingwell et al. 2015 Scaled Agile Inc.

SAFe ART Launch Pak: Supplies Parameters

Parameters for Calculations

Count

Number of total team tables

Number of total team members
Number of guests
Remote locations to video in

10
100
40
2

Leffingwell et al. 2014 Scaled Agile, Inc.

Comments

Leffingwell et al. 2014 Scaled Agile, Inc.