This article is a step by step guide on how to turn an existing Agile framework/methodology that is limited to IT projects into something that is applicable to every project.
Take the following steps, or get someone who can help you with:
- Find a Word version of the manual, or find someone to type it for you.
- Open the file in Word.
- Click on the Replace button on the Home tab of the ribbon.
- Type “software” in the “find what” field.
- Type “product” in the “replace with” field.
- Click on the Replace All button.
- Add the following line to the introduction: this framework/methodology is not limited to IT development, and is applicable to every kind of project.
- Save the file.
Great, now you have an Agile framework/method that is not limited to IT development.
The following can improve the result:
- Repeat step 7, once per page; the same message delivered with different sentences.
- Blame the original resource to be limited to IT development
- Select a new name for your product.
- Keep marketing your product.
- Ask your friends to refer to your product when they are arguing with someone over the fact that Agile is not applicable to every project.
In certain cases, you may have problems with the step 6 of the method explained above; for example, The Scrum Guide doesn’t use the word “software”. It’s a shame, but don’t worry: just proceed to the next step.
You might face difficult questions regarding your new product. In order to make it more authoritative, create at least two products, based on two different original pieces of work, and cross reference: in each one address the other as a great alternative.
You know the rest.
Build on top of it
If you have more than one product created like this, which I really recommend, it’s time to take the next step and create a new product that combines the two.
Don’t worry, you don’t need to produce any real content; just copy and paste the two existing products, and add an introduction. You can hire a ghost writer to handle the introduction for you as well.
Many people have successfully used this guideline before, but I don’t take any responsibility for any damages, either physically, or mentally ;)