Skip to main content

Problem solving techniques

Last post 03:21 am December 24, 2015 by Anonymous
No replies yet
03:21 am December 24, 2015

Hello everyone!

I want to share my technique for problem solving, if you have comments or other ideas I will glad to read them.

Ok, lets try to remember or imagine that or colleague came and said: "it was the last straw, I couldn't wait any more their failing build!". In case like that I am using technique below:
1) Except blaming, teach to use I language ("I can't make the commit cause build too much time is failed")
2) Ask about the solution from colleague who came with compliant("How do you think we can solve that problem?")
3) Accept or reject the solution ("I think we need opinions from other colleagues")
4) Determine scope and criticality. Try to find more facts, driven by emotions we often exaggerate the problem is scope.
a) What is blocking by that?
b) How much it effects capacity?
c) How often?
d) How many colleagues suffer from that?
5) Organize meeting when the criticality is very high. (Using retrospective rules)


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.