The office has three improvement projects open, none finished. A new quoting template has been “nearly ready” since spring, and the team hears about changed priorities second-hand. The agile principles are the twelve statements that accompany the 2001 Manifesto for Agile Software Development, setting out how its authors believed software teams should plan, work and improve.
This guide sets out what the twelve agile principles say, where they came from, and how they can be applied, with limits, to the way a heating, ventilation and air conditioning (HVAC), electrical contracting or renewables business turning over £1M to £50M runs its office, its projects and its process changes.
What are the agile principles?
The agile principles are twelve short statements that sit behind the four values of the Manifesto for Agile Software Development. The agile principles cover customer value, welcoming change, frequent delivery, collaboration, trust, sustainable pace, simplicity and regular reflection, and they were written for software development, not for running a business.
According to the history page of the Agile Manifesto, seventeen people met on 11 to 13 February 2001 at Snowbird ski resort in Utah. They came from software methods such as Extreme Programming, Scrum and DSDM and wanted an alternative to documentation-driven, heavyweight software development processes.
The Manifesto for Agile Software Development states four values: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. It adds that there is value in the items on the right, but its authors value the items on the left more.
How the principles combine into a way of running a whole business is covered in the guide to the agile operating model, and how sprints and reviews work step by step in the guide to agile methodology. This guide stays with the twelve principles.
What do the 12 agile principles say?
The 12 agile principles, as published on the Principles behind the Agile Manifesto page, put customer satisfaction through early and continuous delivery first and end with regular reflection on how the team works. The wording below is a close paraphrase; the original page gives the exact text.
The twelve principles are customer satisfaction, welcoming change, frequent delivery, daily collaboration, motivated individuals, face-to-face conversation, working software as the measure of progress, sustainable pace, technical excellence, simplicity, self-organising teams and regular reflection:
- Customer satisfaction. The highest priority is satisfying the customer by delivering valuable software early and continuously.
- Welcoming change. Changing requirements are welcome, even late in development; agile processes harness change for the customer’s competitive advantage.
- Frequent delivery. Working software is delivered frequently, every couple of weeks to every couple of months, with a preference for the shorter timescale.
- Daily collaboration. Business people and developers work together every day throughout the project.
- Motivated individuals. Projects are built around motivated people, who are given the environment and support they need and trusted to get the job done.
- Face-to-face conversation. Talking face to face is the most efficient and effective way to convey information to and within a development team.
- Working software as the measure. Progress is measured primarily by software that works.
- Sustainable pace. Agile processes promote sustainable development: sponsors, developers and users should be able to keep up a constant pace indefinitely.
- Technical excellence. Continuous attention to technical excellence and good design enhances agility.
- Simplicity. Simplicity, described in the principles as “the art of maximizing the amount of work not done”, is essential.
- Self-organising teams. The best architectures, requirements and designs emerge from teams that organise themselves.
- Regular reflection. At regular intervals the team reflects on how to become more effective, then adjusts its behaviour accordingly.
How do the agile principles translate from software to running a business?
The agile principles translate to running a business by replacing their software terms with business equivalents: “working software” becomes a finished, usable output, the “development team” becomes the team doing the work, and the “customer” can be a paying client or an internal user. The translation is an interpretation; the Manifesto and its principles are written about software development.
Five terms need translating: customer, working software, development team, business people and project. The table shows one reasonable reading of each, not the Manifesto’s own wording.
| Term in the principles | Possible equivalent in a contracting business office | Example |
|---|---|---|
| Customer | The paying client, or the internal user of a process or report | Engineers using a new job sheet; a client receiving a revised quote format |
| Working software | A finished output in live use | A price list estimators actually quote from; a weekly cash report the directors actually read |
| Development team | The people doing the improvement or office work | Estimating, planning, accounts or a small cross-department group |
| Business people | Whoever decides what matters and accepts the result | The owner, a director or a contracts manager |
| Project | A piece of change or office work with an end point | Moving to a new job management system; rewriting the handover process |
Rostone Operating Partners reads the word “working” in the principles as the test for office change: a new quoting template counts as delivered when estimators are using it on live enquiries, not when the draft is finished. That reading makes principles 3 and 7 a practical check on whether a change has happened.
How do the customer and delivery principles apply in a contracting business?
The customer and delivery principles, numbers 1, 2, 3 and 7, apply in a contracting business by breaking office improvement work into small, usable pieces delivered within weeks, judged by whether they are in use, and adjusted as needs change. They tend to suit internal change projects better than fixed-scope client contracts.
Four practical applications follow: deliver in slices, set a short delivery rhythm, measure use rather than effort, and allow priorities to change between cycles.
- Deliver in slices. A new job management system can go live for one job type or team first, so problems can surface early, while they are small.
- Set a short delivery rhythm. Principle 3 asks for delivery every couple of weeks to every couple of months, with a preference for the shorter timescale. An office project can aim for something usable at each step.
- Measure use, not effort. Principle 7 makes working results the primary measure of progress. Reporting on a change project can show what is in use and what it has changed, linked to the measures in a goal setting framework.
- Allow priorities to change between cycles. Principle 2 welcomes late change. In an office, that can mean reordering improvement work at the end of each cycle, not every day.
The GOV.UK Service Manual page on measuring and reporting progress says good reporting should give a clear view of progress without creating extra work for the team, and that too many reporting requirements become counterproductive. A shared board, as in the Kanban method, is one way to show progress without a separate report.
How do the people and team principles apply in a contracting business?
The people and team principles, numbers 4, 5, 6 and 11, apply in a contracting business by putting the person who decides alongside the people doing the work, giving capable staff the support and authority to finish a task, and talking directly rather than through chains of email. They describe how teams work together, not a structure chart.
Four applications fit an HVAC, electrical or renewables office: involve the decision-maker throughout, trust capable people, talk directly, and let the team shape its own method.
- Involve the decision-maker throughout. Principle 4 asks business people and developers to work together daily. For an improvement project, the director who will accept the result can join short, regular check-ins instead of approving a finished design at the end.
- Trust capable people. Principle 5 asks for motivated individuals, given support and trusted to get the job done. This links closely to a healthy company culture and to the leadership behaviours that let people act without waiting for permission.
- Talk directly. Principle 6 favours face-to-face conversation. The GOV.UK Service Manual page on agile tools and techniques describes a daily standup of 15 minutes or less, held at the same time each day, in a format that lets the whole team take part, including people working remotely.
- Let the team shape its own method. Principle 11 says the best designs emerge from self-organising teams. In an office, the people who run a process can be best placed to redesign it, within limits the business sets on cost, compliance and customer commitments.
The Health and Safety Executive (HSE) sets out a related standard in its Management Standards for work-related stress. Part of the Control standard is that employees indicate they are able to have a say about the way they do their work, and HSE lists encouraging employees to use their skills and initiative among the things that should be happening. The standard concerns stress risk, not agile, but points the same way as principles 5 and 11.
How do the pace, quality and simplicity principles apply in a contracting business?
The pace, quality and simplicity principles, numbers 8, 9 and 10, apply in a contracting business by planning improvement work at a pace the team can keep up alongside the day job, building processes and systems properly the first time, and removing steps that add nothing. Together they can help guard against change that burns people out or adds paperwork.
Principle 8 asks that sponsors, developers and users can keep up a constant pace indefinitely. HSE’s Management Standards cover related ground for stress risk: part of the Demands standard is that employees indicate they are able to cope with the demands of their jobs, and it says the organisation should provide adequate and achievable demands in relation to agreed hours of work. An improvement project added to a full workload with no time set aside can work against both.
Rostone sees office improvement work stall when it is fitted in around the day job, with no protected time and no agreed end point, and plans change in short cycles with a named owner and a fixed slot in the week, which is one practical reading of the sustainable-pace principle.
Principles 9 and 10 pull together. In an office, good design can mean a new process is documented, tested with its users and built into the job management system, not left as a workaround. Simplicity can mean removing steps, forms and approvals before adding new ones. The guide to continuous improvement and Lean covers how to find and remove that kind of waste.
How does the reflection principle work as a regular review?
The reflection principle, number 12, works as a regular review in which the team looks at how it has been working, agrees what to keep and what to change, and assigns actions to complete before the next review. In agile teams this review is called a retrospective, and it is usually held at the end of each cycle. Regular reviews of this kind are one of the habits described in how to create a learning organisation in a contracting business, alongside learning from callbacks and near misses.
The same GOV.UK Service Manual guidance on agile tools and techniques describes retrospectives as regular meetings where the whole team talks about what is going well and what is not, usually at the end of an iteration such as a sprint. It suggests allowing 60 to 90 minutes, an open atmosphere in which every member of the team can speak honestly, and a list of actions assigned to people, aimed to be done before the next retrospective.
A contracting business can run the same review at the end of each improvement cycle, or monthly. Four questions, adapted from the GOV.UK example topics, keep it short: what went well, what went badly, what is still unclear, and what will change before the next review.
Regular reflection is also where agile meets wider change. Principle 12 adjusts how a team works at regular intervals; larger changes, such as restructuring or a new system across the business, can need a planned approach as well. The guide to change management frameworks compares the main models for that larger kind of change.
Where do the agile principles not fit in an HVAC, electrical or renewables business?
The agile principles fit least well in site-based, safety-critical installation work, where legal duties, agreed designs and regulations fix how the work is done; the principles cannot override them. The principles also say nothing about employment rights, such as the legal right to request flexible working.
Three limits are worth keeping in view: safety-critical site work, fixed-scope client contracts, and employment rights.
- Safety-critical site work. Self-organisation and late change do not override legal duties or an agreed design. The guide to the agile operating model, linked earlier in this guide, sets out where the regulatory boundaries sit for installation work.
- Fixed-scope client contracts. A priced contract with an agreed specification is not the same as a software backlog. Change on a client job is dealt with under whatever change terms the contract contains, which limits how far principles 2 and 3 can apply to delivery.
- Employment rights. GOV.UK guidance on flexible working describes it as a way of working that suits an employee’s needs, such as flexible start and finish times or working from home, and says all employees have the legal right to request flexible working from their first day in a job. That right, and the employer’s duty to handle requests in a reasonable manner, apply whatever management method is used. Flexible working rules are different in Northern Ireland.
Do the agile principles affect business valuation?
The agile principles do not affect business valuation directly: the Manifesto says nothing about valuation, and no primary source reviewed for this guide links adopting the principles to a higher valuation. Any effect would come indirectly, through how the business performs and how well it can show that performance to a buyer or investor.
A buyer or investor is generally assessing results and the evidence behind them rather than the method that produced them. If applying the principles leads to reliable reporting, documented processes and decisions that do not all wait for the owner, those outcomes can be shown to a buyer; the method on its own is unlikely to be visible to one. Ten management habits that reduce decision queues of this kind are set out in leadership strategies to improve productivity.
Rostone reads the principles against the four GRAX routes a business can take: Grow, Raise, Acquire and Exit. For growth, short cycles and regular reflection (principles 3 and 12) can help change keep pace with a rising workload; for raising finance, treating use as the measure of progress (principle 7) can make reporting on change clearer; for an acquisition, the team principles (4, 5, 6 and 11) can help two teams agree new ways of working; and for an exit, a business that improves without the owner driving every change can be easier to hand over.
Business improvement services for HVAC, renewables and electrical contractors diagnose where margin, cash and capacity are being lost, design a ranked plan of changes, and deliver them inside the business in repeated 90-day turns until it runs differently.
Frequently asked questions
The Agile Manifesto values are four statements of what its authors prefer, such as individuals and interactions over processes and tools. The 12 principles sit behind the values and describe in more detail how a software team works, covering delivery rhythm, collaboration, pace, simplicity and reflection. Both come from the same group of authors, and the Manifesto is dated 2001.
The first of the 12 principles says the highest priority is satisfying the customer by delivering valuable software early and continuously. In a business setting, that can be read as delivering usable results early and regularly to whoever relies on them, whether a paying client or an internal team.
The agile principles are published on the Agile Manifesto website as the principles followed by the Manifesto’s authors: seventeen people who met at Snowbird, Utah, on 11 to 13 February 2001 and signed the Manifesto for Agile Software Development. The Manifesto’s history page describes them as independent thinkers about software development, from methods such as Extreme Programming, Scrum and DSDM. The principles page itself carries no date, and the principles were written for software development.
A small business can start by choosing one office improvement project, breaking it into pieces that can be in use within a few weeks, and holding a short review at the end of each cycle. The review agrees what to keep, what to change and who does what before the next one.
Sources
Agile Manifesto: Manifesto for Agile Software Development; Principles behind the Agile Manifesto; History: The Agile Manifesto
GOV.UK: Service Manual: Agile tools and techniques; Service Manual: Measuring and reporting progress; Flexible working
Health and Safety Executive (HSE): Management Standards: Control; Management Standards: Demands
Last updated: 14 November 2026



