Rebel’s Guide to PM

AUGUST 7, 2023

Identify the problem First, it’s important to understand what caused the issue in order to determine how best to resolve it. You’d be surprised at how many managers don’t bother to find the root cause of the problem to truly understand it. It involves identifying the cause of a problem and then finding ways to address it.

Technical Review 327

Technical Review Monitoring Consulting Development Team Review 327

Planio

OCTOBER 9, 2023

How do they cause issues for your team? How do they cause issues for your team? These beliefs are often false and cause you to feel low, kill off your motivation, and negatively impact your productivity. Jump to a section: What are limiting beliefs? The 6 worst limiting beliefs for project managers 1. It will fail.”

Underperforming Technical Team 88

Underperforming Technical Team Risk Management Risk Controlling 88

Scrum.org

AUGUST 3, 2021

If a team is confronting a problem and is unsure of the exact root cause, the 5 whys exercise taken from the business analysis sector can help get to the bottom of it. The team then asks why that problem exists, writing that answer in the box below. Second, ask what’s holding you back or what’s not going well.

SCRUM 222

SCRUM Technical Review Process Leadership 222

Project Risk Coach

OCTOBER 29, 2018

Let's discuss a simple but powerful tool for solving problems - the Cause and Effect Diagram (alias Fishbone Diagram). Steps to Create a Cause and Effect Diagram Identify and clarify the problem. Identify the cause categories. Brainstorm causes for each category. Add causes to the appropriate category lines.

Defining 191

Defining Risk Process Planning 191

Rebel’s Guide to PM

JULY 22, 2023

Step-by-step decision-making process overview There are 5 steps in the decision-making process in project management. Step 5: Monitor Outcome Once the best solution is implemented, monitor the impact on the project. It is always a good idea to discuss this at project kickoff to ensure that they are always appropriately informed.

Software Review 303

Software Review Monitoring Risk Management Governance 303

nTask

OCTOBER 29, 2020

Of the 20% that undertake process improvements , 5% record little to no success, 28% experience success limited to individual departments but do not record enterprise-level success, and 19% experience success after significant difficulties. Such steps may cause defects and errors. One way to do this is through the 5 Whys method.

Process 133

Process Technical Review Lean Software Review 133

LiquidPlanner

OCTOBER 17, 2017

To get at the core of why the unexpected event or challenge happened, you need to dig deeper. Instead of stopping at one, you need to ask why five times. The 5 Whys. The core idea of the 5 Whys system is exactly what it sounds like: ask the question “Why?” “ Why is the circuit overloaded?

Manufacturing 116

Manufacturing Monitoring Process Defining 116

Project Bliss

JANUARY 30, 2019

Learn about problem-solving tools with these posts: 5 Whys Root Cause Analysis: a Problem-Solving Tool to Get to the Root of the Problem. The ability to walk a team through problem-solving sessions and come up with solutions will get you noticed, in a good way.

Executing 185

Executing Planning 185

Rebel’s Guide to PM

JULY 19, 2021

There are 5 steps the decision-making process in project management. Step 5: Monitor Outcome. Using a framework is important to ensure consistency in how decisions are made, and to help minimize or remove any personal bias around certain solutions or options that might unfairly sway the outcome. Step-by-step overview. In summary.

Process 437

Process Software Review Monitoring Risk Management 437

Scrum.org

MARCH 19, 2023

Setting up the Session I ran the session on ChatGPT on Wednesday, March 15, from 5:40 am CET to 6:30 am CET on the models GPT-3.5 We’ll ask the team to identify the root cause of each problem and then use TRIZ to generate new ideas for addressing those issues. Instead of TRIZ, I would use “Nine Whys” or “What.

ChatGPT 160

ChatGPT SCRUM Technical Review 2020 160

Wrike

FEBRUARY 3, 2021

It’s called the five whys. . What is the five whys method? The five whys method is a problem-solving technique that helps you get to the root cause of a problem. Using this technique, you’ll uncover cause and effect relationships and ultimately uncover how processes and projects can be improved in the future.

PMI 45

PMI Risk Management Controlling Process 45

Teamweek

APRIL 20, 2022

Analyze the root cause – Next, great problem-solvers seek to understand why the problem exists by rooting out the underlying cause. Understanding a Problem – 5 Whys. If you’re trying to get your head around a problem, the 5 whys technique is a great way to uncover the root cause.

Underperforming Technical Team 52

Underperforming Technical Team Risk Management Risk Innovation 52

Project Bliss

FEBRUARY 11, 2019

