Summary of "11c-01_-_Project_Monitoring"

Summary of Lecture 11c-01: Project Monitoring

This lecture focuses on project monitoring as a key aspect of project control during the execution phase. It emphasizes the importance of continuously tracking project progress against planned objectives to ensure successful project completion.

Main Ideas and Concepts

Project Monitoring Defined: Monitoring involves controlling the project by measuring actual work against planned objectives, activities, and subtasks.

What to Monitor:

Work completed vs. planned work
Quality of work
Status updates on work progress
Costs and expenditures
Team member attitudes and cooperation

Tools for Monitoring:

Gantt Charts: Visualize project progress and report status.
Resource Expenditure Tables: Track budget consumption and remaining funds.
Cloud-based Project Management Tools: Examples include Asana, Trello, and SharePoint (used at RPI), which provide shared spaces for document uploads, status tracking, and collaboration.

Frequency of Monitoring: Depends on acceptable delays; critical paths should be reviewed regularly to detect delays or slack and make necessary adjustments.

Methods of Monitoring:

Weekly progress reports
Design reviews
Status updates via email
Scheduled status meetings (in-person or virtual)

Progress Reporting:

Can be formal or informal depending on the audience (management, instructors, team).
Should include honest and transparent reporting of problems, questions, and progress.
Avoid vague progress percentages; use simplified categories: Not Started (0%), In Progress (50%), Complete (100%).
Testing and debugging time should be accounted for, not just design completion.

Types of Progress Reports:

Formal Long Report: Includes cover letter, cover page, appendices, detailed body with work completed, problems encountered, analysis, accomplishments, remaining work, and next steps.
Short Report: Memos, emails, mini design reviews covering tasks in progress, completed tasks, plans, and problems or roadblocks.

Handling Problems and Changes:

Always report issues early to enable corrective action and assistance.
Engage stakeholders early if changes are needed to avoid last-minute conflicts or penalties.
Transparency in reporting builds trust and facilitates decision-making.

Conflict Resolution Example: Scheduling conflicts (e.g., exams vs. sports commitments) require coordination and monitoring among involved parties to ensure accommodations.

Methodology / Instructions for Effective Project Monitoring

Monitor regularly; decide frequency based on project tolerance for delay.
Use visualization tools such as Gantt charts and resource tables for clear status communication.
Maintain honest progress reporting using clear categories (0%, 50%, 100%) to avoid confusion.
Report problems immediately, including roadblocks and questions, to solicit help.
Use appropriate reporting formats:
- Formal reports for upper management or detailed technical review.
- Short reports or emails for team updates and quick reviews.
Leverage technology by utilizing cloud-based project management tools for collaboration and documentation.
Engage stakeholders early by communicating any needed changes promptly.
Monitor team dynamics by tracking cooperation and morale as part of project health.

Speakers / Sources Featured

Primary Speaker: Miss Leveaux (lecturer delivering the content)
Referenced Tools/Systems:
- Asana, Trello (cloud project management tools)
- SharePoint system (RPI internal project space)

No other distinct speakers or external sources were explicitly identified in the subtitles.