Program Management¶

Part 10 is about managing the delivery of value (at the level of the project, the product, the program, and the portfolio) and about the enterprise and government setting where that work happens. Parts 1–9 and 11 show you how to build software well. This part is different. It covers how an organization decides what to fund, lines up many teams and vendors behind that choice, manages the risk and compliance around it, keeps it alive over a long life, partners to innovate, and does all of this ethically and in the public interest. This is where engineering meets strategy, money, procurement, oversight, and accountability.

This management layer matters most exactly where this guidebook is aimed: large teams, enterprises, and governments. A single team can improvise its coordination. Hundreds of teams cannot. Multi-year public funding, procurement rules, audit obligations, and system lifetimes measured in decades turn management from an overhead cost into the thing that decides success or failure. The chapters here treat that context not as bureaucracy to endure but as design input: the constraints and disciplines that let large organizations turn strategy into software worth building, safe to run, sound to depend on, and fit to be trusted.

Chapters in this part¶

10.1 Portfolio and program management: Aligning engineering to strategy and OKRs (objectives and key results), prioritizing across initiatives, and coordinating dependencies among many teams and vendors.
10.2 Risk, audit, and assurance: Enterprise and third-party risk, audit trails and continuous controls, business continuity, and concentration risk.
10.3 Procurement, open source, and licensing: Build/buy/adopt decisions, license compliance, open-source strategy and OSPOs (open source program offices), and managing dependencies.
10.4 Sustaining large and long-lived systems: Stewardship, bus-factor mitigation, deprecation and end-of-life, and managing systems that live for decades.
10.5 Ethics, accountability, and public interest: Professional ethics, algorithmic accountability, equity, sustainability, and serving citizens and customers with dignity.
10.6 Project management: Turning intent into delivered outcomes: predictive/adaptive/hybrid delivery, honest estimation, dependency and risk management, and engaged stakeholders.
10.7 Agile: Adaptive delivery as a mindset of values and principles: Scrum, Kanban, and XP (extreme programming); technical excellence; scaling and descaling; and agile in enterprise and government.
10.8 Maturity models: Assessing capability against a ladder of levels to prioritize improvement, a mirror for directing investment, not a trophy to chase.
10.9 Innovation partnership: The deliberate third option beyond build and buy: partnering with startups, labs, and public instruments to share the risk and reward of creating new capability.
10.10 Software engineering economics: The analytical spine of every funding decision: value and cost, time-value of money, cost estimation, ROI/TCO/NPV (return on investment, total cost of ownership, net present value), the economics of technical debt and the cost of delay, and building a defensible business case.
10.11 Digital sovereignty: Proportionate control over your data, software, and infrastructure, covering jurisdiction versus residency, key control, portability and exit, sovereign cloud, and open standards as strategic autonomy.
10.12 Open source vs closed source: A balanced comparison of open and proprietary software, both as a consumer deciding what to adopt and as a producer deciding what to open-source, across cost, control, security, longevity, and lock-in.
10.13 Interorganization collaboration: How independent organizations work together across boundaries (consortia, foundations, standards bodies, joint ventures, and inter-agency and public-private partnerships), and how to govern shared work and align incentives.

How these chapters interrelate¶

The part moves from the strategic to the tactical and back to the ethical. Portfolio and program management (10.1) sets direction and coordinates the whole. It feeds on the outcome measures of the discovery pipeline (chapter 11.1) and the delivery evidence of chapter 11.2. Project management (10.6) and Agile (10.7) are the disciplines for executing a single initiative within that portfolio: chapter 10.6 lays out the constraints and choices common to all delivery, and chapter 10.7 goes deep on the adaptive option. Risk and assurance (10.2) and procurement, open source, and licensing (10.3) manage what surrounds delivery (exposure, controls, suppliers, and dependencies), and both lean on the security and compliance practices of chapter 4.6. Maturity models (10.8) give you a lens for deciding where to invest in improving all of this. Innovation partnership (10.9) supplies capability the organization can neither build nor buy alone, sitting close to procurement (10.3) and the build/buy/partner logic of chapter 6.1. Sustaining systems (10.4) extends the horizon to the decades a large system lives, drawing on the reliability and operational disciplines of Part 9. Ethics and public interest (10.5) hold the whole endeavor accountable to the people it serves. Read together, these chapters describe how a large organization turns strategy and money into trustworthy software over the long run.