Microsoft Project and the Agile Projects
All those who interacted, no matter how little, with Microsoft Project agree unanimously that it’s a very powerful scheduling tool. In other words, if we define and detail its tasks, it is very good at building a plan (the correct term is schedule), better than anything else. But, in order to define the tasks clearly, we need to know exactly what we expect from the project: what does it have
to deliver, on what conditions, which standards to comply with etc. It sounds easy, doesn’t it? In practice, we all know how complicated (impossible?) it is to define the purpose of the project and the delivery from the very beginning. In this case, how could Microsoft Project help me if I (or my
client) don’t know what I want from it?
Read printed format