from DSSResources.com


What is solution-focused agile?

Daniel J. Power
Editor, DSSResources.com

Managers, project teams, and consultants should focus primarily on the present and future. We examine the past to learn from our mistakes, but we need to also examine “what will work” to deliver results in a given situation. We need to find an opportunity to succeed and a solution to a problem. Solution-focused Agile is a mashup of techniques from multiple disciplines that promote using reflection to encourage innovation and a "what works" solution attitude. Traditional Agile Retrospective meetings are a good addition to any work environment, but adding a more prospective, future-oriented component helps teams improve processes, handle issues and focus attention on solutions to barriers and problems.

Hagar (2019) explains that "Ninety-two percent of executives say agility is critical for the future of their business, yet only 4% of their transformation efforts are delivering agility. The leading causes for this gap are an entrenched legacy culture and general resistance to change. Responding to these challenges and delivering business agility may require more than Agile practices. Many organizations are discovering “solution focus” to be the missing piece of their transformation puzzle when it comes to transforming culture."

Finding solutions, delivering results, is important. Leaders, managers, and teams encounter problems and must find a means of solving a specific problem or dealing with a difficult situation. Problems don't usually "disappear", rather actions must be taken to remedy and resolve a problem. In some situations, doing nothing may resolve a problem, but evidence should suggest that is the best path.

Some intractable problems do exist that are hard, difficult, and seemingly impossible to solve. These problems benefit from "reframing". Framing refers to how one structures or presents a problem or an issue. Framing involves explaining and describing the context of the problem in an understandable manner. Stakeholders are the key to reframing or restating a problem. What is the problem? Who identified the problem? When and why? A well-stated is easier to solve than a poorly stated one and framing should reflect the attitudes and beliefs of stakeholders. A key to innovation and creativity is the framing of problems (Getzels (1975); Getzels & Csikszentmihalyi, 1976).

Problem finding is also often important. A problem can not be solved or resolved until it is adequately and appropriately identified. Problem finding is a thinking process in which a person articulates or states a barrier or issue that should be addressed, a question that needs to be answered, or a solution that is not working.

Doing Agile narrowly focuses on following a specific framework, its practices, and techniques. Being Agile means one broadly emphasizes agile principles and values, attitudes, and agile behaviors, cf., Abtin, 2018. Solution-focused agile means the team uses an agile framework, but the focus is on solving problems in the context of agile values. The guiding principles of agility, include: 1) creating a shared understanding and vision, 2) being adaptive and incremental, 3) being open and transparent with stakeholders, 4) thinking of and considering consequences, and 5) being value-driven, finding solutions that create value for stakeholders.

In general, reason and facts rather than passion should guide agile processes. Passion and emotion may influence ethical judgments, but in business situations, decision and project goals are generally set more rationally to meet customer needs and create value for stakeholders. Emotions do negatively and positively impact rationality, cf., Kirman, Livet, and Teschl (2010). Emotions like fear of failure may positively impact choosing a solution that best meets relevant decision goals and leads to project success. Become agile, be agile, and think agile.

References

Abtin, M., "The Agile Maturity Pyramid: What’s the difference between Doing Agile and Being Agile?" DXC.technology blog, May 6, 2018 at URL https://blogs.dxc.technology/2018/05/06/the-agile-maturity-pyramid-whats-the-difference-between-doing-agile-and-being-agile/

Camp, J., "Decisions are largely emotional, not logical: the neuroscience behind decision-making," BIG THINK blog, June 11, 2012 at URL https://bigthink.com/experts-corner/decisions-are-emotional-not-logical-the-neuroscience-behind-decision-making Getzels, J. W., "Problem-Finding and the Inventiveness of Solutions The Journal of creative behavior, 9(1) pp. 12-18, February 1975 DOI: 10.1002/j.2162-6057.1975.tb00552.

Getzels, J. W., & Csikszentmihalyi, M. (1976), "The creative vision: A longitudinal study of problem finding in art," Creative Education, Vol.4 No.9, September 6, 2013, New York, NY: John Wiley & Sons at URL https://www.scirp.org/(S(i43dyn45teexjx455qlt3d2q))/reference/ReferencesPapers.aspx?ReferenceID=932873

Hagar, M., "Solving the Transformation Puzzle with Solution-Focused Agile," Cutter Business Technology Journal, July 31, 2019 at URL https://www.cutter.com/article/solving-transformation-puzzle-solution-focused-agile-504341

Kirman, A., P. Livet, and M.Teschl, "Rationality and emotions," Philosophical Transactions of the Royal Society London B Biological Science, 2010 Jan 27; 365(1538): 215–219 doi: 10.1098/rstb.2009.0194.

Lerner, J. S., Y. Li, P. Valdesolo, and K. S. Kassam, "Emotion and Decision Making," Annual Review of Psychology, Vol. 66: pp. 799-823 (Volume publication date January 2015), https://doi.org/10.1146/annurev-psych-010213-115043 and at URL https://scholar.harvard.edu/files/jenniferlerner/files/annual_review_manuscript_june_16_final.final_.pdf

Pounds, W. F., The process of problem finding, MIT Research Report, 1965 at https://archive.org/details/processofproblem00poun/page/n13

Last update: 2019-08-02 02:40
Author: Daniel Power

Print this record Print this record
Show this as PDF file Show this as PDF file

Please rate this entry:

Average rating: 0 from 5 (0 Votes )

completely useless 1 2 3 4 5 most valuable

You cannot comment on this entry





DSS Home |  About Us |  Contact Us |  Site Index |  Subscribe | What's New
Please Tell Your Friends about DSSResources.COMCopyright © 1995-2015 by D. J. Power (see his home page).
DSSResources.COMsm is maintained by Daniel J. Power. Please contact him at djpower1950@gmail.com with questions. See disclaimer and privacy statement.


Google
 
Web DSSResources.com

powered by phpMyFAQ 1.5.3