Project Managers Should Not Fear the Baseline
Project managers should use baselining as a tool to improve, not to demonstrate failure.
There seems to be a growing phenomenon in the US, and I believe worldwide, that nobody takes responsibility or ownership anymore. OK, this is not new but I believe it is growing. This fear of ownership is in turn creating a fear of commitment. We see this throughout society. I also see this in the world of project management.
Baselining a project is a way of making a commitment to an end date. The project is tracked from that point forward against the baseline plan that was committed. I wrote earlier about how this is like a game of kick the can as we track actual progress against the plan. The problem becomes that most projects track poorly against this plan.
The poor performance of the project usually has less to do with the project manager or the project team and more to do with the systemic failures of the organizational culture to provide the proper tools and governance to allow the projects to succeed. These systemic issues really become the moose on the table that no one wants to talk about. As a result the PM and/or the project team are blamed for the failure.
Not producing a baseline that we can use to track the project against is a way of disguising the fact that the project if off track and allowing the PM and the team to survive until the scapegoats are sought after the project fails. Everyone hopes that they will not be the ones that are sacrificed when the failure become evident.
While it is true that the creation of a baseline and tracking against that plan will expose project problems earlier, I contend that this will also increase the opportunity for success. At a minimum this would minimize the failure gap of the project. Identifying problems early allows for corrective actions to be taken to put the project back on track. This then should be every project manager’s approach to tracking their projects. This will increase the opportunity to be successful and decrease the possibility of being the first on the chopping block.
As noted earlier the problems that will be uncovered are likely due to failures within the organization. Identifying these problems will not only help the current project but will also help future projects if the failures are corrected. Additionally the PM and project team will not be held solely accountable for resulting failures in the project.
The baseline is not something to be feared. Rather it is the most important tool that a project manager has at their disposal to increase the possibility of success. So don’t fear the baseline. Embrace and utilize it to create success for you and you project.
Print
Baselining a project is a way of making a commitment to an end date. The project is tracked from that point forward against the baseline plan that was committed. I wrote earlier about how this is like a game of kick the can as we track actual progress against the plan. The problem becomes that most projects track poorly against this plan.
The poor performance of the project usually has less to do with the project manager or the project team and more to do with the systemic failures of the organizational culture to provide the proper tools and governance to allow the projects to succeed. These systemic issues really become the moose on the table that no one wants to talk about. As a result the PM and/or the project team are blamed for the failure.
Not producing a baseline that we can use to track the project against is a way of disguising the fact that the project if off track and allowing the PM and the team to survive until the scapegoats are sought after the project fails. Everyone hopes that they will not be the ones that are sacrificed when the failure become evident.
While it is true that the creation of a baseline and tracking against that plan will expose project problems earlier, I contend that this will also increase the opportunity for success. At a minimum this would minimize the failure gap of the project. Identifying problems early allows for corrective actions to be taken to put the project back on track. This then should be every project manager’s approach to tracking their projects. This will increase the opportunity to be successful and decrease the possibility of being the first on the chopping block.
As noted earlier the problems that will be uncovered are likely due to failures within the organization. Identifying these problems will not only help the current project but will also help future projects if the failures are corrected. Additionally the PM and project team will not be held solely accountable for resulting failures in the project.
The baseline is not something to be feared. Rather it is the most important tool that a project manager has at their disposal to increase the possibility of success. So don’t fear the baseline. Embrace and utilize it to create success for you and you project.
Previous Post: How Project Managers Can Get Their Projects Back On TrackNext Post: How Far Should Project Managers Breakdown a Project?
Most Discussed Posts
Cloud computing has emerged as one of the most significant game changers to hit the technology landscape in the past 20 years. With this massive expansion of the cloud, the perception of the IT organization is shifting from a utility player to a change agent. This eBook breaks down five ways progressive organizations are using cloud-based IT Management solutions to help drive innovation and become more strategic, including: adding visibility and analytics, speeding up time-to-value, lowering costs, improving prioritization, and providing a blueprint for future cloud deployments.
Read the white paper to see how IBM helped Citigroup deliver new services and enhancements to their 200 million customers faster.
There are 3 ways to modernize legacy applications: rewrite completely, acquire packaged solutions or migrate existing code. This paper explains why it's best to migrate and how IBM® Rational® software can help.
Accommodating specific lines of business can result in a hybrid ecosystem of applications and servers. The resulting complexity of this architecture makes for an environment that is costly to maintain and difficult to change when addressing new challenges.
This whitepaper will help you to define a mobile device passcode policy. Security managers must attempt to reconcile two opposing goals. They must: 1) create a passcode policy that is strong enough to protect the device if it is lost or stolen, while: 2) not annoying users with needless length or complexity.
This whitepaper, authored by The Radicati Group, looks at the key reasons organizations should consider moving to a cloud-based archiving solution. Email archiving solutions enable organizations to store, monitor, and collect electronic data exchanged by their users to comply with internal policies and regulations.
ATERNITY will showcase a 30-minute demo on how Fortune 500 companies are leveraging its award-winning FPI Platform to deliver a user-centric approach to Proactive IT Management.
For businesses to move forward and tap into the ever-expanding universe of Internet users and network-enabled devices, it's critical to learn how to make the transition to IPv6. Learn the critical steps your organization must take to make a seamless transition-and keep your business world connected.
Learn how IT teams can protect against spear phishing tactics. Harry Sverdlove, chief technology officer of Bit9 offers a frank discussion about spear phishing - the most common technique used in today's advanced attacks.
Learn how to build a solid business case for your migration to Red Hat Enterprise Linux so you can run leaner, innovate faster, be more flexible and own the New Now.
Social media isn't about you; it's about everything around you. As you consider how your customers want to communicate with you, social media is something that can't be ignored. But what should your strategy be? Is social media "just another channel?" What kind of a plan makes sense for your contact center and for your customers? Join our experts as they share their insight and research results.
Hardware tokens were a popular method of strong authentication in past years but the cumbersome provisioning and distribution tasks, high support requirements and replacement costs have limited their growth. The additional log-in steps that hardware tokens require and the resulting user frustrations have limited adoption and make them impractical for larger scale partner and customer applications.
Sponsored Links
