Agile Delivery Kit for Software Organisations


How to work in an agile way. This starter kit provides the strategies, recipes. workshops, technologies, practices, and guides that will help you and your people create a way of work that enables success.





3 minutes to read

Last Updated: Wed 25 Oct 2023 11:15

** Courage | Focus | Commitment | Openness | Respect **

Our best efforts have been made, rather than to dictate, to create a balance between autonomy required for self-management, and alignment required to maintain our business. Always question the content here! Always!

The first decision that needs to be made is Should we use Agile or Traditional Practices. To do that you need to decide what sort of work you are working on. If the work that you have is in Simple or Complicated environments, it is suitable to use traditional practices like PMI or Prince2. If your work is in a Complex or Chaotic environment then you should use an Empirical system like Scrum or Kanban.

Product Delivery

In the Product Delivery world, we operate in a complicated environment where we deliver many easily understood items to the customer; the outcome is known. This may be Support Tickets, a Software Factory, or another pre-built system that we are deploying or configuring. For this type of work, we should follow flow-based techniques to model our current process, and then optimise for output; more stuff.

Risk Management: Risk here is managed by more control; lists of risks and mitigating actions.

Techniques: flow-based techniques complimented at scale with PMI / Prince2 / Plan-Driven


Review: Should we use Agile or Traditional Practices?

Product Development

If we are building something that does not exist yet (all Software Engineering exists here!) then we are in a complex environment and need to use an empirical approach. Implementing an Empirical Process Control System requires transparency. Transparency is required to Inspect and Adapt our work.

We expect that you will use Scrum to manage the work, Nexus to manage many teams work, and Evidence-based Management to monitor your progress.

Risk Management: Delivery of Done increments of value every Sprint including the first.

Techniques: Empirical techniques complemented by Kanban

naked-Agility-Scrum-Framework.jpg Kanban.png

Review: Should we use Agile or Traditional Practices?

Are Scaling practices right for us?


Answer: Scaling Scrum

Overview of Content

Join the Community
The league of extraordinary lean-agile practitioners is a group of peers and seasoned practitioners that continuously learn, share emergent practices, and discuss topics with courage, commitment, focus, respect, & openness!