How deeply does Think Like a CTO cover phased delivery strategy?

Demonstrates staged proposals and intermediate wins, without specifying implementation mechanics.

Phased delivery strategy

A method of implementing a plan through successive stages with limited commitments and intermediate results.

A phased delivery strategy replaces an all-or-nothing proposal with successive commitments, relevant choices, and visible wins. It gives decision-makers room to provide input while limiting early exposure. section 2.1.4

Use the approach when a proposal requires executive commitment:

Offer several outcomes rather than a simple yes-or-no decision. section 2.1.4
Make each choice relevant to the immediate organizational situation. section 2.1.4
Sequence the work so the organization can benefit from intermediate wins before committing too much. section 2.1.4

A proposal to a CEO

Instead of asking a CEO to approve one irreversible plan, present relevant stages and demonstrate benefits along the way. The CEO can influence the direction while the organization learns the proposal’s full scope. section 2.1.4

How Think Like a CTO covers it

liveBook manning.com

Read Think Like a CTO on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Practical Automation with PowerShell: Effective scripting from the console to the cloudA phased approach is a technique for developing an automation through successive stages that provide incremental improvements and benefits.
liveBook manning.com

Think Like a Software Engineering ManagerA phased approach is a delivery technique that divides a larger change into sequenced stages with progressively broader scope.

Compare how 3 books explain phased delivery strategy →

Related concepts

deploymentused by · Deployment is the process of making software, models, or other computational systems available to operate in a target environment.
automationused by · Automation is the execution of tasks or processes by machines or software with reduced direct human intervention.
riskaddresses · Risk is the possibility and potential impact of an adverse outcome arising from uncertainty.
feedbackconfigured by · Feedback is information about an action, system, or outcome that can inform evaluation, decisions, or subsequent behavior.
dependencyaddresses · A software dependency is a component, resource, or prerequisite on which another software component or operation relies to function or proceed.

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.