Project Charter
Project Charter
Project Charter refers to a statement of objectives in a project. This statement also sets out detailed project goals, roles and responsibilities, identifies the main stakeholders, and the level of authority of a project manager. It acts as a guideline for future projects as well as an important material in the organization's knowledge management system. The project charter is a short document that would consist of new offering request or a request for proposal. This document is a part of the project management process, which is required by Initiative for Policy Dialogue (IPD) and Customer Relationship Management (CRM).
Business Case
This outlines the need for a project charter to take place. A business case should set out the benefits gained from carrying out a project charter. Benefits need not only be in terms of finance such as revenue, cost reduction, etc., but also the benefit that the customer receives. Following are the characteristics of a good business case: The reasons of undertaking the project. The benefits gained from undertaking the project now. The consequences of not doing the project. The factors that would conclude that it fits the business goals.
Project Scope
As the name denotes, it refers to the scope that the project will give the business if they undertake the project. Before doing a project, the following concerns need to be addressed: The within scope and out of scope needs to be considered. The process that each team will focus upon. The start and end points for a process. Availability of resources. Constraints under which the team will work. Time limitations . The impact on the normal workload if the project is to be undertaken.
Conclusion:
The project charter is not only a tool that is used for planning projects but also a communication mechanism that acts as a reference. A well-planned project with an effective communication plan will definitely bring in success for the project undertaken at hand. Therefore, the Project Charter should be one of the frequently referred documents in a project and the entire project team needs to be aware of the content of the Project Charter. This is a key element for a successful project.
Unit Price
In this model, the project is divided into units and the charge for each unit is defined. This contract type can be introduced as one of the more flexible methods compared to fixed price contract. Usually, the owner (contractor/client) of the project decides on the estimates and asks the bidders to bid of each element of the project. After bidding, depending on the bid amounts and the qualifications of bidders, the entire project may be given to the same service provider or different units may be allocated to different service providers. This is a good approach when different project units require different expertise to complete.
Cost Plus
In this contract model, the services provider is reimbursed for their machinery, labour and other costs, in addition to contractor paying an agreed fee to the service provider. In this method, the service provider should offer a detailed schedule and the resource allocation for the project. Apart from that, all the costs should be properly listed and should be reported to the contractor periodically. The payments may be paid by the contractor at a certain frequency (such as monthly, quarterly) or by the end of milestones.
Incentive
Incentive contracts are usually used when there is some level of uncertainty in the project cost. Although there are nearly-accurate estimations, the technological challenges may impact on the overall resources as well as the effort. This type of contract is common for the projects involving pilot programs or the project that harness new technologies. There are three cost factors in an Incentive contract; target price, target profit and the maximum cost. The main mechanism of Incentive contract is to divide any target price overrun between the client and the service provider in order to minimize the business risks for both parties.
Conclusion
Selecting the contract type is the most crucial step of establishing a business agreement with another party. This step determines the possible engagement risks. Therefore, companies should get into contracts where there is a minimum risk for their business. It is always a good idea to engage in fixed bids (fixed priced) whenever the project is short-termed and predictable. If the project nature is exploratory, it is always best to adopt retainer or cost plus contract types.
The Workflow
Have you seen process flow diagrams? If yes, then activity diagrams takes the same shape. Usually there are two main shapes in activity diagrams, boxes and arrows. Boxes of the activity diagram indicate the tasks and the arrows show the relationships. Usually, the relationships are the sequences that take place in the activities. Following is an example of activity diagram with tasks in boxes and relationship represented by arrows.
This type of activity diagram is also known as activity-on-node diagram. This is due to the fact that all activities (tasks) are shown on the nodes (boxes). Alternatively, there is another way of presenting an activity diagram. This is called activity-on-arrow diagram. In this diagram, activities (tasks) are presented by the arrows. Compared to activity-on-node diagrams, activity-on-arrow diagrams introduce a little confusion. Therefore, in most instances, people often use activity-on-nodes diagrams. Following is an activity-on-arrow diagram:
Step 1:
First of all, identify the tasks in the project. You can use WBS (Work Breakdown Structure) for this purpose and there is no need to repeat the same. Just use the same tasks breakdown for the activity diagram as well. If you use software for creating the activity diagram (which is recommended), create a box for each activity. Illustrate all boxes in the same size in order to avoid any confusion. Make sure all your tasks have the same granularity.
Step 2:
You can add more information to the task boxes, such as who is doing the task and the timeframes. You can add this information inside the box or can add it somewhere near the box.
Step 3:
Now, arrange the boxes in the sequence that they are performed during the project execution. The early tasks will be at the left hand side and the tasks performed at the later part of the project execution will be at the right hand side. The tasks that can be performed in parallel should be kept parallel to each other (vertically). You may have to adjust the sequence a number of times until you get it right. This is why software is an easy tool for creating activity diagrams.
Step 4:
Now, use arrows to join task boxes. These arrows will show the sequence of the tasks. Sometimes, a 'start' and an 'end' box can be added to clearly present the start and the end of the project. To understand what we have done in the above four steps, please refer to the following activity diagram:
Conclusion
Activity diagrams can be used for illustrating the sequence of project tasks. These diagrams can be created with a minimum effort and gives you a clear understanding of interdependent tasks. In addition, the activity diagram is an input for the critical path method.