• Português
  • 简体中文
  • 繁體中文
  • Deutsch
  • English
  • Español
  • Français
  • 日本語
  • Latviešu
  • Lietuvių
  • Русский
agiletour.org
Home

Submitted Conference Content

Full name

Thomas Cagley
Job
email t [dot] cagley [at] davidconsultinggroup [dot] com
Skypeid thomas.cagley.jr
Phone number 4409338768
Company DCG
City (Country) Avon Lake
Time 1h
Type of Conference Conference < 40 attendees
Level Beginner

Splitting User Stories!

Biography

Mr. Cagley is the Vice President of Consulting for The David Consulting Group. He is an authority in guiding organizations through the process of continuous process improvement. His areas of expertise encompass management experience in a wide variety of methods and metrics: Lean software development, Agile software development, quality integration, quality assurance and the application of the Software Engineering Institute’s Capability Maturity Model® Integration (CMMI) to achieve process improvements. Mr. Cagley is an active member of the International Function Point Users Group and is a Certified Function Point Specialist. He is also the editor of the Software Process and Measurement Podcast - SPaMCAST and blogs at tcagley.wordpress.com. He can be reached at t.cagley@davidconsultinggroup.com

Description

Splitting User Stories! A user story (See User Stories, October 28, 2013) is a brief, simple requirement statement from the users perspective. The classic format of a user story is: “As a , I want to so that .” When initially constructed, a user story can represent a concept that the team can’t wrap their mind around and can’t finish in an individual iteration. Therefore, the user story needs to be broken down into smaller chunks. Stories, when they are accepted into a sprint, must meet the “rule.” The rule is that each story must deliver functionality which is potentially implementable. I strongly suggest that this rule is the only rule that can’t be broken. Breaking this rule tends to create waterfall or architectural splits, which flies in the face of the Agile principles. The guidelines inferred by the INVEST acronym provide a directional framework to create well-formed stories.

Prerequisites

Understanding of what user stories are!

Benefits for the attendees

Attendees will learn why splitting user stories into smaller pieces makes sense and patterns for splitting user stories.

Go to the submission page!

Submitted by ppetit on Mon, 06/13/2011 - 02:02

User login

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
                                                          
  ad88888ba            ,d8      ad88888ba     ad888888b,  
 d8"     "8b         ,d888     d8"     "88   d8"     "88  
 Y8a     a8P       ,d8" 88     8P       88           a8P  
  "Y8aaa8P"      ,d8"   88     Y8,    ,d88        aad8"   
  ,d8"""8b,    ,d8"     88      "PPPPPP"88        ""Y8,   
 d8"     "8b   8888888888888            8P           "8b  
 Y8a     a8P            88     8b,    a8P    Y8,     a88  
  "Y88888P"             88     `"Y8888P'      "Y888888P'
Enter the code depicted in ASCII art style.