Module 3
1. Define Project Time Activities
• Purpose: Establish the specific tasks necessary to complete the project.
• Steps:
• Break down the project scope into smaller, manageable tasks.
• Identify dependencies among tasks (e.g., which tasks must precede others).
• Define milestones to measure progress and major deliverables.
• Tools: Work Breakdown Structure (WBS), task lists, and decomposition techniques.
2. Sequence Activities
• Purpose: Determine the logical order of tasks to ensure efficient workflow.
• Methods:
• Precedence Diagramming Method (PDM): Visualize task dependencies using:
• Finish-to-Start (FS): Successor starts only after predecessor finishes.
• Start-to-Start (SS): Successor starts simultaneously with predecessor.
• Finish-to-Finish (FF): Successor finishes only when predecessor finishes.
• Start-to-Finish (SF): Successor finishes based on predecessor starting.
• Output: Network diagrams (e.g., Activity-on-Node, Activity-on-Arrow).
3. Estimate Activity Resources
• Purpose: Identify and allocate resources required for each task.
• Steps:
• Assess resource types (human, material, equipment).
• Identify skill levels, availability, and constraints.
• Allocate resources efficiently using RACI charts or resource histograms.
• Considerations:
• Balance resources to avoid bottlenecks.
• Plan for support needs such as information systems or administrative help.
4. Estimate Activity Durations
• Purpose: Predict how long each activity will take.
• Methods:
• Use historical data from past projects.
• Leverage expert judgment from team members or consultants.
• Apply PERT Analysis:
• Formula: (Optimistic + 4 × Most Likely + Pessimistic) / 6.
• Accounts for variability and uncertainty in time estimates.
• Challenges: Account for interruptions, rework, holidays, and resource availability.
5. Develop Schedule (CPM and PERT)
• Critical Path Method (CPM):
• Focuses on the longest sequence of dependent activities (critical path).
• Helps identify tasks that directly affect project duration.
• Program Evaluation and Review Technique (PERT):
• Incorporates time variability using weighted time averages.
• Provides a statistical approach to predict project completion probability.
• Steps:
• Identify activities and dependencies.
• Create a network diagram.
• Calculate early start, early finish, late start, late finish, and slack for tasks.
6. Resource Loading and Leveling
• Resource Loading: Assign resources to tasks to meet project requirements.
• Resource Leveling:
• Adjust schedules to address resource overallocation.
• Delay non-critical tasks to balance workload.
• Output: Resource histograms, Gantt charts with adjusted task durations.
7. Control Schedule
• Purpose: Monitor progress to ensure adherence to the project timeline.
• Techniques:
• Use tracking tools (e.g., Gantt charts, Earned Value Analysis).
• Regularly update the schedule based on actual performance.
• Implement corrective actions through Integrated Change Control.
• Output: Updated schedules, variance reports, and performance metrics.
Module 4
1. Develop Project Charter
• Purpose: Formally authorize the project.
• Contents:
• Project purpose, objectives, and high-level requirements.
• Identified stakeholders and assigned project manager.
• Assumptions, constraints, and initial risks.
• Significance: Serves as the foundation for all project planning.
2. Develop Project Management Plan
• Purpose: Integrate plans for scope, schedule, cost, quality, and resources.
• Steps:
• Collect input from all stakeholders.
• Create subsidiary plans (e.g., Risk Management Plan, Communication Plan).
• Align with organizational strategies and objectives.
• Output: Comprehensive document guiding project execution and control.
3. Direct and Manage Project Execution
• Purpose: Perform tasks to deliver project outputs.
• Activities:
• Coordinate resources and stakeholders.
• Execute planned activities as per the schedule and scope.
• Manage communications and resolve issues as they arise.
• Output: Deliverables, work performance data, and change requests.
4. Monitor and Control Project Work
• Purpose: Compare actual progress with planned metrics.
• Steps:
• Use performance measurement tools like Earned Value Analysis.
• Identify deviations and analyze their impact on the project.
• Propose corrective or preventive measures.
• Output: Work performance reports, forecasts, and updates.
5. Perform Integrated Change Control
• Purpose: Manage changes to project baselines in an organized manner.
• Steps:
• Review change requests and assess impacts on scope, cost, and schedule.
• Approve or reject changes through a Change Control Board (CCB).
• Document and communicate approved changes.
• Output: Updated baselines, logs, and project documents.
6. Close Project
• Purpose: Formally complete the project or phase.
• Steps:
• Verify deliverables against acceptance criteria.
• Conduct lessons learned sessions and document findings.
• Archive project documents and release resources.
• Output: Final project report, signed-off deliverables, and lessons learned database.
