article thumbnail

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

Scrum.org

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. You might get more value from reading this blog if you watched the recording and reviewed the slides that are available on the webinar page - A Cycle Time Journey: 164 to 8 Days in 6 Months.

Cadence 217
article thumbnail

How Do you Make a Retrospective an Interesting Session?

NimbleWork

So we want to include agile retros in the general cadence of the project lifecycle for iterative projects, whether you meet in person or virtually – but that regular cadence brings its own challenges. You can avoid that and keep the pace of the meeting high if you use software, even if you are all in the same room.

Cadence 109
Insiders

Sign Up for our Newsletter

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

article thumbnail

Review People Over Process

Henny Portman

Furthermore, neither agile or scrum contemplates how the agile team should be connected to a larger organization and to external partners who will likely have differing development processes and cadences. It puts the focus on the software and the related business processes in a powerful way by using different scenarios. Conclusion.

article thumbnail

Scaling Agile Practices – Improve Business Outcomes

Agilemania

Develop on Cadence; Release on Demand. In SAFe®, this is known as Develop on Cadence, a coordinated set of practices that support Agile Teams by providing a reliable series of events and activities that occur on a regular, predictable schedule. Agile Team and Agile Release Train Cadences. Release on Demand.

Cadence 98
article thumbnail

A Review Of Scrum For Kanban Teams

Digite

First off, I have to say that I’m not 100% certain how I feel about Yuval’s blog post. It also encourages everyone to review/adopt the values (in Scrum language) that can help software development teams succeed in building software. They will ship increments of software on a cadence or on demand.

article thumbnail

The Increment Is Dead

Scrum.org

If you’re a veteran of the software industry, you probably remember those days where we released to production/GA every couple of months. When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. Can it also be a release cadence?

Cadence 134
article thumbnail

The Sprint Increment Is Dead

Scrum.org

If you’re a veteran of the software industry, you probably remember those days where we released to production/GA every couple of months. When we say “Working Software” in the Agile Manifesto, we don’t mean just “It is working and we tested it meets our acceptance criteria and our definition of Done”. Can it also be a release cadence?

Cadence 127