Setting up and agile project

In order to agilize a project we don’t need to decide what agile method to use, but to make sure that the project context is set up for agility:

  1. define what to do (create a backlog of what needs to be done )
    • define needs, this triggers the conception and realization of user stories
    • agree outcomes, what is of value for the customer in order to originate flow
  2. select who will do it (form a team that has all the competence and skills to complete the work)
    • organize clarity (conversations about needs and US’s), speed (cadence of delivery), and accountability (taking ownership of delivery)
  3. set the ground rules on how to do it (agree on how work is going to be done in order to deliver value frequently)
    • Keep visibility (this backs up conversations and understanding of needs, helps manage flow and cadence, and clarifies commitment)
    • manage options and test assumptions (how work is prioritized, estimated, validated, and completed)

agile is about 3 things

These agile fundamentals provide a solid ground where agile practices will facilitate the delivery of value.

Note: this is based on Mike Cottmeyer’s (Leading Agile) thoughts, integrated with Mike Burrows’ Agendashift principles.

Unknown's avatar

Author: Mario Aiello

Hi, I’m Mario – a retired agility warrior from a major Swiss bank, beyond agile explorer, lean thinker, former rugby player, and wishful golfer. What frustrates me most? Poor agile adoption, illusionary scaling, and the lack of true business agility. I believe agility should fit purpose, context, and practice – and continuously evolve. Active in the agile space since 2008, my consulting journey began in 2012, helping a digital identity unit adopt Scrum at team level. That work led to the design of an Agile Operating System for the entire organization. Today, as an independent consultant, I help organizations unlock sustainable agility – guided by adaptive intelligence: sensing challenges, learning fast, and adapting with purpose.