Agile Delivery Kit for Software Organisations
Article
6 minutes to read
Last Updated: Wed 25 Oct 2023 11:15
This kit provides examples and suggestions of the strategies, recipes. workshops, technologies, practices, and guides that will help you be successful. Where posable these pages will use the terminology from the guides referenced here.
To enable the offer we have use these catagories to group the relevant content:
- Strategies - a plan of action designed to achieve a long-term or overall aim
- Recipes - a set of instructions which are likely to lead to a particular outcome
- Technologies - the application of scientific knowledge for practical purposes
- Practices - the actual application or use of an idea, belief, or method, as opposed to theories relating to it
- Guides - These guides are published and recognized guides to a topic.
How to use this content
This content represents a starting point, or SDK, to help organisations kickstart creating their own way-of-working based on emergent lean-agile practices.
All of this content represents a baseline starting point for any Product delivery team or organisation. You can modify as needed within the bounds of your business context without breaking the core mindset.
Rules are for the guidance of wise people and the obedience of fools
–Adam Cogan
If you would like to create your own copy of this SDK we recommend that you fork the repository on GitHub so that you can continue to pull new changes and updates to the content.
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. In service to that we try to uphold the following values in all aspects of our work: Courage, Focus, Commitment, Openness, & Respect
We recommend that you always question the content here, and always ask if you can do something easier and simpler.
If so, do that!
Way of Working & First Principals
Creating a collaborative, decentralized, and democratized way-of-working is an important part of developing a process and you should involve everyone that you expect to use it. People will not buy into your process unless its their process too. We operate in a highly competative and dynamic market
he first key understanding is that there are no companies left that are in low competition markets with few customer demands. Those complicated markets have not existed since the 70s and all companies today have to deal with highly competitive markets with high customer demand and churn.
These core first principals, routed in empiricism, are at the heart of this document:
No items currently published...
Whitepapers & Presentations
- Live site Culture & Site Reliability - Creating a live site culture with site reliability engineering and how it fits the DevOps journey of Microsoft from traditional waterfall to agile engineering.
- An Enterprise Evolution that Shows that you can too - The DevOps journey of Microsoft from traditional waterfall to agile engineering.
Reasons why agile often fails (anti-patterns)
- Unprofessional Behaviour - We need to stop normalising unprofessional behaviour and call it out whenever we hear it.
- The Hero - The Hero takes it upon him or herself to be the saviour.
- The Eye Roller - The Eye Roller sees Scrum as unnecessary and vocally complains about using it, falling just short of refusing to participate.
- The Avoider - The Avoider uses the letter of their perceived law in their defence.
- The Absent Product Owner - The Absent Product Owner is frequently too busy to attend to their responsibilities as prescribed by Scrum.
- The 90 Percenter - The 90 Percenter is frequently “almost done” with whatever they are working on.
Frequently Asked Questions
- Should we use averages to make decisions?
- Should a Scrum Master be as knowledgeable as a Product Owner?
- Does having a definition of ready a good idea?
- How can you tell if you are agile?
- Does the theory of Open Systems result in an inability to ever find a route cause?
Guides
- The Scrum Guide - The Scrum Guide contains the definition of Scrum.
- Nexus Guide
- Manifesto for Agile Software Development - We are uncovering better ways of developing software by doing it and helping others do it. These are our values and principles.
- Kanban Guide - Kanban is a strategy for optimizing the flow of value through a process that uses a visual, pull-based system.
- Kanban Guide for Scrum Teams - The flow-based perspective of Kanban can enhance and complement the Scrum framework and its implementation.
- The Evidence-Based Management Guide - Evidence-Based Management (EBM) is an empirical approach that helps organizations to continuously improve customer outcomes, organizational capabilities, and business results under conditions of uncertainty.
- Detecting Agile BS - The purpose of this document is to provide guidance to DoD program executives and acquisition professionals on how to detect software projects that are really using agile development versus those that are simply waterfall or spiral development in agile clothing.
Discussions, Communities, & Contributing
You can create or join a discussion on any topic.
You can join the community on any topic.
We absolutely accept pull requests for changes, additions, and updates. We ask that you keep each PR to one idea or topic, with as few files affected as possible, to enable our moderators to review and accept the changes quickly.
Current Stewardship
Name: Martin Hinshelwood
Email: martin [at] nkdagility.com
Chat : “martin [at] nkdagility.com EXTERNAL” in Microsoft Teams.
License
© 2023 Martin Hinshelwood and naked Agility Ltd. This publication is offered for license under the Attribution Share-Alike license of Creative Commons, accessible at https://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form at https://creativecommons.org/licenses/by-sa/4.0/.