BUS 528 - Chapter 4 Ideas

1. Project rules are the foundation
a) Agreement on the goals of the project among all parties involved
b) Control over the scope of the project
c) Management support

2. Publish a project charter
Because projects are unique and temporary, a project manager’s position and authority are temporary. The charter clearly establishes the project manager’s right to make decisions and lead the project. A charter is powerful, but it is not necessarily complex.

3. Statement of work (SOW)
A SOW answers many questions about a project, including the purpose, scope, deliverables, and chain of command. Clearly documented and accepted expectations begin with the statement of work. It lists the goals, constraints, and success criteria for the project—the rules of the game.
SOW is for members of the same organization. Contract might be needed if the team is consists of multiple organization. Although it is used to manage expectations and establish agreements, much like a contract, the SOW as it is described here is not meant as a substitute for a contract.

4. Responsibility matrix
A responsibility matrix lays out the major activities in the project and the key stakeholder groups. Using this matrix can help avoid communication breakdowns between departments and organizations because everyone involved can see clearly who to contact for each activity. The steps involved:
a) List the major activities of the project.
b) List the stakeholder groups.
c) Code the responsibility matrix - RACI
d) Incorporate the responsibility matrix into the project rules

Even though there are a lot of paper works on project management but these papers track the project well and ensure the success of the project. Update those forms whenever changes happen to the project.