Scribd
Upload
288 views1 page

SPIDR Poster

S.P.I.D.R. is an approach to splitting large stories into smaller stories by focusing on specific aspects. It involves pulling out a "spike" or research activity to gain knowledge and potentially split the story. Other techniques include relaxing rules to support in initial stories, splitting based on paths or flows in a story, focusing on different types of data, or splitting across interfaces. The goal is to make large stories more manageable in size and scope.

Uploaded by

super_sumo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
288 views1 page

SPIDR Poster

S.P.I.D.R. is an approach to splitting large stories into smaller stories by focusing on specific aspects. It involves pulling out a "spike" or research activity to gain knowledge and potentially split the story. Other techniques include relaxing rules to support in initial stories, splitting based on paths or flows in a story, focusing on different types of data, or splitting across interfaces. The goal is to make large stories more manageable in size and scope.

Uploaded by

super_sumo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

S.P.I.D.R.

the approach to
splitting stories

SPIKES Make a large story smaller by pulling out a spike,


which is a research activity after which the team
will know more.
• Sometimes just doing a spike makes the
remaining work a manageable size.
• Other times, the new knowledge creating by the
spike makes it easier to see ways to split the story.

RULES PATHS
Sometimes a story is large Consider the paths
because of the business through a story and split
rules, technology each path into its own
standards, or such that story.
must be supported.
• Draw a simple flowchart
• Consider relaxing support of what happens in a
for these rules in an initial story. Each sequence of
story. steps can be a story.
• Add support for additional • Expand one big step of
rules in subsequent the flowchart into a story.
stories.

DATA INTERFACES
Look for ways to split the story based on the Split a story across multiple interfaces if
type of data that must be supported. supporting those interfaces makes the story
take significantly longer to develop.
• Can a first story support valid data and a later
story add support for invalid data? • Split out stories by browser type or version,
or by different hardware.
• How about frequent types of data and less
frequently seen types of data? • Consider building a minimal user interface
first or leave styling out of an interface
initially.

Better User MOUNTAIN GOAT


S O F T W A R E
Stories

You might also like