1 Rule || Simplicity

Maximising the amount of work NOT done!

Manifesto for Agile Product Development – for any industry !

Agility remains a mindset, a philosophy and an attitude towards becoming a better version of who we are today.

Manifesto for Agile Product Development


We are uncovering simpler ways of developing products with end user engagement. Through this work we have come to value:

Individuals and interactions over processes and tools

Working prototypes over comprehensive documentation

End user collaboration over assumptions based on past evidence

Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.



Principles behind the Agile Product Development


We follow these 12 principles:


  1. Our highest priority is to create a working prototype, enough to generate an early end user feedback – through continuous delivery of valuable iterations.
  2. Welcome changing specifications, even late in development. Agility harness change for the end user’s competitive advantage.
  3. Deliver viable iterations frequently, from a couple of days to a couple of weeks, with a preference to the shorter timescale.
  4. End user representatives and developers must work together daily throughout the product lifetime.
  5. Build products around motivated and empowered individuals. Give them a secure environment, support their needs and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working iteration of prototype is the primary measure of progress.
  8. Agility promote sustainable development. The sponsors, developers, and end user representatives should be able to maintain a constant pace indefinitely.
  9. Continuous attention to operational efficiency and transparency enhances end user trust.
  10. Simplicity – the art of maximizing the amount of work not done – is essential.
  11. Best specifications and design decisions emerge from self-organizing and self-managing teams.
  12. At regular intervals, the team reflects on how to become more effective by adapting internal processes, adjusting internal synergy and creating an empathetic culture.


12 thoughts on “Manifesto for Agile Product Development – for any industry !

  1. Love it. The Agile manifesto for Software development was written by software engineers for software development. Even if some principles make sens for other “activities” there is a big difference when building a product (Looking for a solution) and building a software. It is like the difference between building a startup and running a business. One is looking for a business model and the other is optimising a business model. Thanks for this initiative.

    Liked by 1 person

  2. The intent behind this is sound but I dont think the answer to simplifying the Agile Manifesto is adding more words. You’re probably better of substituting “software” for “solution” or “system”.


    1. I have thought about using “solution/system” before. Although it can be confusing to product development such as medicines, food or any industry which we always forget to consider where “development” exists.

      What can you propose instead of solution or system? “Prototype” is my way of explaining which can also improve with a better term if necessary.


  3. When you think of it, what IT people are calling a “product” is actually a digitalised service. You are not “building a product” you are developing a service to be delivered via screens 🙂 Just sayin’ 🙂

    Liked by 1 person

    1. 🙂 indeed it is. Just a day ago on this same discussion on LinkedIn I was speaking to a gentleman who phrased it as.. software is a mass less product.

      Simplicity is all I advocate for by this version, so all development can be distinguished from manufacturing practices.. which stops us from being truly agile.


  4. A service is also developed and that can be done through agile approach. Try googling “service design”? 🙂


    1. Yes ofcourse, services can be developed following agile principles. We can then start creating specific terms in multiple industries.

      To avoid that complication we need simplicity and group all of them as “Product” as that’s what they are 🙂.. in one way or another.

      Liked by 1 person

    1. Service is not something we develop, it’s something we provide. It has known predictable steps where we should always apply lean principles to lower waste.

      Development is about experimenting theory to get a practical solution where a lot of failure and wastage is evident and at times even advisable. Without it we can never know what doesn’t work 🙂


  5. Except the quote “Agility remains a mindset, a philosophy and an attitude towards something better – on and on.” is there any new in 2.0?


    1. The original Agile Manifesto was sufficient and precise except for the fact that software development was the core of it. As all values and principles are/can be used on any other industry I have only updated the areas which makes it software development specific.

      The essence and the principles are almost identical. If you compare, you can see what I mean. Hope this helps.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: