| |
|
| |
Business Case |
|
|
A business case captures the reasoning for initiating a project or task. It is often presented in a well-structured written document, but may also sometimes come in the form of a short verbal argument or presentation. The logic of the business case is that, whenever resources such as money or effort are consumed, they should be in support of a specific business need. |
|
An example could be that a software upgrade might improve system performance, but the "business case" is that better performance would improve customer satisfaction, require less task processing time, or reduce system maintenance costs. A compelling business case adequately captures both the quantifiable and unquantifiable characteristics of a proposed project. |
| |
|
| |
|
|
|
|
|
|
|
| |
|
| |
Check Point Report |
|
|
Completing a regular Check Point Report is a core project management activity. It allows you to keep staff on track, keep management informed of your progress and to seek guidance when needed. It also helps you to pull the entire team together, to focus them on delivering the project on time and within budget. |
| |
|
| |
|
|
|
|
|
|
|
| |
|
| |
Project Plan |
|
|
Planning is a process for accomplishing purpose. It is blue print of business growth and a road map of development. It helps in deciding objectives both in quantitative and qualitative terms. It is setting of goals on the basis of objectives and keeping in view the resources. |
|
A plan should be a realistic view of the expectations. Depending upon the activities, a plan can be long range, intermediate range or short range. It is the framework within which it must operate. |
| |
|
| |
|
|
|
|
|
|
|
| |
|
| |
Project Scheduling Guidelines |
|
|
Every Project should have a robust Project Schedule produced and maintained in a project planning tool to assist the Project Manager in controlling the project, throughout its lifecycle. |
|
The Project Scheduling Guidelines below explain what the key elements are when creating and maintaining an effective Project Schedule. |
| |
|
| |
|
|
|
|
|
|
|
| |
|
| |
QRC for Project Issue Resolution |
|
|
The purpose of issue management is to insure that any concerns recognized during a project are addressed in a timely manner and do not go unresolved until they become major problems. |
|
A quick reaction checklist ensures that all Risk and Issue procedures are consistent throughout programme and that risk and issue are managed homogeneously within projects. |
|
|
| |
|
|
|
|
|
|
|
| |
|
| |
Project Change Process |
|
|
The objective of Change Management is to ensure that standardised methods and procedures are used for efficient handling of all changes to controlled environment, in order to minimize the number and impact of any related incidents upon normal operational service. |
|
Change Management can ensure standardized methods, processes and procedures are used for all changes, facilitate efficient and prompt handling of all changes, and maintain the proper balance between the need for change and the potential detrimental impact of changes. |
|
|
| |
|
|
|
|
|
|
|
