User:Financist/Project Management 101

Diagram showing PRINCE2 processes. The arrows represent flows of information.

Project Management 101

1.Balance needs of the

  • project
  • team
  • individuals on the team

2.Balance responses from the stakeholders

  • Know their objective
  • Have them define clear requirements

3.Build Plan

  • Breakdown of tasks required to achieve the Project Goal
  • Individual Team Members and their capabilities, training requirements, positioning and responsibilities

4.Costs

  • Spreadsheets.
Itemised Costings for team members, management, etc. (manning)
Run-up costs, Facilities/utilities maintenance and lease costings and any end-of-project liabilities
Total cost
  • Identify budget agreed to run the project
  • Manage people according to the plan
  • Conduct team meetings once a week (or every two weeks)

5.How much of the project process you want to apply:

Each change should have a formal change request and tracking.

6.Issue management and tracking.

  • Technical resources
  • Using Mailbox or Issue Tracking Software

7.Risk Management

  • List of issues that could happen/not happen.
Note any contractual obligations or key performance indicators that may affect available funding
Note areas of expenditure blowouts and other equivalent risks for example: "We have consultants available; they cost money but will reduce our risk"

9.Reporting process

  • Report issues that are change

10.Final:

  • Final Costs
  • Report of Delivery
  • Lessons learned
In theory Project Managers are using the Lessons Learned to improve the process

11.Speak clearly.

edit