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

Popular posts from this blog

Voice of the Customer (VoC) vs Voice of the Business (VoB)

  Tthe differences and strategic importance of Voice of Business (VoB) and Voice of Customer (VoC) in Lean Six Sigma: Voice of Business vs Voice of Customer: Aligning Strategy with Value In the world of Lean Six Sigma , success hinges on understanding and balancing two critical perspectives: the Voice of the Customer (VoC) and the Voice of the Business (VoB) . While both are essential for driving sustainable growth and operational excellence, they represent distinct priorities that must be harmonized for optimal results. 🔊 Voice of the Customer (VoC) Definition : VoC refers to the needs, expectations, preferences, and feedback of the customer—whether internal or external. Focus Areas : Product/service quality Delivery timelines Customer experience Responsiveness and support Methods of Capturing VoC : Surveys and interviews Focus groups Customer complaints and feedback Net Promoter Score (NPS) Goal : To ensure that processes and outputs are aligned with what the customer truly ...

Control Chart in Lean Six Sigma

Control Chart in Lean Six Sigma Introduction In Lean Six Sigma , a control chart is a fundamental statistical tool used to monitor process performance over time and ensure that improvements are sustained . It belongs primarily to the Control phase of DMAIC , where the focus is on maintaining process stability and preventing regression after improvements have been implemented. A control chart helps distinguish between normal process variation and abnormal variation that requires investigation and corrective action. What Is a Control Chart? A control chart is a time-ordered graphical display of process data with statistically determined limits. It answers a critical question: Is the process stable and predictable, or is something unusual happening? A typical control chart consists of: Center Line (CL) – the process average or mean Upper Control Limit (UCL) – upper boundary of expected variation Lower Control Limit (LCL) – lower boundary of expected variation Plotted data points o...

Defect Leakage

Defect leakage occurs on the Customer or End User side after the delivery of the application. Once the application has been released to the client, if the end user gets any kind of defect using the application, it is called "Defect leakage". Formula for Defect Leakage: Defect Leakage = Number of Defect found during next phase / ( Number of Defects found during testing + Number of Defects found during next phase) * 100 For Example, During the UAT production site, 50 defects were detected by the end users and 150 defects were detected throughout the QA process, including both the test site and the production site. Therefore, the defect leakage would be: Defect Leakage = (50/150)*100 Defect Leakage =33 % Reasons for Defect Leakage: Absence of stringent test cases walkthrough and review process. Environment differences. Missing test cases to cover appropriate condition. Poorly designed test case due to misunderstood requirements. Incorrect deployment in UAT or production. Use of ...