article thumbnail

Choosing a Development Approach

International Institute for Learning

Product variables include innovation, scope stability, requirements certainty, ease of change, and delivery cadence. Delivery cadence considers if your project has one main deliverable or can be decomposed into multiple smaller deliverables. Delivery cadence. How do you know which approach to use? Bulletin Board. Innovation.

Cadence 52
article thumbnail

The Agile Fluency model

Henny Portman

The Agile Fluency model, developed by Diana Larsen and James Shore in 2012 and substantially updated in 2018, is a framework to help teams understand their current position and to help them develop an individual road map. Delivering teams deliver on the market cadence (agile sustainability).

Agile 85
Insiders

Sign Up for our Newsletter

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

article thumbnail

Compendium of Works to Increase Probability of Project Success

Herding Cats

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Risk Management (#RM). Business, Technical, Systems, Risk, and Project Management. Five Immutable Principles of Digital Transformation Project Success - PMI San Diego Chapter , 11 July 2018. Management Processes (#MP).

article thumbnail

Webinar Recap: Introduction to the Power BI Suite

MPUG

And having that standardized across all of our projects and programs in an organization again is key so that we compare apples with apples rather than comparing apples with pears is often we do when we have a subjective view perhaps of what a risk might be or whether something’s red and blue of green. We have the Power BI Gateway.

article thumbnail

What’s Worse Than Not Automating Your Software Delivery Pipeline?

Leading Agile

But there’s a risk that people will get excited about automation and get ahead of themselves. Circa 2018 this might seem rather obvious, but one aspect of automating a software delivery pipeline is to automate the build process for the application. It seemed a high-risk situation to me. Is that really a big deal?