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

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more

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

4 T's - Technology, Time, Teamwork, Transparency

 1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished.  3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...
Post a Comment
Read more