The BAD Toolkit brings together agile methods to solve problems under a community driven framework and we'd like to tell you a bit more about the thinking behind it.
The four areas below are intended to give you an overview of what makes us tick. If you have any additional queries, then just get in touch.
Often the adoption of the BAD Toolkit within organisations follows a journey similar to the low cost model shown below.
To facilitate the take up of the Toolkit, our aim is to provide visitors with enough support that they can implement the BAD Tools themselves. This support includes:
Both information and Cheat Sheets are available as downloads to explain the theory behind the Tools and solutions and to allow you to give it a go.
Real world examples show how the VMOST Canvas would fit in the context of other teams and organisations.
A list of independent Practitioners are available to offer advice and support where needed.
We believe that the BAD Toolkit is a brilliant change adoption tool and that when used it can streamline organisational change by ensuring that investment is spent in the optimal areas.
This is why we have released the tools within the BAD Toolkit so that you are free to use and improve on it, rather than hiding it behind a subscription model or keeping it as restricted intellectual property under a heavy copyright framework.
We are clear in our shared vision.
The purpose of The BAD Toolkit Ltd is not to achieve a financial profit. The driver for the toolkit is to ensure that everyone, regardless of their position or organisation, has the ability to see how others have adapted and adopt Agile methodologies in order to solve similar unique problems.
Both the tool authors and contributors, as well as the people involved in the operation of the BAD.Tools site receive no income from The BAD Toolkit Ltd, and we are proud that the BAD Toolkit is driven by the Agile spirit of collaboration by of bringing people together to solve problems and move the industry forward.
Even though The BAD Toolkit promotes shared knowledge, it does not mean that we do not take ownership and IP seriously. We believe that everyone involved in defining a tool should be given credit. Whether its the authors who created the foundations of the technique or the practitioners who have adapted it to solve a specific challenge.
The Toolkit eco-system is built around crediting everyone who has shaped the tool. Our approach is that any person or company may contribute and will be attributed as sponsor / author. All contributions are reviewed by a board of experienced delivery experts to ensure that quality is maintained.
From a practical aspect, both the website and the repo have prominent links to our guidelines on crediting sources to help our contributors. There is also the ability for anyone to report any violations of this attribution.