Project Lifecycle and Initiation
Project+ covers the project lifecycle from initiation to closure, drawing on general PM best practices (not exclusively PMBOK). Project lifecycle phases: Initiation (define the project, get authorisation), Planning (define how the project will be executed), Execution (carry out the plan), Monitoring and Control (track progress, manage changes), Closing (formally end the project). Initiation documents: Project Charter (authorises the project — scope overview, objectives, sponsor, PM, initial budget and schedule), Statement of Work (SOW — describes what the project will deliver, often used in procurement), Business Case (justifies the investment — cost-benefit analysis, expected ROI). Stakeholder identification: anyone affected by or able to affect the project — internal (executives, end users, IT teams) and external (customers, vendors, regulators). Stakeholder register: documents each stakeholder's name, role, contact info, interest, influence level, and communication requirements. An engaged sponsor is the most important factor in project success — they remove organisational blockers.
Planning and Scheduling
Project+ planning focuses on practical tools. Scope definition: what the project will deliver (in-scope) and what it will NOT deliver (out-of-scope — explicitly stating out-of-scope prevents scope creep). Work Breakdown Structure (WBS): hierarchical decomposition of deliverables into work packages — used to estimate duration, cost, and assign responsibility. Resource planning: identify team members, tools, materials, and facilities needed. Resource histogram: bar chart showing resource demand over time — reveals over-allocation (a person assigned more than 100% in a time period). Schedule tools: Gantt chart (bar chart showing activities against a timeline — most common for IT projects, shows dependencies and milestones), Critical Path Method (identify the longest path — project duration and float for each activity), PERT (Program Evaluation and Review Technique — three-point estimation: optimistic, pessimistic, most likely — weighted average: (O + 4M + P) / 6). Milestones: zero-duration events that mark significant achievements — used as schedule checkpoints and go/no-go decision points.
Risk, Communication, and Change Management
Risk management for Project+: risk is any uncertain event that could impact project objectives positively (opportunity) or negatively (threat). Risk register: documents each risk with probability, impact, risk score (probability x impact), risk owner, and response strategy. Responses for threats: Avoid (change the plan to eliminate the risk), Transfer (contract, insurance), Mitigate (reduce probability or impact), Accept (acknowledge and move on — passive or active with contingency). Communication plan: defines what information is communicated, in what format, how frequently, to whom, and by what channel. Meetings: kickoff meeting (introduce team, confirm objectives, establish expectations — most important communication event), status meetings (regular progress updates — keep short and structured), retrospectives/lessons learned (capture what worked, what did not — improve future projects). Change management: changes to scope, schedule, or budget must go through a formal change request process — assess impact, get approval from the appropriate authority, update the plan and baselines, communicate to stakeholders.