Managing while creating reserves is both a habit and an art. To prevent potential problems, it helps to follow five useful principles.
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.
¿Porque Debes Medir?, para evaluar el desempeño, porque buscar el porque de las cosas? Para buscar respuestas?by
Si no se mide lo que se hace, no se puede controlar y si no se puede controlar, no se puede dirigir y si no se puede dirigir no se puede mejorar, No tienes un norte definido en donde se posiblemente se comenten errores, lo cual se traduce en perdida de dinero, tiempo y en lo más importante en un cliente insatisfecho.
It’s frustrating to work on projects when the client or the customer keeps moving the target you're trying to hit--whether that be requirements, a date or even the vision for the project. How does a project manager fight this moving target and still deliver on time?
Once we share a ballpark estimation, there will be a follow-up question: “How did you get these numbers?” Then we need justification. Is there any easy and simple way to get this done? Yes! Use this article in conjunction with the Project Estimation Calculator template.
If you cannot make a plan to have the right people at the right time, then your project will not succeed. But how do you arrive at that plan with the number of resources? And how do you ensure that the number of people is right, and the start and finish dates are correct? It all starts with estimating.
Everyone focuses on preventing scope creep and trying to control the scope, but there are times when it's appropriate to actually increase the scope. Project managers need to be ready to handle that situation as well…are you?
Assumptions are some of the biggest culprits in scope creep, misunderstandings and successful projects being declared failures. This article will provide examples of each--and ways to take the assumptions out of the picture and make your project a success.
Change is inevitable, and the only thing that is certain is change. While we can all agree to this, it is imperative that all project managers understand the impact of scope changes to projects that are in the pipeline or the execution phase.
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.