Skip to main content

Monitor and Control project

Monitoring and Controlling is the largest and continuous part of the project management.

It keeps eye on everything that’s happing in/out of the project and adjusts as needed.  

A good project manager is constantly monitoring every single thing happing in the project. If you find the problem latter it’s hard and more expensive to solve it.

The below practices need to be followed by a project manager for an effective monitor and control of the project:

Project meetings:

Conduct the project meeting on daily (daily scrum) or weekly basis without fail and ensure that all the team members joins.

If the team is not co-located use the audio conference/video conference. Make the meeting shot, come up with action items and send the Minutes of Meeting (MoM) at the end of the meeting.

Need to follow up with team to close the action items on the agreed target closure date. Discuss on the status/issues and provide help required for the team work on the tasks.

If possible use the online tools to track the action items to closure.

Individual attention to team:

Pay the individual attention to team members by asking the status/problem facing/concerns/help needed. Make it informal, this will solve the communication gaps, team building and helps the project manager to bring the real picture of the status which is not captured in the project meetings.

Change Control Board Meeting:

Conduct the CCB meeting regularly to find the changes that really wanted to make for the project needs.

Decide the changes needed for the project in the CCB meeting.

Evaluate the technical, schedule, and cost impact of the change and make the decision with sponsor approval.

The changes needs to be tracked in Change Control Tracker with status of the change along with justification, impact if not implemented and others.

Collaborative contribution to issues/risks:

It’s very important that the issue and risks are updated on the daily or weekly basis and the necessary actions are taken to close the same.

Timely completion of time sheets:

The time sheets needs to be created by the project manager upfront and shared to the team. The team needs to fill the time sheet on daily basis. 

Need to ensure that the comments in the time sheet are provided properly and any deviations in the task need to be addressed and the future tasks needs to be changed to accommodate the deviations.

Project manger need to build the discipline to the team to enter the time sheet on daily basis or weekly basis.

Keep Eye on process checklist:

Keep the eye on the process checklist to make sure the process followed properly.

For example if you are running the weekly iteration in the agile project need to check the unit testing, code review and completed features are demoed on weekly basis.

Weekly status reports:

The project manager held with lot of work and it’s not sufficient to fill the template provided for the weekly status report.

The preparation of the week status report helps the project manger to think about what happened on this week, what gone wrong and right and find out the obstacles in the project.

Project Manager needs to re-plan the tasks planned ahead based on the weekly status.

Project Manger need to think on the scope, deliverables, dependencies, schedule and budget on every week and plan the actions accordingly.

Comments

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - archite

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir

Lessons learned from sprint retrospective meeting

Scenario: Team Missed Sprint Goals Challenge: A development team consistently missed its sprint goals, leading to frustration and a drop in morale. Team members felt overwhelmed by the workload and struggled to communicate effectively. Retrospective Insights: During the retrospective, team members openly discussed their challenges and frustrations. They identified bottlenecks in communication, unclear priorities, and unrealistic expectations. The team realized that individual workloads were not evenly distributed, causing burnout for some members. Lessons Learned: Effective Communication Matters: The team recognized the importance of clear communication. They committed to regular stand-up meetings, where everyone shared progress, blockers, and priorities. Balancing Workloads: The retrospective highlighted the need to distribute tasks more evenly. They decided to monitor workloads and adjust assignments accordingly. Setting Realistic Goals: The team acknowledged that setting achievable