Know more, do less

Command Palette

Search for a command to run...

Know more, do less

incrementalism

UpdatedApril 5, 2024

•1 min read•View as Markdown

Neville Scheevel

Sr. Program Manager, Cloud Products & Governance at Warner Bros Discovery

Comments

Join the discussion

No comments yet. Be the first to comment.

More from this blog

Clearly communicate technical project updates using the Executive Charter as a dictionary

For project success, we need to deliver on leadership's vision. And since the Executive Sponsor has the final say, the Dev Team’s work needs to embrace that vision and demonstrate regular technical progress towards it. To ensure everybody is aligned,...

Jan 20, 2025·2 min read

Clearly communicate technical project updates using the Executive Charter as a dictionary

Streamline Knowledge Transfer using AI

This is one of the best use-cases for Generative AI A common scenario: Your IT talent lands a new job. They hand in their notice. Nobody has time to write documentation. The clock is ticking. How will you capture their tribal knowledge before they wa...

Oct 8, 2024·3 min read

Liar-liar Gantt chart on fire

Why Capacity Heat Maps beat Gantt charts

Jun 4, 2024·2 min read

When facing the complexities of a project how do you go about making sense of it?

Compressing complexity into something manageable

Mar 24, 2023·1 min read

When facing the complexities of a project how do you go about making sense of it?

AGILE CONVERSATIONS...

6 posts

TPM, agilist, Cloud product owner, process analyst, Generative AI enthusiast

It’s pretty simple. Most projects fail to meet estimates, and the reason we are estimating is so we can determine:

do we possess the resources to complete a project?
can we finish on time?
is the project even worth it?

But when a project is unlike anything the team has accomplished together, the early estimation will be a overly optimistic wild guess. What’s more, if a rigid cross-team timeline is built on our fictional estimates then we'll end up too far behind to allow for mid-course corrections.

📈

After all, adding people or resources to an already late project results in making the project even later.

So the solution is to measure all the "risk" upfront through lean experimentation. And by "risk" I mean the unknown bits that defy accurate estimation.

So, identify the unknowns, slice them into thin experiments, dedicate resources, time-box each experiment, and complete only enough until it is "knowable" then scale estimates accordingly.

#productivity #lean #agile

Archive
Privacy
Terms

Sitemap RSS