Specificationby example
•Download as PPT, PDF•
0 likes•562 views
This document discusses specification by example, a technique where examples are used to specify requirements, enable acceptance testing, and serve as documentation. It recommends writing examples one iteration ahead, a few days before planning, during planning, and inside iterations. It provides tips for how to write good examples, such as finding missing concepts, using domain language, selecting a suitable format, including only key examples, and getting feedback. It also distinguishes between software and business models and test design versus software design. Additionally, it outlines an effect mapping technique to link business goals to stakeholder activities and epics.
Specificationby example
- 1. Specification by Example Ãœrgo Ringo
- 2. Specification why?
- 3. Key Goals of Examples • shared understanding - now • acceptance testing - soon • documentation - future
- 4. When to Write Examples • 1 iteration ahead • few days before planning • during planning • inside iteration
- 5. How to Write Examples • find missing concepts • use domain language • find suitable format • keep only key examples • get feedback
- 6. Software model vs business model Test design vs software design
- 7. Effect Mapping • why? - biz goal • who? - stakeholder • how? - stakeholder activity • what? - epic
- 8. Gojko Adzic - Agile product management using Effect Maps (http://gojko.net/papers/effect_maps.pdf)
Editor's Notes
- to understand complexity, to avoid rework
- ask customer to tell you how he would check whether given functionality works or ask what he would do if the system didn't work assert your assumptions (by asking feedback questions if in workshop)
- prioritize on stakeholder activity level epics are "shopping list" - start from here and build towards the goal