Which problems seem to be causing the most pain or impact? Then drill down a bit more by asking questions to get to the root cause. Continue to ask “Why?” ” after each problem statement until you know you’re at the root cause of the problem. Tool: 5 Whys?.

Underperforming Technical Team 204

Underperforming Technical Team Energy Leadership Risk Management 204

Planview

JANUARY 24, 2019

These problems, as mentioned, were cited by a large percentage of respondents in Planview’s resource management study as a primary cause of their resource management pains. Part 5: How Risk Management is Crucial to Project Management. So, then we must ask: Why are projects late? But what’s really at the heart of the matter?

Estimate 89

Estimate Governance Government Risk Management 89

Proofhub

AUGUST 9, 2023

It uses the following framework to improve that constraint: The Five Focusing Steps: Identify, Exploit, Subordinate, Elevate, and Repeat The Thinking Processes: What needs to be changed, what should it be changed to, and what actions will cause the change? It focuses on throughput accounting.

Process 78

Process Manufacturing Lean Monitoring 78

Project Bliss

SEPTEMBER 25, 2019

Conflict on teams can cause people to immediately feel threatened, intimidated, or anxious. More on communication skills: 5 Styles of Effective Listening That Will Make You Smarter. More on getting support and buy-in for your projects: 5 Critical Reasons the Best Project Managers are in Sales & Marketing, To o.

Innovation 136

Innovation 136

Project Bliss

AUGUST 29, 2019

But after conducting a 5 Whys Root Cause Analysis , you all realize and agree the support calls are from users who have just adopted new software you’ve rolled out. Impact – the impact this is causing for the team, or the problems you’re experiencing as a result of the current state. . Helpful tips.

2020 149

2020 Software Closing Monitoring 149

PM Basics

SEPTEMBER 7, 2022

Root cause analysis. Poor requirements are the number one cause of project failure. 5: Use Brainstorming and Interviews Techniques for Deeper Analysis. 6: Apply Root Cause Analysis for Systematic Risks. To group all identified risks by the root cause. Checklists (risk categories). Interviews.

Risk 109

Risk Software Review Underperforming Technical Team Risk Management 109

Scrum.org

APRIL 2, 2019

Ask a Scrum practitioner and they'll give you 3-4, maybe 5, if he’s real good, values Scrum holds dear. As you are past recognizing and naming the emotions and things that cause those, it’s time to ask, “Why does it make me feel that way? What is the root cause for the emotion?” What are we talking about here?”

Underperforming Technical Team 119

Underperforming Technical Team Construction SCRUM Controlling 119

Planio

NOVEMBER 11, 2020

5 steps to run an effective sprint retrospective and make real change. Dig deeper into the issues with the “5 whys”. 5 steps to run an effective sprint retrospective and make real change. What are some red flags to watch out for during a sprint retrospective? Prepare and gather your tools. Start, Stop, Continue.

Underperforming Technical Team 135

Underperforming Technical Team Development Team Review SCRUM Risk Management 135

Project Bliss

MARCH 19, 2019

This blog has already looked at some core skills for problem solving including the 5 Whys and a simple step-by-step process for solving problems. Problems have roots that go deep! So you are left with the alternative of facilitating the problem solving yourself, as the project manager. Look for Relevant Information.

Risk Management 216

Risk Management Process Risk 216

Scrum.org

MAY 7, 2019

With strong roots in complexity science, and collected by Keith McCandless and Henri Lipmanowicz , all Liberating Structures implement five design elements and ten principles. One of the main causes of Zombie Scrum is that teams often have no idea why they are even doing Scrum. Let’s build communities that cause change!

SCRUM 188

SCRUM Development Team Review Leadership 2018 188

nTask

SEPTEMBER 12, 2019

Reverse brainstorming instead asks the participants to list all of the problems and the ways to cause problems. When all of the team members have listed all of the ways to cause problems, then you will be properly ready to solve them because you would know what can cause potential issues in any current or future strategy.

Process 114

Process Risk Management Agile Risk 114

Planio

SEPTEMBER 13, 2022

Why you’re getting so many more mental blocks than usual. The 7 main causes of mental blocks in the workplace. The 5-minute activity to break through your mental blocks. The 7 main causes of mental blocks in the workplace. That’s why team workload management is so important). Then, continually ask yourself “Why?”

Closing 78

Closing Agile Planning Leadership 78

Scrum.org

MAY 5, 2022

Make the purpose of your work clear with Nine Whys. Why is this activity important for you? Discover and build on the root causes of success with Appreciative Interviews. Every day, I would give myself a rating on a scale of 1–5. Use Troika Consulting to offer practical help to each other.

