Remove Cadence Remove Engineering Remove Sustainability Remove Technical Review
article thumbnail

Troubleshooting in Lean-Agile Development

MPUG

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. Developers, with all due respect to them, are generally optimistic people.

Lean 64
article thumbnail

Agile Unplugged: EP 02 | Mike Cottmeyer and Dennis Stevens

Leading Agile

– I was working in my office down in technology Parkway. You get super clear backlogs, you find out what the real cadences you’ve finished work that you start. Champion was in there designing, he realized his shortcomings, to business process re engineering. And BPR was about the technology. – Yeah.

Agile 63
Insiders

Sign Up for our Newsletter

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

article thumbnail

Sprint Anti-Patterns

Scrum.org

Every activity required to achieve the Product Goal, such as Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, occurs within Sprints. This also applies to refactoring parts of the tech stack, exploring new technology that might be useful, fixing some bugs, or sharing knowledge with fellow teammates.

article thumbnail

28+2 Sprint Anti-Patterns Holding Back Scrum Teams

Scrum.org

All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints. This also applies to refactoring parts of the tech stack, exploring new technology that might be useful, fixing some bugs, or sharing knowledge with fellow teammates.

SCRUM 160
article thumbnail

Comparing Nexus and SAFe - Similarities, Differences, potential synergies

Scrum.org

PS Some people feel the term Sprint isn’t the best choice if we want to emphasize “sustainable pace”. . Empiricism via working integrated increments every Sprint - System Demo & Nexus Sprint Review meeting a common Definition of “Done”. Nexus Sprint Goal - Program PI Objectives - just at different cadence/frequency. Nexus - ART.

Cadence 137
article thumbnail

Compendium of Works to Increase Probability of Project Success

Herding Cats

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Business, Technical, Systems, Risk, and Project Management. Table of Contents (Click the Name to go to Section).

article thumbnail

Questioning Agile Dogma

Leading Agile

I’d like to consider the following in this post: Sustainable Pace. Sustainable Pace. By setting a sustainable pace for the work, teams were able to maintain a steady rate of delivery, leading to greater predictability and hence easier planning. Note: sustainable is good; sustained is not.). Stable Team.

Agile 99