Scrum Outside Software: Applying Scrum in Operations and Construction
Scrum is a framework originally designed for managing complex software development work. Its principles -- transparency, inspection, and adaptation -- and its empirical approach to planning (plan based on what you know, inspect what happens, and adapt) are applicable beyond software development wherever work is complex, requirements are uncertain, or the best path to the goal is not fully known at the start.
In 2022, Scrum and agile methods are being applied in construction project management, manufacturing operations, marketing and creative functions, and public-sector service delivery. Here is a beginner-friendly overview of what Scrum looks like in non-software contexts and what changes when you apply it outside of software development.
What Stays the Same in Non-Software Scrum
The core Scrum structure -- Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective -- applies in non-software contexts with relatively minor adaptation. The Sprint is a fixed-length period during which the team works toward a clear goal. Sprint Planning defines what will be done and how. The Daily Scrum is a 15-minute synchronisation that identifies blockers. The Sprint Review inspects what was built or delivered and collects feedback. The Retrospective identifies how the team can improve its process.
What Changes in Non-Software Scrum
The Product Backlog and Sprint Backlog take different forms. In construction, the Backlog might be a list of work packages or work fronts. In operations, it might be a list of process improvement initiatives or standard work updates. The form of the Backlog must match the nature of the work.
The definition of 'done' changes. In software, 'done' typically means tested, reviewed, and integrated. In construction, 'done' might mean inspected, certified, and handed over to the next trade. In marketing, 'done' might mean published and live. The definition of done must be adapted to the specific work context.
The Sprint Review changes format. In software, Sprint Reviews typically involve a demonstration of working software. In operations, the Sprint Review might involve a presentation of process improvement results, with before-and-after data. In construction, it might involve a site walkthrough of completed work.
Physical and safety constraints require adaptation. Construction and manufacturing work has physical sequencing constraints (you cannot pour concrete until the formwork is in place) and safety requirements (certain work cannot begin until a safety inspection is complete) that must be reflected in Sprint planning.
Where Non-Software Scrum Works Best
Non-software Scrum works best where the work has some flexibility in sequencing and approach, where feedback is available on a Sprint-length cycle, and where the team has some control over how they approach the work. Pure execution of a fully-specified plan benefits less from Scrum than work that involves problem-solving, design, or iteration.
XNM supports public-sector and capital-project organisations in implementing Scrum and agile delivery practices in non-software contexts. Reach out to XNM's program & project delivery advisory team to discuss Scrum implementation and agile delivery for your organisation.