SCRUM 215

SCRUM Underperforming Technical Team Energy Consulting 215

Herding Cats

MARCH 21, 2016

Let's start with Dean Gano's introduction to Apollo Root Cause Analysis , which is a George Bernard Shaw quote so fitting to the discussion of ignoring the root cause and going straight for a solution to the symptom - in many cases an Unnamed symptom. Provide EVIDENCE to support the existence of each cause.

Estimate 43

Estimate Finance Manufacturing Governance 43

Herding Cats

MARCH 15, 2016

So in the end nothing is fixed, the dysfunction is not identified, the Root Cause is not identified, and therefore is it not possible to claim Not Estimating will fix anything, for the simple fact that the problem has not been defined. If you want to learn how to do this - and not follow the naive 5 Whys - read this.

Estimate 44

Estimate Defining 44

Herding Cats

OCTOBER 24, 2018

When you hear project failure statistics, and no Root Cause for those numbers, there is no hope that any suggested corrections can be credible. A Corrective Action addresses the cause of the non-conformance do it does not reoccur. A Cause is an answer to a why question. A fact is a cause supported by evidence.

2014 45

2014 Aerospace 2011 2013 45

Herding Cats

OCTOBER 28, 2016

In a recent Blog post titled Precision it is suggested Precision (or the implication thereof) is perhaps the root problem of most, if not all dysfunction related to estimation. . First, without finding the root cause of the estimating gaps, the quest for a solution is an open loop problem. Why is this the case?

Estimate 28

Estimate Performance Measurement Information Technology Risk Management 28

Project Pulse Journal

NOVEMBER 18, 2023

Identify deviations from the project schedule and understand their root causes. As a project progresses, external factors, stakeholder and customer/client expectations, or internal changes may cause the project to drift from its primary vision. 5 Whys, Ishikawa Diagram, etc.). Ask yourself why it happened.

Monitoring 40

Monitoring Controlling Technical Review Software Review 40

Planio

APRIL 21, 2021

5 brainstorming techniques that S.U.C.K. (in 5 brainstorming techniques that S.U.C.K. (in For example, use question bursts to come up with the right problems, rapid ideation to think up potential solutions, 5 Whys to dig further, and then Mind Mapping or others to organize and decide on a plan of attack. in a good way).

Underperforming Technical Team 88

Underperforming Technical Team Innovation Process Energy 88

Herding Cats

MARCH 12, 2016

But that dysfunction is not "caused" by the estimate. It may a "symptom" of poor estimates, but not the "cause." Without first identifying the Root Cause of the symptom, not suggestion for improvement will be effective. Root Cause Analysis is the key here. Just the conjecture of a symptom.

Estimate 46

Estimate Cadence Risk Management Risk 46

ProProject Manager

AUGUST 27, 2018

On page 236 of the Project Management Book of Knowledge (PMBOK), 5th edition, the only reference to “problem statement” appears in the Project Quality Management section under Cause and Effect Diagrams: “The problem statement typically describes the problem as a gap to be closed or as an objective to be achieved.”. The 5-Why’s.

Technical Review 52

Technical Review Closing PMI Software Review 52

Herding Cats

MARCH 19, 2017

This is a serious mistake unless we have done the Root Cause Analysis of the observed problem. It may turn out what is being observed is the symptom of a root cause that was not understood by the people that hired us. Why are you seeing what you're seeing? What are the possible causes of these observations?

Estimate 35

Estimate Software Developers Software Development Governance 35

Teamweek

MARCH 5, 2020

There are many causes for productivity bottlenecks. To find the source of the bottleneck, you have to dig deep using the 5 Whys Framework. The 5 Whys is a technique originally implemented by Sakichi Toyoda from Toyota Motors in the 1930s. It helped find the root cause of errors.

Technical Review 17

Technical Review Software Review Estimate Consulting 17

ActiveCollab

OCTOBER 2, 2023

THE 5 WHYS ANALYSIS This problem-solving technique aims to uncover a problem's underlying cause by repeatedly asking the question, "Why?". The goal is to dig deep and identify the root cause rather than addressing surface-level symptoms.

Process 36

Process 36

ProProfs Project Management

MAY 4, 2021

The cause and effect analysis or the fishbone diagram techniques are employed to visually represent the causes of defects of the process. Other than asking questions, you may apply various types of business process improvement tools, for example, the 5 Whys, which also helps in detecting inefficiencies and problems in the system.

Process 52

Process Planning Technical Review Underperforming Technical Team 52