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

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .