15 Running with User Story Lite
The goal of this chapter is to introduce the user story practice, including its elements in the Essence language, and to illustrate how TravelEssence adopted and applied the practice. Specifically, the reader will after finishing this chapter be introduced to
- the elements of the user story practice, including relationships between the respective elements, activity flows, and its relationship with the kernel elements (in TravelEssence’s case, only Requirements and Work);
- quality criteria for each user story and the decisions they drive along the practice;
- the elements and structure of a simplified version of the user story practice (called User Story Lite) in a real endeavor, including the obstacles and challenges that might arise; and
- the coverage of kernel solution activity spaces by the User Story Lite practice.
After studying this chapter, you should be able to
- explain the “Who,” “What,” and “Why” of user stories;
- explain the purpose of Card, Conversation, and Confirmation within a user story;
- explain the INVEST criteria;
- explain why we need the “so that” clause in a user story;
- explain the purpose of the User Story Lite practice and the problems it solves;
- explain how TravelEssence adopted and applied User Story Lite and the benefits they achieved, together with the benefits implied by using the User Story Lite practice in an essentialized form; and
- list and explain the alphas, work products, activities, and patterns of User Story Lite.