Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
NANO INCREMENTAL
DEVELOPMENT
AKA ELEPHANT CARPACCIO
WHAT HAVE WE GOTTEN
OURSELVES INTO?
• Elephant Carpaccio
is an exercise
invented by Alistair
Cockburn to help
people pract...
WHAT’S A STORY
ANYWAY?
• As a <type of user, "Actor">, I want <some
action> so that <some goal/achievement>.
• As Alex, I ...
“INVEST”
• Independent, demo-able,
potentially release-able
• Negotiable
• Valuable (Customer,
knowledge)
• Estimatable
• ...
HOW BIG CAN STORIES
BE?
Months Weeks Days Hours Minutes
WHAT WE WILL DO TODAY
• Build a simple application
• 5 iterations of 10 minutes
each
• Instead of 3-5 slices,
we’re aiming...
WHY SMALLER STORIES?
• Learn faster w less risk
• Better product earlier
• More business options
• Less time “underwater”
...
THE PRODUCT:
DISCOUNT CALCULATOR
Three Inputs:
• Quantity
• Unit price
• 2-letter state code
One Output:
• Total price (di...
SPRINT 0:
CREATE THE BACKLOG
• Demo-able
• Implementable within
sprint time box
• Noticeably different from
other “slices”...
HOW WILL YOU BUILD?
• What is your first
slice?
• Can you slice things
even thinner?
• Risk reduction
• Value = customer
v...
SPRINT 1…
• Write code
• Tests (TDD, red/green, NFT?)
• Pair?
• Shout “slice” whenever you finish
one
• Go!
• Demo / Accep...
SPRINT 2…
• Shout “slice” whenever
you finish one
• Demo / Acceptance
test…
SPRINT 3…
• Shout “slice” whenever
you finish one
• Demo / Acceptance
test…
SPRINT 4…
• Shout “slice” whenever
you finish one
• Demo / Acceptance
test…
SPRINT 5…
• Shout “slice” whenever
you finish one
• Demo / Acceptance
test…
COMMON SPLITTING
TECHNIQUES
• Defer complexity
• Zero, then one, then
many (e.g, states
codes)
• Hard coding values
• Defe...
RETROSPECTIVE
• How far did you get?
• How was your code
quality?
• How many and what kind
of slices?
• What did you learn?
BUT WE CAN’T SHIP
THAT STORY…
• Independent: demo-able, potentially release-able
• A Minimal Viable Product or Minimal Via...
www.andycleff.com
“Type a quote here.”
Prochain SlideShare
Chargement dans…5
×

Scrum Learning Game: Elephant Carpaccio

2 986 vues

Publié le

There are a number of great scrum learning games "out there" and this one was developed by Alistair Cockburn. It is a classic that's great for agile scrum teams. I've taken a few liberties, inspected and adapted, and offer up my own recipe.

Publié dans : Ingénierie
  • Soyez le premier à commenter

Scrum Learning Game: Elephant Carpaccio

  1. 1. NANO INCREMENTAL DEVELOPMENT AKA ELEPHANT CARPACCIO
  2. 2. WHAT HAVE WE GOTTEN OURSELVES INTO? • Elephant Carpaccio is an exercise invented by Alistair Cockburn to help people practice breaking user stories and their related tasks into really thin vertical slices.
  3. 3. WHAT’S A STORY ANYWAY? • As a <type of user, "Actor">, I want <some action> so that <some goal/achievement>. • As Alex, I want to be able to filter my dash dashboard by list so that I can isolate data to a specific list. • As a Developer I can select from configuration options, press a button and have a VM in less than 10 minutes.
  4. 4. “INVEST” • Independent, demo-able, potentially release-able • Negotiable • Valuable (Customer, knowledge) • Estimatable • Sized Right • Testable (Has i/o) User GUI Client Back End
  5. 5. HOW BIG CAN STORIES BE? Months Weeks Days Hours Minutes
  6. 6. WHAT WE WILL DO TODAY • Build a simple application • 5 iterations of 10 minutes each • Instead of 3-5 slices, we’re aiming for 15-20
  7. 7. WHY SMALLER STORIES? • Learn faster w less risk • Better product earlier • More business options • Less time “underwater” • Deliver value more often • Happier stakeholders • Happier users CumulativeValueDelivered Time Small stories Medium stories Big stories
  8. 8. THE PRODUCT: DISCOUNT CALCULATOR Three Inputs: • Quantity • Unit price • 2-letter state code One Output: • Total price (discounted price plus sales tax)
  9. 9. SPRINT 0: CREATE THE BACKLOG • Demo-able • Implementable within sprint time box • Noticeably different from other “slices” • Adds value
  10. 10. HOW WILL YOU BUILD? • What is your first slice? • Can you slice things even thinner? • Risk reduction • Value = customer value + knowledge value • Walking skeleton….
  11. 11. SPRINT 1… • Write code • Tests (TDD, red/green, NFT?) • Pair? • Shout “slice” whenever you finish one • Go! • Demo / Acceptance test…
  12. 12. SPRINT 2… • Shout “slice” whenever you finish one • Demo / Acceptance test…
  13. 13. SPRINT 3… • Shout “slice” whenever you finish one • Demo / Acceptance test…
  14. 14. SPRINT 4… • Shout “slice” whenever you finish one • Demo / Acceptance test…
  15. 15. SPRINT 5… • Shout “slice” whenever you finish one • Demo / Acceptance test…
  16. 16. COMMON SPLITTING TECHNIQUES • Defer complexity • Zero, then one, then many (e.g, states codes) • Hard coding values • Defer validation • Simple interface (GUI last)
  17. 17. RETROSPECTIVE • How far did you get? • How was your code quality? • How many and what kind of slices? • What did you learn?
  18. 18. BUT WE CAN’T SHIP THAT STORY… • Independent: demo-able, potentially release-able • A Minimal Viable Product or Minimal Viable Feature consists of one or more stories that have been put together to provide enough value to warrant it being put into production. • The Product Owner decides when enough value has accrued to meet the “let’s ship it” threshold
  19. 19. www.andycleff.com “Type a quote here.”

×