Skip to main content

Problems faced and How solved them

 Problems faced and How solved them


As a project manager, they daily face different problems. He needs to solve them effectively.

Refer my previous article on Problem Solving Skills..

Now we will go through the problems I have faced in my experience and how I solved them.

  

Problem 1: 

Lack of accountability:

A common reason for project failure. 

A team member is not showing interest in taking accountability for the tasks assigned to him, not attending meetings, and not providing status updates to the lead.

Solution:

I had a discussion with the developer and lead, to whom he reports.

He found that he focused on the negatives of the project.

Started Encourage the team member to open his eyes to see what we are working on and why it's important to the client, organisation, and team.

A culture of punishment can poison any seeds of creativity and innovation. So we started encouraging him, and once he met the goal, we promised him he would be nominated for an award and ensured that he would be awarded.

Slowly, we have started seeing improvements in his work.

Problem 2:

Unrealistic deadlines: 

Project estimation was created during the proposal and approved during the SOW.

The team was assigned to the project during the project's kickoff.

Unrealistic deadlines are often caused by insufficient estimation of teams' capabilities due to the above factors.

As a project manager, my role is to estimate, negotiate, and execute project timelines, along with setting the right deadline for each task based on every team member's experience and skillset.

Review and revise the plan frequently based on the status of the task.

Problem 3:

Inadequate stakeholder (customer) engagement:

Remember, engaging with stakeholders is not just about meeting project objectives; it’s about fostering collaborative relationships that contribute to organization’s projects’ overall success and longevity.

During one of the project executions, we faced delays in getting APIs from other external project teams.

We addressed this to the client manager during the WSR and MSR meetings, but there was no support from him due to inadequate engagement.

I started to involve them in the decision-making process and used the communication channel as per the SOW.

I created a group in Microsoft Teams and started addressing our concerns and impact on project deliverables due to a delay in API integration and building positive relationships.

The client manager started understanding the impact on project success, and the account manager also started involving himself in the group chat. Then the client manager arranged meetings with the API team and our team. Once we started opening the communication channel, the API team provided their plan for releasing the API's, and we also revised our plan for the integration of the API and republished it.

The problem was solved smoothly due to building a positive relationship and providing a proper status update.



Comments

Post a Comment

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 - ar...
Post a Comment
Read more

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...
Post a Comment
Read more

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more