IKIWISI | Glossary

Definition:

IKIWISI is an acronym for “I Know It When I See It” which is used in Agile Software development to simplify the process of gathering software requirements. In the olden days, software requirements gathering was easy when compared to the present. Of course, it was not that simple. Software requirements gathering was the first set of business, before even starting with designing, cost estimation, planning and programming. But, certain straight forward criteria required completeness, consistency, traceability and testability for some software specifications, like User-interface: IKIWISI or I Know It When I See It.

The recent developments in IKIWISI, COTS ( Commercial off the Shelf) software and the rapid change in IT development, combined to examine the complicating factors. The many degrees of complexity and freedom in solutions, intangibility in software, seems to demand concrete and cyclic feedback, from people evaluating prototypes or partially built systems to clarify and refine their vision.

Further Reading:

Book: Agile and Iterative Development: A Manager’s Guide by Craig Larman

Glossary

LeSS/ LeSS Huge | Glossary

Definition:

LeSS is a lightweight, Agile framework for scaling Scrum to more than one team. It was born from the experiences of Agile leaders Bas Vodde and Craig Larman, who saw an opportunity to shorten time to market and improve product quality by scaling Scrum beyond the individual team level. LeSS Huge builds on the LeSS framework by optimizing for eight or more teams. As a result, LeSS Huge introduces several new concepts and challenges for managing large-scale backlogs. These are requirement areas, area product backlogs, and area product owners.

LeSS Huge applies to products with “8+” teams. Avoid applying LeSS Huge for smaller product groups as it will result in more overhead and local optimizations. All LeSS rules apply to LeSS Huge, unless otherwise stated. Each Requirement Area acts like the basic LeSS framework.

LeSS HUge framework is ideal for:

Hierarchy view — Ideal for a product owner to see high-level business goals.

Priority view — Ideal for team members to manage their individual backlog items.

Further Reading:

Large Scale Scrum by Bas Vdde and Craig Larman