Scribd
Upload
27 views3 pages

SPIDR Techniques

SPIDR Technique for story slicing

Uploaded by

unknown139
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
27 views3 pages

SPIDR Techniques

SPIDR Technique for story slicing

Uploaded by

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

The SPIDR technique is a useful approach in Agile for splitting large user

stories into smaller, more manageable ones. The acronym SPIDR stands
for Spike, Path, Interface, Data, Rules. Each of these elements
represents a different aspect of the story that can be used to break it
down into smaller, more actionable stories.

Breakdown of the SPIDR Technique:

1. S – Spike

o Definition: A spike is a research task or experiment used to


explore a complex problem or uncertainty.

o Usage: When you encounter a user story with unknowns or


technical challenges, create a spike to investigate and gather
information. This often leads to clarity and helps in defining
more specific, smaller stories.

o Example: If your LMS has a requirement to integrate with an


unknown third-party tool, create a spike to research the tool’s
API, capabilities, and compatibility with your system.

2. P – Path

o Definition: Path refers to breaking down a story based on


different user paths or workflows.

o Usage: Identify different ways a user might interact with a


system and split stories according to these pathways. Each
path can then be developed and tested independently.

o Example: In an LMS, if a large story involves users enrolling


in a course, the story can be split into separate paths like
“enrollment through the mobile app” and “enrollment via the
web interface.”

3. I – Interface

o Definition: Interface refers to splitting stories based on


different user interfaces or touchpoints.

o Usage: If a feature will be accessed through multiple


interfaces (e.g., mobile, desktop, API), you can split the story
based on these.

o Example: If the LMS needs a feature for submitting


assignments, you could split the story into “submission via
desktop interface” and “submission via mobile app.”

4. D – Data
o Definition: Data refers to splitting stories based on different
sets or types of data that the feature will handle.

o Usage: If a feature deals with multiple data inputs or types,


split the story accordingly.

o Example: For an LMS feature that tracks user progress, you


could split it into “tracking video lecture progress” and
“tracking quiz completion.”

5. R – Rules

o Definition: Rules refer to the business rules, logic, or


conditions that govern a feature.

o Usage: If a story involves complex business logic, you can


split it by focusing on different rules or sets of rules.

o Example: If an LMS needs a feature for certification issuance,


you could split it into stories like “certification based on course
completion” and “certification with a minimum grade
requirement.”

Example of Using SPIDR to Split a Story in an LMS Context:

Original Large Story:


"As an instructor, I want to set up a course with modules, quizzes, and
certification so that students can learn and get certified upon completion."

Applying SPIDR:

 S – Spike:

o Spike Story: "Research the best practices for setting up


modular courses in the LMS, focusing on user engagement
and content delivery."

 P – Path:

o Split into:

 "Set up a course with modules only."

 "Add quizzes to the course."

 "Integrate a certification process after course


completion."

 I – Interface:

o Split into:
 "Allow course setup via the desktop interface."

 "Enable course setup via the mobile interface."

 D – Data:

o Split into:

 "Set up modules with video content."

 "Set up modules with reading material."

 "Set up modules with interactive quizzes."

 R – Rules:

o Split into:

 "Issue certification based on completion of all modules."

 "Issue certification only if the student passes the final


quiz with a minimum score."

Importance and Implementation:

The SPIDR technique is important because it allows teams to break down


complex stories into smaller, more manageable ones that are easier to
implement, test, and deliver incrementally. This helps in maintaining
momentum, reducing risks, and ensuring that value is delivered to the
end-users continuously.

 Implementing SPIDR: Start by analyzing the large story using the


SPIDR framework. Identify the aspects that can be split based on the
five elements. Then, create smaller stories that can be prioritized
and completed within a single sprint. Regularly revisit and refine
these smaller stories as more information becomes available or as
the project evolves.

Using SPIDR effectively ensures that the development process remains


agile and adaptable, allowing teams to focus on delivering high-quality
features incrementally.

You might also like