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 219
article thumbnail

Release planning and predictable delivery

Scrum.org

TL;DR; Without working software, you can’t build trust and you don’t know when you will get the next piece of working software. Once you accept this, and quality becomes non-negotiable, your Dev e lopers can focus on creating usable increments of working software. Professional Developers create working software.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Are These DevOps Obstacles Getting in the Way of Your Agile Transformation?

Leading Agile

As more and more companies scramble to untangle the code of their monolithic legacy software and get it into the cloud, strategic priorities are shifting. Want the Deck Text HIDDEN to 33777 Video Transcript We will run into times where packing software makes it harder for us to transform the skills of our staff and external vendors.

article thumbnail

Unlocking the Power and Mastery of Development Approach and Life Cycle

Project Pulse Journal

The challenge of integrating an intricate methodology into your project execution might be intimidating, yet it is essential to optimize project delivery and align with business and stakeholder values while avoiding unnecessary complexity in your workflow. It also supports cadence synchronization for the creation of project deliverables.

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

Troubleshooting in Lean-Agile Development

MPUG

When facing these challenges, Lean-Agile approaches have certain inherent or built-in mechanisms and execution best practices. 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 the feature is complete, it can be delivered.

Lean 64
article thumbnail

Don’t Blame Agile for Bad Agile

Velociteach

Since only a third of the features in enterprise software are commonly used, delivering incrementally reduces waste. People may be able to execute the practices but will not know why. Teams conform to a 2-week delivery cadence, creating a standard operating rhythm and predictability. Agile practices are not mechanical.