Sources and further reading
The frameworks, standards and authors this article draws on, grouped by subject, with what each one supports.
The two traditions
The framework as it stands: the accountabilities, the artifacts and their commitments, and the absence of a project manager role. Earlier editions are archived on the same site.
Manifesto for Agile Software Development
The 2001 manifesto and its twelve principles, including technical excellence (ninth) and a sustainable pace (eighth).
A Guide to the Project Management Body of Knowledge (PMBOK Guide)
The ten knowledge areas, the process groups of the sixth edition, and the move to principles and performance domains in the seventh.
Agile Practice Guide
PMI's own recognition of adaptive approaches.
The New New Product Development Game
The article that gave Scrum its name.
The first presentation of Scrum as empirical process control.
Managing the Development of Large Software Systems
The paper usually cited as the origin of the waterfall, which warns against running it in a single pass.
Improvement and management
Statistical Method from the Viewpoint of Quality Control
The improvement cycle later known as plan, do, check, act.
Out of the Crisis
Deming's management principles, including driving out fear and eliminating numerical quotas.
The planning onion, and doing high-value, high-risk work early. Developed in the companion article, Agile Planning.
Architecture and technical practice
Teams that adopt the process, neglect technical practice and slow down.
The slowdown curve of figure 4.
The WyCash Portfolio Management System
Where the technical debt metaphor comes from.
Scrum : le guide pratique de la méthode agile la plus populaire
The recommendation to give about a quarter of early sprints to architecture.
Crystal Clear: A Human-Powered Methodology for Small Teams
The walking skeleton.
Conway's law: systems mirror the communication structure of the organisations that build them.
Team types, including complicated-subsystem teams for deep specialists.
Scale and regulation
Scaling Scrum with a Nexus Integration Team.
Scaling Scrum around one Product Backlog.
Scaling through a network of teams.
PI Planning, Release Train Engineers, enablers and the architectural runway.
IEC 62304: Medical device software, software life cycle processes
Documented architecture for safety classes B and C, and traceability from requirements to tests.
AAMI TIR45: Guidance on the use of agile practices in the development of medical device software
Recognised by the FDA as a consensus standard.
Quality Management System Regulation (QMSR)
Design controls under 21 CFR 820, now aligned with ISO 13485.