Introducing agility into traditional systems development processes is never easy. Firstly, you have got to want to change. Secondly, you need to have a vision of what to change to. Finally, you need the tenacity to forge ahead in the face of stiff resistance. It is usually the third that is the most difficult journey to undertake. The hardest part of the journey is during the transition wherein you show how to bring agility into executing projects. You are walking the fine line between traditional methodology and incrementally introducing change.
One of the challenges during the transition is the question,” how do I know if the project is on track?” Despite all the conversations around introducing agility, when the rubber hits the road, it always comes back to “are the tasks on the critical path late?” or “what’s the project CPI and SPI?” or a variation thereof. Critical path and earned value concepts are deeply ingrained into our psyche. It is not easy to let go. (continue reading…)