Features are cross-functional so journey-level planning prefered these days because no point writing down a list of individual features textually that lacks context. Also, it is not possible to do minuscule planning by just writing down features textually in lack of visualization. Visual planning is achieved by journey maps and rapid prototype that is comprehensible and effective documentation method. There are two types of worst-case scenario mapping. One is assumptive and another one is data-driven. It is the need to assume a lot of things to create the MVP (assumptive to-do list). But assumptions have to clash with differences of opinion in round table meeting and have a high chance of failure. So these days it is tried to keep the user journey lean and only deliver the “minimal viable product” by definition. One day design sprint could be used for it.

https://twitter.com/rat9/status/1149203975234715649

After creating the Minimal Viable Prototype, evaluative outcome analysis and evaluative worst-case scenario can be carried out. AB testing and contextual enquiry are some of the ways to collect data. Based on data-driven decision making the speculative opinions can be effectively sideline and further course of action is decided.

Combination of heuristic and kanban is fatal if it is done for a long time without including any evaluative methods to validate the prototype. This is exactly the reason I have written down the post Forget Lean UX, Implement Heuban and quote “Planned failure is a safer way to get better insights.”

Agile is a progressive concept. We are still debating about various aspect of it. Similarly, every framework and methodology is progressive. Heuban is also progressive concept.