Remove Cadence Remove SCRUM Remove Software Review Remove Sustainability
article thumbnail

How We Reduced Cycle Time from 164 Days to 8 Days in 6 Months

Scrum.org

In December 2020, my friend Adrian Galarza and I delivered a Scrum.org Scrum Pulse Webinar - A Cycle Time Journey: 164 to 8 Days in 6 Months that summarized the journey of Adrian’s Scrum Team. Due to horrible time-management on my part, we could not answer all the questions in the webinar, so we are answering them in this blog instead.

Cadence 216
article thumbnail

5  misconceptions about Scrum's Sprint Event

Scrum.org

Many well-meaning Scrum practitioners have misconceptions about Scrum, which sometimes leads to creating “rules” that do not exist in the framework. Scrum is deliberately incomplete because the framework is used in complex environments where simple best practices won’t fit all situations.

SCRUM 183
Insiders

Sign Up for our Newsletter

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

article thumbnail

Minimal measures for minimal stability in a complex environment

Scrum.org

Scrum, in its more general definition, is a simple framework to help us address complex challenges. Product development is the subset of complex problem domains where Scrum took root first; by explicitly acknowledging software and new product development to be complex work, serving to deliver complex products in complex circumstances.

Cadence 202
article thumbnail

Unlocking the Power and Mastery of Development Approach and Life Cycle

Project Pulse Journal

This domain facilitates strategic alignment, optimized delivery cadence, methodology customization, increased flexibility, and improved risk management. The desire for a project management framework that sustains deliverability, supports the required cadence, and remains faithful to an adaptable methodology is now within reach.

article thumbnail

Troubleshooting in Lean-Agile Development

MPUG

An example of this type can be the Scrum framework. It’s usually based on a cadence. As shown in the above figure, there is no regular timeboxed iteration, but incremental delivery can happen in cadence. When you fire a gun in the dark, it’s difficult to aim due to the lack of light. Flow-based Lean-Agile.

Lean 64
article thumbnail

SAFe Simply Explained (Part 1): Core Competencies and Principles

Inloox

In most cases, however, previous experience is based only on the small-scale use of Scrum or other agile methods in individual departments. What usually started in software development can now be extended to the entire company and thus, change the way people collaborate. But it’s not that easy.

article thumbnail

How do you implement SAFe agile in your organization?

Agilemania

The groundwork for SAFe was formed in 4 knowledge areas – agile software development, lean product development, systems thinking, and DevOps. SAFe contains a combination of principles, processes, and best practices that help large organizations in easy adoption of agile frameworks including Lean, Kanban, and Scrum. Code Quality.

Agile 98