^ [[2 About Agile]] # 2.4 Agile Myths Some people (both IT and business-oriented) are very enthusiastic about applying Agile approaches to their work. Others are sceptical about Agile for a number of reasons, influenced perhaps by certain myths about Agile. Some of these myths are listed below: **Myth — Agile is a silver bullet** - You can fail as in any other project. But **with Agile you might fail sooner** and in doing so, you **save resources**. **Myth — Agile teams do not do documentation** - They do not produce unnecessary documentation. **Myth — Agile is anti-planning** - In Agile development there is **extensive planning on multiple levels**, and **with high visibility**. - There is a **Release Plan**, **Iteration plans**, and **daily work is planned** during Stand-up Meetings. - There are different **tools** for planning (e.g. **product and iteration backlogs**). **Myth — Agile is undisciplined** - In fact, Agile development is **extremely disciplined**. Practices like Continuous Integration, Automated Testing, Iteration reviews and retrospectives, Iteration and release planning, etc, are some examples of how disciplined Agile development must be. - In most Agile practices all **iterations** and **meetings** are **timeboxed**. - There is **commitment to "ship product" regularly**. - **Improving the practice** is part of the practice. **Myth — Agile is Scrum.** - Scrum is not the only Agile approach, **there are at least ten more**. - **Scrum** focuses mostly on the **"construction" aspect of projects**. - **Scrum** **does not address** activities for managing the **complete project lifecycle**. - Scrum has become one of the **most popular Agile frameworks** (true). **Myth - Agile is anti-architecture** - Solution architecture is **minimised to what is known**. - **Solution architecture** is valuable and in one or another way it is **used by Agile teams**. Next: [[3 PM2-Agile – Overview]]