Product ideation in groupPlanning
Implementing practices like Event Storming, Lean Canvas, 25/10 Crowdsourcing, 1-2-4 All, User Story Mapping
The practice of production ideation in group
The term “Ideation” has been forged by John Stuart Mill back in the XIXth century [Godin 2018] and deals with the creation process to generate innovative ideas. In the agile culture, there are many creative techniques to generate, develop, and communicate new ideas, notably:
- the well known Brainstorming [Higgins 1994]
- Yasuo Matsumura’s Lotus Blossom [Higgins 1994]
- the SCAMPER technique [Serrat 2017]
- Von Oech’s dodecahedron technique [Von Oech 2011]
- De Bono’s six thinking hats [De Bono 1999]
- Event Storming [Brandolini 2019]
All those ideation techniques are actually more efficient when performed in group for several reasons such as:
- the combination of everyone’s point views provides more valuable insights with lower fallacies
- it uncovers implicit knowledge
- everyone gets on the same page
- it recovers enthusiasm
The underlying rationale can be provided with the Panarchy model [Gunderson 2002] [Moustier 2020] for ideation workshops gathers three levels of “ecocycles”:
- the individual experience
- the ideation workshop
- the market expectations
Within the Panarchy model, an ecocycle figures the evolution of a subsystem where
- α is the change starting phase of a subsystem
- r is the exploration of the subsystem to face the change
- K occurs when the exploration enables accumulating effort and resources as long as the exploration outcomes is compatible with the acquired resources
- and Ω , the releasing phase when the subsystem collapses and releases part of the accumulated resources, the so-called “memories”
Still, according to the Panarchy model, ecocycles are linked when subsystems influence each other's: when a subsystem reaches the Ω phase, it releases part of its resources to the linked ecocycle forcing it to enter its own α phase. The links between individuals, team and market also build a double loop learning structure that helps to reach the “good product” instead of a solution that would be simply compliant with an individual (say the Business Analyst or the Product Owner) point of view.
The ideation workshop merges individual “memories” into a common knowledge that should be more representative of the market needs.
Impact on the testing maturity
Ideation is not only a matter of making tacit needs into explicit requirements with a social process [Nonaka 1998]. Such a phenomenon is also met when it comes to architecture [Beck 2001] [Leffingwell 2008][Larman 2010][Moustier 2020]. Actually, this emerging approach helps to raise "Architecturally Significant Requirement” (ASR) [Moustier 2019-1] [ASR 2021] from the many points of view and also align everyone on a common technical view that would be required from a subsidiarity point of view [SAFe 2021-9][Appelo 2010][Moustier 2020]. To enable group design, “Model Storming” [Galiber 2019] can be pretty useful for there is no monopoly on innovation [Leffingwell 2008].
Group ideation is also relevant when it comes to coding. While coding alone, the Developer’s refactoring ability is actually naturally narrowed by algorithmic and compiling matters; this limit can be overcome notably with Pair programming and eventually Mob programming to let better ideas emerge from the coding attendees.
Finally, testing goes just the same. Sprint refinement in “3 Amigos” mode contributes to improving a Product Backlog Item (PBI). Moreover, the ATDD practice is also much more efficient when the whole team is involved than when only Testers provide test automation [Ferguson 2017b][Moustier 2020] which leads to the 4th principle of agile architecture “They build it, they test it” - [Leffingwell 2008].
Agilitest’s standpoint on product ideation
Agilitest uses a #nocode technology [Forsyth 2021]. This approach enables fast skill ramp up and therefore the adoption of test automation and ATDD become really simple and thus group product ideation.
To discover the whole set of practices, click here.
To go further
- [Appelo 2010] : Jurgen Appelo - « Management 3.0: Leading Agile Developers, Developing Agile Leaders » - Addison Wesley - 2010 - ISBN : 978-0321712479 - voir aussi https://fr.slideshare.net/jurgenappelo/agile-management-leading-teams-with-a-complex-mind/
- [ASR 2021] : Wikipedia – JAN 2021 - https://en.wikipedia.org/wiki/Architecturally_significant_requirements
- [Beck 2001] : Kent Beck et al. - « Manifeste pour le développement Agile de logiciels » - 2001 - http://agilemanifesto.org/iso/fr/manifesto.html
- [Brandolini 2019] : Alberto Brandolini - « Introducing EventStorming » - Leanpub - 2019 - https://leanpub.com/introducing_eventstorming
- [De Bono 1999] : Edward De Bono - AUG 1999 - “Six Thinking Hats” - ISBN 9780316178310
- [Ferguson 2017b] : John Ferguson - « Broad brushes and narrow brushes: there’s more to BDD than Given/When/Then » - 29/MAR/2017 - https://www.linkedin.com/pulse/broad-brushesnarrow-theres-more-bdd-than-john-ferguson-smart/
- [Forsyth 2021] : Alexander Forsyth – JAN 2021 - « Low-Code and No-Code: What’s the Difference and When to Use What? » - https://www.outsystems.com/blog/posts/low-code-vs-no-code/
- [Galiber 2019] : Flavius Galiber, III - « Lean-Agile MBSE: Best Practices & Challenges » - SAFe Summit 2019 - 29/SEP - 04/OCT/2019 - https://vimeo.com/372960506
- [Godin 2018] : Christian Godin - OCT 2018 - “Encyclopédie conceptuelle et thématique de la philosophie” - ISBN 9791026708063, lire en ligne
- [Gunderson 2002] : Lance H. Gunderson & C. S. Holling - « Panarchy - Understanding Transformations in Human and Natural Systems » - Island Press - ISBN 1-55963-857-5
- [Higgins 1994] : James M. Higgins - 1994 - “101 creative problem solving techniques” - ISBN 1-883629-00-4
- [Larman 2010] : Craig Larman, Bas Vodde - « Practices for Scaling Lean & Agile Development - Large, Multisite, and Offshore Product Development with Large-Scale Scrum » - Addison-Wesley - 2010 - ISBN-13: 978-0-321-63640-9
- [Leffingwell 2008] : Dean Leffingwell&Ryan Martens & Mauricio Zamora - AUG 2008 - “Principles of Agile Architecture” - https://scalingsoftwareagility.files.wordpress.com/2008/08/principles_agile_architecture.pdf
- [Moustier 2019-1] : Christophe Moustier – JUN 2019 – « Le test en mode agile » - ISBN 978-2-409-01943-2
- [Moustier 2020] : Christophe Moustier – OCT 2020 – « Conduite de tests agiles pour SAFe et LeSS » - ISBN : 978-2-409-02727-7
- [Nonaka 1998] : Ikujiro Nonaka & Noboru Konno - 1998 - “The concept of `Ba': Building a foundation for knowledge creation.” - https://www.semanticscholar.org/paper/The-Concept-of-%E2%80%9CBa%E2%80%9D%3A-Building-a-Foundation-for-Nonaka-Konno/355bd3020ebad1f2a92c9ebefdd619bc0d87c7b5
- [SAFe 2021-9] : SAFe - FEV 2021 - “Principle #9 – Decentralize decision-making” - https://www.scaledagileframework.com/decentralize-decision-making/
- [Serrat 2017] : Olivier Serrat - MAY 2017 - “The SCAMPER Technique” - https://www.researchgate.net/publication/318018918_The_SCAMPER_Technique
- [Von Oech 2011] : Roger von Oech - 2011 - “A Whack on the Side of the Head” - ISBN 978-0911121-13-7