Organizing the ART and PI Preparation Flashcards

1
Q

What are some characteristics of an effective ART organization??

A
  • Has cross-functional teams
  • The ART has:
    -► A virtual organization of 5–12 teams (50–125+ individuals)
    ► Synchronized on a common cadence (a PI)
    ► Aligned to a common mission via a single ART Backlog
  • Teams on the ART are organized for Flow
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

SAFe recommends monitoring six different Flow Metrics throughout the various levels of the organization to measure flow and find areas of improvement. What are those Metrics?

A

Flow Distribution
Flow Velocity
Flow Time
Flow Efficiency
Flow Predictability
Flow Load (measure WIP)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What kinds of decisions can be decentralized?

A

Some decisions are:
- infrequently made,
- long-lasting, or
- provide significant economies of scale.

These decisions should remain centralized. Decentralize everything else.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the purpose of the System Team?

A

The primary reason to have a System Team is to increase the ART’s speed, quality, and productivity without jeopardizing the team’s ability to deliver new solution value.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is PI Planning? What is its purpose?

A

PI Planning is a cadence-based event that serves as the heartbeat of the Agile Release Train (ART), aligning all teams on the ART to a shared mission and Vision.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the inputs to PI planning?

A

Business Context
Roadmaps and Vision
top 10 Features

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

PI Planning starts with what (what event?_

A

PI Planning starts with the event briefings.

These briefings are delivered by Business Owners and key stakeholders and provide a clear Vision and context for the upcoming PI.

Everyone receives the same message to create Alignment during the PI Planning event.

A successful PI Planning event results in agreement across all teams and their respective Business Owners on the goals for the next PI,

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are the outputs for PI Planning?

A

Committed PI Objectives:

PI Objectives are created by each team, and business value for these is assigned by the Business Owners.

The Program Board:

The Program Board is updated, showing Feature delivery dates, dependencies between teams, and relevant events and Milestones.

Risks: (Not identified as a primary output) but its addressed in the PI planning process

Program Risks are identified and either resolved, owned, accepted, or mitigated. Teams leave PI Planning with a committed set of PI Objectives and with a good understanding of how they will work with one another across the ART to resolve dependencies so that the whole ART is contributing to meeting business goals.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are some of the main reasons for PI planning?

A
  • Create alignment on what to build next
  • Agree on goals for the next PI
  • Ensure visibility to planned, sequencing of work, dependencies, and risks
  • Match demand to capacity by allowing teams to plan their own work
  • Decentralize decisions
  • Gain commitment from everyone on the plan
  • Have the people doing the work plan and commit to the work
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are some of the benefits of PI planning?

A
  • Establish face-to-face communication across all team members and stakeholders
  • Build the social network the ART depends upon
  • Align development to business goals with the business context, Vision, and team and ART PI Objectives
  • Identify dependencies and foster cross-team and cross-ART collaboration
  • Provide the opportunity for ‘just the right amount of architecture’ and Lean UX guidance
  • Match demand to capacity and eliminate excess work in process (WIP)
  • Foster fast decision-making–you have all people needed to plan your PI at the PI Planning event
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Which represent the work for the Agile Release Train?
o Features
o Epics
o Stories
o Capabilities

A

Features represent the work for the Agile Release Train

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

The active participation of this group in the PI Planning provides an essential Guardrail on budgetary spending. What is that group?

A

Business owners

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

PI Event planning start with what? What is the purpose of starting with this?

A

The day starts with the content presentations, creating a shared understanding of the business context and the boundaries that the teams are planning the PI inside.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

In the First break out session ART teams do what?

A

The teams create draft plans for each Iteration,
write draft PI Objectives, and identify ART PI
Risks and impediments.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

For PI Planning to be successful preparation is needed in these 3 areas:

A

Organization Readiness -
Content Readiness
Logistical Readiness

Organization Readiness: there must be strategy alignment among participants, stakeholders, and Business Owners. Critical roles are assigned. Do we have Planned Scope and Context, Business Alignment, Agile teams and assigned roles?

Content Readiness: important to have a clear vision and context so that the right stakeholders can participate (3 briefing ready for morning day1?)

Logistical Readiness: Rooms, food,Tools and machines ( audio, supplies etc)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Identify some Anit-patterns associated with PI Planning.

A

** Lack of Feature Preparation**
Solution: Ensure Features and Enablers meet the DoR.

Leverage the ART Kanban to visualize progress toward Feature readiness and establish ongoing flow for refining the ART Backlog.

Encourage the teams to set aside time in each Iteration to understand and refine Features and Enablers for the upcoming PI.

**Product Management or System Architect not available **

Work with Product Management and the System Architect to help them understand the importance of being available for pre-planning work and activities. Ask how you can help them prepare.

** Business Owners aren’t available or don’t see value in attending **

Solution: Use materials from the PI Planning toolkit. Leverage the PI Planning Overview for Stakeholders deck to help them understand their role in the PI Planning event.

** Not protecting the Innovation and Planning (IP) Iteration **

Solution: Coach the teams to protect the IP Iteration
Coach the teams to protect the IP Iteration, so they have time to focus on PI Planning preparation.