Remove why-pi
article thumbnail

“Agile Is Just for Software” and other Scrum Myths

Scrum.org

That is why Scrum can be used in so many different contexts: because of its flexibility and the fact that Scrum provides just enough - but not too much - structure to enable teams to work together to deliver value. This is why Scrum myths are such a problem. That is the power of Scrum. That’s a question that only the team can answer.

SCRUM 179
article thumbnail

The Transformation Journey: Lessons Learned

Planview

First, why scale Agile in the first place? Why Make the Transformation Journey? This is why the making the transformation journey toward agility is so critical. SAFe has a mechanism for continuous planning called Program Increment or PI planning. Every 10 weeks, we do PI planning for the next quarter.

Cadence 148
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

SAFe Simply Explained (Part 2): Basic Idea and Most Important Terms

Inloox

This is why we want to briefly summarize the basic concept as well as the most relevant terms that are relevant for the initial understanding of the method in this blog post. Program Increment (PI). PIs are typically 8 - 12 weeks long. A PI is to an Agile Release Train what an iteration is to the agile team. Agile Teams.

Lean 173
article thumbnail

SAFe Easy Explained (Part2): Basic Idea and Most Important Terms

Inloox

This is why we want to briefly summarize the basic concept as well as the most relevant terms that are relevant for the initial understanding of the method in this blog post. Program Increment (PI). PIs are typically 8 - 12 weeks long. A PI is to an Agile Release Train what an iteration is to the agile team. Agile Teams.

Lean 156
article thumbnail

To Fix Your OKRs – Go Back to First (Familiar) Principles

Scrum.org

Why does initiative/autonomy matter so much? To inform about why rather than prescribe what/how. The connection can be reinforced as part of the “Why Now” for each objective. That’s a shame because OKRs have huge potential if used effectively. So let’s go about fixing your OKRs! . Let’s start with the basics.

Cadence 199
article thumbnail

Agile OKRs to Measure Improvement in Flow and Value Outcomes OKRs

Scrum.org

Without robust empirical measures, organisations tend to turn to the symbols they can see, such as team happiness, velocity, throughput, visualisation of work by using post-it notes, attendance at Agile events, or number of PI planning events held. This is a useful template to build your Agile OKrs. Describe the outcome as a hypothesis.

Agile 215
article thumbnail

Improving SAFe Through Professional Scrum

Scrum.org

So, again, why do so many Scrum practitioners, trainers, and thought leaders consider it unsafe and a Scrum-but? Why don't we just have a Program Increment that is at the same length of the team-level increment? Why do we even need this big room planning in the first place? I hear a lot of questions and claims. Kind of hard.

SCRUM 140