• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Specificationby example
 

Specificationby example

on

  • 789 views

 

Statistics

Views

Total Views
789
Views on SlideShare
776
Embed Views
13

Actions

Likes
0
Downloads
9
Comments
0

2 Embeds 13

http://www.ignite.ee 10
http://ignite.ee 3

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 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

Specificationby example Specificationby example Presentation Transcript

  • Specification by Example Ürgo Ringo
  • Specification why?
  • Key Goals of Examples• shared understanding - now• acceptance testing - soon• documentation - future
  • When to Write Examples• 1 iteration ahead• few days before planning• during planning• inside iteration
  • How to Write Examples• find missing concepts• use domain language• find suitable format• keep only key examples• get feedback
  • Software model vs business modelTest design vssoftware design
  • Effect Mapping• why? - biz goal• who? - stakeholder• how? - stakeholder activity• what? - epic
  • Gojko Adzic - Agile product management using Effect Maps(http://gojko.net/papers/effect_maps.pdf)