Run Projects That Deliver

Achievement of project completion within schedule, budget, and quality/requirements constraints—the traditional 'iron triangle' of programmatic performance. (Reconciling complexity, value, and organizational capability.)

started 0 · finished 0 (claimed) · not yet measured (verified) · no data (n<5)

Derived from: Run Projects That DeliverT1

Ordered tasks (41) — this is what a project auto-creates

#1Apply structured project-management practices as the foundation for delivery controlHighTo Do
The adoption of established PM methods as the root cause behind clarity, control, engagement, and sponsorship downstream.
Assignee: Unassigned · due 0 days after project start · takes 14 days
#2Define the project scope in writing before work begins and get sign-offHighTo Do
Lock down what the project actually is—goals, boundaries, deliverables, and who owns what—before work begins. You get the artifacts and the conversations that make ambiguity impossible.
Assignee: Unassigned · due 14 days after project start · takes 14 days
#3Build a credible plan with evidence-based estimates and sequenced workHighTo Do
Turning a defined project into a credible plan: decomposing work, sequencing dependencies, estimating with data instead of optimism, and resourcing realistically.
Assignee: Unassigned · due 28 days after project start · takes 14 days
#4Complete sufficient definition and design before authorizing full project fundingMediumTo Do
How much definition, scoping, and design must be complete before you authorize full funding—and how to gauge whether the front end is ready.
Assignee: Unassigned · due 42 days after project start · takes 7 days
#5Reach a documented, shared understanding of goals and success criteria with all stakeholdersHighTo Do
Reach a genuine shared understanding of goals, priorities, and success criteria across stakeholders and the team.
Assignee: Unassigned · due 49 days after project start · takes 14 days
#6Correct for optimism bias and strategic misrepresentation in estimates and commitmentsLowTo Do
Address why your estimates are systematically wrong in one direction. It separates the honest cognitive bias from the deliberate lowballing—and shows both corrode delivery.
Assignee: Unassigned · due 63 days after project start · takes 3 days
#7Track project performance against baselines and forecast outcomes at every reviewHighTo Do
Track performance against baselines so you can forecast where the project is heading—not just report where it's been.
Assignee: Unassigned · due 66 days after project start · takes 14 days
#8Operate a change-control process that welcomes valuable scope additions and blocks creepMediumTo Do
Distinguishes valuable scope discovery from corrosive creep, and gives you a change-control process that welcomes the first while blocking the second.
Assignee: Unassigned · due 80 days after project start · takes 7 days
#9Identify, assess, and mitigate risks continuously rather than only at kickoffHighTo Do
See problems before they arrive—'flying ahead of the plane'—by identifying, assessing, and mitigating risks continuously rather than at a kickoff workshop.
Assignee: Unassigned · due 87 days after project start · takes 14 days
#10Identify every stakeholder, understand their needs, and involve them at the right cadenceHighTo Do
Identify who has a stake, understand what they actually need, and involve them at the right cadence so surprises don't detonate at delivery.
Assignee: Unassigned · due 101 days after project start · takes 14 days
#11Make all work, progress, and impediments visible to everyone who needs to actMediumTo Do
Make all work, progress, and impediments visible to everyone who needs to act on them. You learn what to expose and how saturation differs from mere reporting.
Assignee: Unassigned · due 115 days after project start · takes 7 days
#12Catch and clear obstacles before they become crises through standing impediment managementMediumTo Do
Catch and clear obstacles before they metastasize into crises. You learn to run impediment management as a standing operational function, not an occasional rescue.
Assignee: Unassigned · due 122 days after project start · takes 7 days
#13Assess team capability against the project's demands and close the gaps before they become delivery risksLowTo Do
Why the same management process yields different results depending on who is running it. It positions team capability as the amplifier or dampener of your PM practices.
Assignee: Unassigned · due 129 days after project start · takes 3 days
#14Design safety, health, and environmental management into the project from the startMediumTo Do
How safety, health, and environmental management is designed into the project rather than inspected onto it. It connects SHE practices directly to whether the project can be called a success at all.
Assignee: Unassigned · due 132 days after project start · takes 7 days
#15Execute the plan consistently until the work is genuinely doneMediumTo Do
Focus on about the unglamorous act of doing what the plan says, consistently, until the work is genuinely done. It distinguishes a good plan from a plan that actually gets executed.
Assignee: Unassigned · due 139 days after project start · takes 7 days
#16Deliver scope, schedule, and budget targets simultaneously without silent trade-offsHighTo Do
The classic iron triangle—schedule, budget, and quality—as the baseline measure of programmatic delivery. It shows what feeds this outcome and where the tensions between the three constraints resolve.
Assignee: Unassigned · due 146 days after project start · takes 14 days
#17Lead the project through credibility and influence rather than positional authorityHighTo Do
Focus on about leading a project without owning the reporting lines—earning credibility, influence, and willing followership through character and capability rather than title.
Assignee: Unassigned · due 160 days after project start · takes 14 days
#18Build a committed team that owns the outcome and resolves conflict productivelyHighTo Do
Build a team that trusts each other, owns the outcome, and resolves conflict productively—the difference between a group of assigned people and a committed team.
Assignee: Unassigned · due 174 days after project start · takes 14 days
#19Build a team environment where speaking up with concerns or bad news is safe and expectedLowTo Do
Build the shared belief that speaking up—with concerns, questions, or bad news—is safe rather than career-threatening.
Assignee: Unassigned · due 188 days after project start · takes 3 days
#20Size the delivery team at 5–9 members with all needed skills and genuine decision authorityMediumTo Do
Size and empower a delivery team so it can actually own its work. You learn why the 5-9 range and cross-functional composition are load-bearing, not cosmetic.
Assignee: Unassigned · due 191 days after project start · takes 7 days
#21Implement Scrum or an equivalent iterative framework with its roles, events, and artifacts intactHighTo Do
This is your operating core: the roles, time-boxed events, and artifacts that turn iterative intent into a repeatable rhythm. You learn what Scrum actually prescribes versus what teams invent.
Assignee: Unassigned · due 198 days after project start · takes 14 days
#22Keep the backlog continuously ordered by value and risk so the team always works on what matters mostMediumTo Do
Shows the Product Owner how to keep the backlog continuously ordered by value and risk. You learn what 'value-based' rules out and how ordering differs from categorizing.
Assignee: Unassigned · due 212 days after project start · takes 7 days
#23Deliver working increments frequently and use honest inspection to steer the projectMediumTo Do
How frequent working increments and honest inspection create a learning loop that steers the project. You learn to treat delivery as an empirical process, not a plan-execution one.
Assignee: Unassigned · due 219 days after project start · takes 7 days
#24Run retrospectives that produce and implement process improvements every cycleMediumTo Do
The retrospective discipline and the mindset behind it: treating your process as a product you relentlessly refine. You learn to make improvement systematic rather than aspirational.
Assignee: Unassigned · due 226 days after project start · takes 7 days
#25Concentrate team effort on one goal at a time and eliminate activity that adds no valueMediumTo Do
Concentrating effort on one essential goal at a time and stripping out activity that doesn't add value. You learn why focus is a throughput decision, not a discipline preference.
Assignee: Unassigned · due 233 days after project start · takes 7 days
#26Measure team velocity as a forecasting and improvement signal, not a performance scorecardMediumTo Do
Team velocity as a forecasting and improvement signal—the rate of genuinely completed work per cycle. It shows what raises it and how it converts into value.
Assignee: Unassigned · due 240 days after project start · takes 7 days
#27Measure and act on stakeholder and customer satisfaction throughout the project, not just at closeoutHighTo Do
Address the human verdict on your project—whether the people who matter feel the deliverable and results met what they expected.
Assignee: Unassigned · due 247 days after project start · takes 14 days
#28Use short iterations and frequent inspection to reduce risk exposure and improve predictabilityMediumTo Do
How short iterations and frequent inspection buy you predictability and shrink your risk exposure. It reframes iteration as a risk-management strategy, not just a delivery cadence.
Assignee: Unassigned · due 261 days after project start · takes 7 days
#29Secure and activate executive sponsorship that clears obstacles and delivers timely decisionsMediumTo Do
Secure and activate the executive backing that clears obstacles, protects priority, and delivers timely decisions.
Assignee: Unassigned · due 268 days after project start · takes 7 days
#30Build the organizational PM capability that makes each project smarter than the lastMediumTo Do
Address the capability that lives above any single project—standard processes, a PMO, tooling, and the knowledge transfer that lets each project start smarter than the last.
Assignee: Unassigned · due 275 days after project start · takes 7 days
#31Select and develop project leaders whose cognitive and emotional traits fit the work's complexityLowTo Do
Examine the dispositional traits—breadth of orientation, openness, emotional intelligence, and experience—that shape how effectively a person can lead projects.
Assignee: Unassigned · due 282 days after project start · takes 3 days
#32Measure team happiness and design for autonomy, mastery, and purpose as leading indicatorsMediumTo Do
Treats team happiness—grounded in autonomy, mastery, and purpose—as a leading indicator you can read and influence before performance changes show up in the numbers.
Assignee: Unassigned · due 285 days after project start · takes 7 days
#33Impose aggressive constraints to force focus and apply FIRE values to every scope decisionLowTo Do
Makes the counterintuitive case for imposing aggressive limits—on budget, time, size, features—to force focus and creativity. You learn how FIRE (fast, inexpensive, restrained, elegant) values sharpen decisions.
Assignee: Unassigned · due 292 days after project start · takes 3 days
#34Manage the creative front end by separating divergence from convergence as deliberate phasesLowTo Do
Managing the creative front end—moving deliberately from generating many options to converging on one refined solution. You learn to keep divergence and convergence as separate, disciplined phases.
Assignee: Unassigned · due 295 days after project start · takes 3 days
#35Design shock-absorption and adaptability into the project so disruptions don't derail deliveryMediumTo Do
Building a project's capacity to absorb change and shocks without derailing. You learn what makes resilience a designed property rather than a matter of luck or heroics.
Assignee: Unassigned · due 298 days after project start · takes 7 days
#36Calibrate the level of PM rigor to the project's actual complexity and uncertaintyMediumTo Do
How a project's scale, novelty, uncertainty, and urgency should change how much structured management you apply. You learn to read complexity as a dial, not a fixed trait.
Assignee: Unassigned · due 305 days after project start · takes 7 days
#37Choose the contract and delivery model that pre-wires the right incentives and collaboration patternsMediumTo Do
Shows how the contractual and procurement structure you choose pre-wires the incentives, collaboration patterns, and safety accountability of everyone on the project. You will see why the deal terms are a design decision, not paperwork.
Assignee: Unassigned · due 312 days after project start · takes 7 days
#38Build and verify the systems integration capability that makes separately-built components work as oneLowTo Do
Address the capability to make separately-built components work together as one system. It matters most exactly when the project is complex and the interfaces are many.
Assignee: Unassigned · due 319 days after project start · takes 3 days
#39Hold scope, time, budget, and quality in view simultaneously and close without silent trade-offsHighTo Do
Define the multidimensional target—scope, time, budget, and quality together—and how to keep all four in view rather than trading them off blindly.
Assignee: Unassigned · due 322 days after project start · takes 14 days
#40Shift the definition of success from finishing the project to producing the benefits it was built to createHighTo Do
Shifts the definition of success from finishing the project to producing the benefits the project existed to create. It connects delivery, satisfaction, and throughput to sustained strategic value.
Assignee: Unassigned · due 336 days after project start · takes 14 days
#41Raise your lens from a single project to the portfolio and treat team well-being as a throughput driverLowTo Do
Raises the lens from a single project to the portfolio and the people running it. It treats sustainable well-being as a driver of long-term throughput, not a soft afterthought.
Assignee: Unassigned · due 350 days after project start · takes 3 days