IT Project Tips and Tricks - 03 - Methodology
An IT Project Methodology describes how project work is identified, documented, assigned, tracked, tested, and deployed to end users. At the start of my career, there was no true use of methodology. Requirements and tracking work was done in an ad hoc manner. A waterfall approach was used where all requirements, design, coding, testing, and deployment were done in their entirety one after the other. This did not work well because by the time we got around to testing and the end users saw the app for the first time, often they would say, 'Hey this is not bad but really, it's not what we wanted, we wanted it like this instead, bla bla bla.' But by then the app was coded 100%, so it was too late to go back and do a rewrite because it would be too much work. In the end, we would patch the app with band aids to give end users something resembling what they really wanted. Later in my career, I was exposed to several methodologies including Method1, RUP, and eXtreme/Agile. In