Proactively managing risks during the different phases of a project can have a significant impact on the project’s outcome. Explore four key factors that can help alleviate the workload of the project management team and lead to better project results.
Sometimes, the most valuable lessons an IT project manager learns are the result of wrong decisions. Here are five lessons to keep in mind as you try to prove yourself worthy of working for a mature organization and become a senior level IT PM.
When evaluating the acquisition of a company, many organizations emphasize the financial aspects but downplay facets of the consolidation dealing with project execution. This paper examines the major considerations and discusses how to improve the integration process to avoid negative impact.
Typically, effort estimates are overly optimistic, and there tends to be a good deal of over-confidence regarding their accuracy. Today, customers are more interested in knowing all of the pricing factors and pricing influencers in any service deal; effort estimation (being a direct input to service price) becomes a vital success factor in today's competitive business environment.
Can't use earned value because your cost data is confidential? Or because the actual costs are not accurate or itemized enough? No problem! Simply use the time assignments and completion percentages for project status and forecasting.
The attached workbook is useful for these many projects out there where no costing data can be used--or is not available--so the classic Earned Value Technique cannot be applied. It provides not only a progress tracking mechanism but also effort based project forecasting based on the above consideration.
In the webinar Eight Steps to Designing New Products for Business to Business Customers, Larry Micek took us through eight steps on how we can improve new product development success rates. The session was packed with information, and here are the questions and answers that came out of that session.
Einstein thought problems were more important than solutions and he preferred blackboards to business cases. Yet many cases read like a solution looking for a problem. John Finneran argues business cases should be built around the simple, fundamental technique of stating a problem and answering a question.