I’m a strong advocate of the Agile Manifesto. This “new look” (the document was signed back in February 2001) to the Software Engineering has brought large productivity, predictability and quality improvements. That said, it has also generated equally large pain in all those projects where it has been misunderstood or applied in a bias way.
While not universally applicable, Agile usually brings real benefits when we remember to look at both sides of their characterization sentence:
That is, while there is value in the items on the right (tradicional approach), we value the items on the left more (agile approach).
Unfortunately, engineers feel the freedom and fun (positive and deserved) of the left side (Individuals and interactions, working software, customer collaboration, responding to change), but they just ignore or despise the habits on the right (processes and tools, documentation, contract negotiation and following a plan). The manifesto states that we have to value more the habits on the right, not that we have to only value them.
In my opinion special attention has to be made in generating simple but thorough and useful documentation needed to communicate important information as well as high level plans to set expectations and staff accordingly to meet business strategy goals.
Last, let me add that Methodologies cannot be used as a Prêt-à-Porter, methodologies need to be tailored to the specific needs and reality of the company.
Reviewing your current methodology
Adopting or modifying your methodology
Enhance your forecasting capabilities
Enhance your testing and software quality methodology
Define and generate project management metrics
Selecting and using project management tools
This is not Agile
Avoiding or embracing an impossible deadline
If you have any questions or comments, or if you would like to contact me for more detailed information, please use the form below and I will get back to you as soon as possible. Thank you for your interest.