65d2e46788
Add consistent front-matter schema to CLAUDE.md and GROK.md, including title, date, topics, related articles, and abstracts. Apply similar front-matter to draft files (agile-stories.md, uses-and-abuses.md) and published articles (Agile-Or-Whatever-You-Call-It.md, Testers-As-Explorers.md, etc.) to improve indexing, searchability, and cross-referencing. Ensure topics use a controlled vocabulary and abstracts capture core theses.
1.5 KiB
1.5 KiB
| title | date | topics | related | abstract | ||||
|---|---|---|---|---|---|---|---|---|
| Agile Stories | 2025-04-07 |
|
|
An exploration of user stories through the lens of actors, objects, and purposes, and what this reveals about the true nature of Agile practices. |
Agile Stories
What Is The Story?
Three Questions:
- Who is asking for something?
- What are they asking for?
- WHY do they want it?
This covers off the three aspects of business value:
- To whom are we providing value?
- With what are we providing value?
- What value is being provided?
There are three categories of thought this can be grouped into:
- Actors
- Objects
- Purposes
An actor is anyone we interact with, who intends to derive something of value from us.
An object is any “thing” we intend to use, to provide value
A purpose is the value we intend to provide.
All good stories must answer all three questions.
How Big Is The Story?
This is where estimating comes in. Estimation involves:
- Effort - The degree of difficulty or amount of work expected during the development process. This should include testing.
- Complexity - The number of elements, their relationships, their interdependencies, and the amount of research needed, to complete the story.
- Risk - The scope of the “unknowns” of the story; external dependencies; potential problem areas; amount of experience with the technologies involved; etc.
These factors constitute a relative measure of story size, not an objective one (like height, weight, or volume).