article thumbnail

Troubleshooting in Lean-Agile Development

MPUG

Many project managers utilize a Lean-Agile approach when there is high change or churn in project requirements, significant lack of clarity in scope, high complexity to their projects, and/or a larger number of risks associated with such. Two Lean-Agile Types. Iteration-based Lean-Agile. Flow-based Lean-Agile. Flow-based.

Lean 64
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

Beyond Mechanical Scrum

Scrum.org

The teams at his company had well established cadences for their Scrum events; well-oiled Daily Scrums that are done within 15 minutes and result in transparency of what the team will do for the next 24-hours. They are releasing software after every 2-week sprint. Welcome to Lean Startup. All straight out of XP.

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

How Do you Make a Retrospective an Interesting Session?

NimbleWork

Many teams lean into retrospectives to help uncover areas where processes could be slicker, where engagement hasn’t been as effective as it could and to look for areas of improvement. Get Software Tools that Support the Retro Process Make sure everyone has access to software tools designed specifically for retros.

Cadence 109
article thumbnail

11 Proven Stakeholder Communication Tactics

Scrum.org

Stakeholder communication: It is simply not enough for an agile product development organization to create great code and ship the resulting product like a clockwork. The two formal Scrum events that come to mind are: Sprint Reviews. The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog.

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.