Sometimes the temptation to work on an exciting project—and other times the pressure from the business executives to get the business—leads to agreement on unrealistic expectations. This article discusses the mistake of agreeing to unrealistic timelines and suggests a few ways on how this can be avoided—and the project kept under reasonable control.
It is through gaining a better understanding of the uncertainties—and better managing them in relationship to the project environment and stakeholders involved—that PMs may more effectively approach and complete their endeavors to contribute more value.
Earned value management is a technique that integrates scope, cost and time to highlight how the project has done in the past and predict how it is expected to do in the future. This article discusses a few basic concepts of EVM and is useful for anyone looking to get started on this topic, as well as for candidates preparing for certification.
Despite all of your best intentions, sometimes the project will be in trouble. If it is, it’s time to take a step back and learn how to deal with it. Here are some things to keep in mind as you try to stop seeing red.
Projects are the manifestations of scores of complex, unique activities that vary from project to project and industry to industry. But there are certain serious mistakes that are common in nature, and that are committed in many large projects. Learn how to deal with seven such major issues that are generally prevalent in almost all projects.
Managing while creating reserves is both a habit and an art. To prevent potential problems, it helps to follow five useful principles.
Every project manager has faced scope creep but may not appreciate the importance of project documentation. SCARs, an acronym for scope creep and action reports, reminds us that they are to be created and updated throughout the project and will prove to be valuable assets en route to continuous process improvement.
The project workflow framework enables even the inexperienced project manager to use detailed step-by-step guidance, examples, tools and practical advice, freeing experienced project managers to manage programs and portfolios and promoting better use of project resources to reduce the cost of projects across all industries.
In this article, we look at the key to schedule success, historical and repeatable tasks, why schedules fail, how to eliminate the target date tango and build a schedule defense that manages the risks.
Are you still blaming users for new requirements? Why is this all happening? Is it because of the lack of discipline among requirements holders, who just keep on asking for different things—often late in our projects—throwing a monkey wrench into our schedules and budgets?
Project managers must ensure that projects are aligned with business strategy and value creation for their company and its shareholders. The author demonstrates the importance of the bridge between the business and project worlds, even when there is not a clear link between their objectives. But one objective always remains the same: to create economic value.
Simply put, scope is the size of the project. But there’s more to it than that!
This checklist will assist you in minimizing scope creep, schedule extensions and project failure by evaluating whether the initial requirements are complete. This series of requirements attributes, quality checks, and examples provide a thorough review of what you plan to do.
The change request form should be used to formally initiate a request for change to a project. Types of change requests you can initiate by using this form include changes to scope, timeframes, deliverables, resources, milestones and expenditures.
Change is bound to happen. Make sure that you handle it correctly by following the proper procedures. This form will help you cover all your bases so change doesn't have to mean big surprises or project disasters.
This simple change request form will keep you mindful of what the proposed change is and the impact it will have.
How do changes get recorded, analyzed and approved on your project? This document contains guidelines for these procedures and more.
The statement of work (SOW) encompasses the goals, scope, deliverables, cost and schedule estimates, stakeholder roles, chain of command and communication guidelines for a project. Learn how to put a quality SOW together by studying its components.
Assess the scope, impact ranking and criticality of each business change required to implement a particular application package.
This procedure describes the process of testing software code or products by the test team. It documents the procedure for the entire testing cycle: generating test plans, scheduling tests, conducting tests and reporting test results. This procedure applies to new development, as well as major and minor releases, including customized solutions delivered to customers.
This Powerpoint presentation is a high-level view of the basics of planning and defining scope.
Use this form to capture the what, how and why of your proposed project change and to get sign-off from the brass.
This tool is designed to create service level agreement information for a justification or similar document. It is most useful for IT organizations that are too small to have a Project Management Office, but can use better control over linking project service level agreements with business objectives.
Are you intending to develop a project? You need a project notification sheet.
This document outlines the Business Scope, which is a description of the area of the business to be supported by the application package, including the specific business activities to be supported, the business objects to be managed and the organizations and sites to be supported.
Who's on first? What's on second? Don't know who's on third? When it comes to your project, you need to have this information at your fingertips. Use our definition of a project status report to make sure your team members provide the right information to the project manager.