Remove 2019 Remove Cadence Remove Lean Remove Meeting
article thumbnail

The Transformation Journey: Lessons Learned

Planview

We wonder if many enterprises even did annual planning for 2021: How many organizations are still running off the plan they created in 2019? A continuous planning cadence – quarterly, monthly, or even weekly – enables organizations to be ready to move fast when change occurs, or new opportunities appear on the horizon.

Cadence 148
article thumbnail

Mastering the (new) Agile Coaching Mindset for the 4th Industrial Revolution (4IR)

International Institute for Learning

The common thread from all the 4IR discussions is that predicting the optimal delivery approach for realizing the value propositions of new and existing goods and services, as well as leveraging 4IR technologies to meet customer’s rapidly evolving preferences, is in itself, unpredictable. Under Tim Cook, Apple Inc.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Managing A Hybrid-ScrumBan Project with MS Project Agile

MPUG

Many times, managing a Hybrid-Agile project with a sole Lean-Agile approach doesn’t meet the needs of an organization, the expectations of stakeholders, required delivery frequency of customers, or address uncertainties associated with engineering work. As always, your comments, feedback, and suggestions are welcome. References. [1]

Agile 111
article thumbnail

Sprint Burndown and Burnup Charts with MS Project Agile

MPUG

As I’ve explained in a previous article, flow-based Agile can benefit from cadences. However, the Remaining Cumulative Work line continues to slide further and finally meets the time axis on the final day of the Sprint. The content is taken from my new course, Mastering MS Project 2019 Agile. Building a Sprint Burnup Chart.

Agile 75
article thumbnail

Questioning Agile Dogma

Leading Agile

How can the same principle be a good idea in 2002 and a bad idea in 2019? As the deadline for a given project loomed, the teams went into “death march” mode, in which they attempted to compensate for all the wasted time up to that point (as well as to try and meet unrealistic expectations) by working themselves to exhaustion.

Agile 115