Skip to main content

Problem Solving Skills

 Problem Solving is one of the key personalities of the project manager or the any individuals.

Problem Solving:

Problem solving is the powerful human activity, computers are the tools in problem solving but it is human who solves the problem.

The ability of the problem solving comes from doing it and need to pull many information and solutions to solve the problem.

Problem solving is the combination of experience, knowledge, process and art.

Problem Solving Process:

Process is the series of logical steps that followed to produce an optimum solution.

Time and Resources are the two constraints for the problem solving. The given problem needs to be solved with in specific time with available resources.


Skills required for solving the problem:
• Knowledge
• Motivation
• Experience
• Communication Skills
• Learning Skills
• Group Skills

Type of Problems:
1. Knowledge Problems
- When a person encounters a situation that he doesn’t understand
2. Troubleshooting Problems
-When equipment or software behaves in unexpected ways
3. Mathematical Problems
- Describe physical phenomena with mathematical models
Example: Find x such that 5X+5 = 25
4. Resource Problems:
There is never enough time, money, or equipment to accomplish the task. The resources get the problem solved in spite resource limitations.
5. Social Problems:
For example if a factory is relocated to where there is shortage of skilled worker, engineers should set up training program for employees.
6.  Design Problems:
Require creativity, teamwork, and broad knowledge to design the architecture

Difficulties in solving the problem:
Some of the reasons we do not find the most effective solutions to our problems. Identified few difficulties we are facing to solve the problem below:
• Not recognizing the problem
• Failure to use the known information
• Failure to analysis the data
• Approaching the problem with predefined mindset or Inflexible thinking
• Fear of making mistakes or looking foolish
• Fear of taking risks
• Lagging in decision making
• Monotonous work
• Expectations of others to help

Problem Solving Method:
1. Recognize and understand the problem:
Understand the problem by defining the input/outputs, known’s/unknowns and sketch the problem.
2. Gather Information:
Collect the relevant data and remove the unwanted data which leads confusions to the problem. List relevant questions to the problem based on the knowns and unknowns.
State all the assumptions and ensure during selection of the effective solution the assumptions are addressed.
3. Generate solution methods:
There are many approaches to solve the problem examples are mind mapping, fishbone diagram, SWOT analysis and others.
4. Redefine and Implement:
Evaluate the selected solution method selected in the above step. Identify the “best” solution based on the situation and environment and other factors.
5. Verify and Test:
Compare the solution with the problem statement, test the solution and don’t stop until you get the correct answer.

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

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

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