Project issues and risks, like zombies, move relatively slowly. It’s extremely rare that a project manager will be introduced to a project one day and be overwhelmed by the same failed project the next. Therefore, like survivors of a zombie apocalypse, project managers have time to prepare--and to look for those indications that projects are turning...
Using a step-by-step approach to budgeting will make your life easier in the long run, allow you to accurately answer any questions about project expenditures, make much more accurate future cost estimates for similar projects and generally give you more control over the project. Here's some help.
How are you with uncertainty? Do you revel in the possibilities or crave closure? Agile methods have a very different approach to requirements management that some people find empowering...and others find infuriating.
Incorporating robust requirements traceability guidelines into a project keeps a strong check-and-balance approach in place by making sure that each business need is truly identified as a genuine requirement, and that those requirements are then directly connected to deliverables.
Given the serious challenges that projects face with requirements, requirements management is no laughing matter. Yet to become successful at it, you might want to consider starting the discussion with a funny remark…
Requirements cannot stand alone. So why do we so often fail to acknowledge that connection to other project elements...and what is the consequence of that failure?
Gathering thorough and appropriate requirements is a critical piece of a successful project. Very often, even a well-scoped project can get derailed by poorly gathered or managed requirements. This article will outline four practices to help you breathe L.I.F.E. into your requirements.
A successful collaboration between project teams and stakeholders on requirements management will help prevent the projects from becoming another failure statistic.
Organizations are becoming increasingly strategic in the way that projects are reviewed and approved. The decisions that we make around requirements are some of the most fundamental on a project, but do we consider the right factors when making those decisions?
Managing requirements becomes much easier when they are well defined from the beginning so that you avoid confusion and rework. Here are some key concepts to help you get it right the first time.
There are times when a customer or a stakeholder demands that you change your process or method of managing something on the project. How can you cope with their demands without getting swept overboard? Keep these four things in mind.
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 5 page 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.