This post originated from an RSS feed registered with .NET Buzz
by Ranjan Sakalley.
Original Post: Definition of a "Wicked Problem"
Feed Title: Ranjan Sakalley
Feed URL: /error.htm?aspxerrorpath=/blogs/ranjan.sakalley/rss.aspx
Feed Description: (the life and times of a mock object)
Off late I have been using this term a lot, since I read about it in a Stephen Covey book.
A wicked problem is a problem that could only be defined by solving it, or part of it.
I have been busy currently on a product that manages more than a GB of
data transfer between servers and automates several workflows, and God
knows how many wincked problems have been defined till now. And there
are still many of them left to be solved.
A simple example of a wicked problem that I am going to face is software performance. Wonder if you can share some?
Previous Topic
