Governance on the Windows 7 Project

The dedicated followers of our project, through this blog will have noticed that I am the second Project Manager who has been assigned to its delivery.  As with projects delivered in the real world the Project Manger can change as is the case for project.  Importantly, what processes and procedures do we have in place to mitigate this risk?  Our Project Managers are fully trained in our home grown Predictor methodology which greatly assists in transitioning Project Managers mid project.  We took this opportunity to monitor the effectiveness of this approach and to date it has been effective with a few small issues that are now solved and rolled into our processes.  As you know success is a journey, not a destination.

You will have read this project is of great importance to Data#3 where the same governance is applied throughout the lifecycle of this project as is applied to any other project.  Customers are customers, whether they be internal or external, to Data#3 it is irrelevant.  Sometimes delivering to an internal customer is more difficult due to the associated ‘mateship’.  This is something that is always at the forefront of every Project Manager’s mind.

 You may have also read through Shaun Duncan’s recent blog entry this week that we are currently in Week 2 of Production Deployment.  Allocating users to a choice of nine timeslots over three days seems to be a good way of managing the allocation of the installations.  No major issues have been raised, which is good testament to the rigorous testing prior to the rollout.