Knowledge hub
Blogs
Apr 2, 2024

Agile Manifesto | Principle 10

In the forthcoming weeks, we are exploring one Agile Manifesto principle or value every Tuesday. This week, it's Principle 10's turn.

Principle 10

Simplicity – the art of maximizing the amount of work not done – is essential.

The title of this principle is a bit counter-intuitive and confusing to read. What it boils down to, however, is focus on quality & customer value, not perfection. Do not go for the “eierlegende Wollmilchsau”, which refers to a all-in-one solution that solves all problems and has all imaginably possible positive attributes. Do not gold-plate the e-bike you are producing, just because you can. Focus instead on what the customer really wants and optimize business value*. The iterative & incremental approach (Principle 2 & 3) helps with continuous value delivery (Principle 1) and retaining focus on what is most relevant for the customer to implement next. Any work items that distract from this remain in the backlog or are discarded. If that comes counter-intuitive, because we have been socialised into maintaining ever-growing ToDo lists, the practice of having a Not-ToDo list could be a good start in raising awareness of what brings value and what doesn’t. The focus on simplicity also benefits the maintenance of the solution and hence decreases the risk of accumulating technical debt (Principle 9).

Explore each principle & value with us

Introduction to the Agile Manifesto & Part 1 – The Agile Team: Skills & Culture

Principle 1: Our highest priority is to satisfy the customer through early and continuous delivery of valuable solutions*.

Principle 2: Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

Principle 3: Deliver working solution* frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

Principle 4: Business people and team* must work together daily throughout the project.

Principle 5: Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

Principle 6: The most efficient and effective method of conveying information to and within an agile team is real-time conversation.

Principle 7: Working solution* is the primary measure of progress.

Principle 8: Agile processes promote sustainable development. The sponsors, team*, and users should be able to maintain a constant pace indefinitely.

Principle 9: Continuous attention to technical excellence and good design enhances agility.

Principle 10: Simplicity – the art of maximizing the amount of work not done – is essential.

Principle 11: The best architectures, requirements, and designs emerge from self-organizing teams.

Principle 12: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Value 1: We value individuals and interactions over processes and tools.

Value 2: We value working solution* over comprehensive documentation.

Value 3: We value customer collaboration over contract negotiation.

Value 4: We value responding to change over following a plan.

*LEGEND:

Business Value: Business Value encompasses any deliverable, feature, or enhancement that directly contributes to customer satisfaction, employee well-being, or overall organizational success. It can encompass not only customer-facing elements but also internal enablers that improve efficiency and effectiveness within the organization.

Developers: has been exchanged by team to recognize that Agile Teams can encompass a diverse range of roles and functions beyond just software development

Iteration: An Iteration refers to a distinct phase or cycle within a development process, where a set of tasks or activities are completed in a defined timeframe. In Scrum methodology, an Iteration is known as a Sprint, typically lasting 2-4 weeks, during which a set of prioritized work items are completed.

Lead Time: Lead Time refers to the duration it takes for a task or project to move from the initial request or conception stage to its completion, including all necessary processes and steps.

MVP (Minimum Viable Product): The MVP is a basic, functional version of a product or service that includes essential features, allowing it to be deployed or released to gather early feedback from users or customers.

Software: has been replaced by solutions to account for the fact that Agility does not only apply to software development, but to any kind of value that a business offers to the customer.

It might also interest you!

Agile Manifesto | Principle 11

In the forthcoming weeks, we are exploring one Agile Manifesto principle or value every Tuesday. This week, it's Principle 11's turn.
Read more

Agile Manifesto | Principle 12

In previous weeks, we explored one principle of the Agile Manifesto every Tuesday. This week, it's the last principle's turn: Principle 12. From next week onwards, we will explore the values.
Read more

Agile Manifesto | Value 1

So far we have explored one Agile Manifesto principle every Tuesday. This week, we will start with delving into the values – with Value 1.
Read more
Written by Julia Heuritsch, SAFe Practice Consultant & Agile Coach