How software development    teams use user stories: adistributed cognition perspective
Studying user stories in a real-life               context• Mature agile implementation• Interviews to build a user story ...
The traditional idea of the mind is      “I think, therefore I am”                  A brain in a vat                      ...
Distributed CognitionMind inescapably part of the worldPeople share and create new thinking with• Other People• Artefacts•...
Airspeed indicator with a speed bugImage thanks to Wikipedia and Creative Commons
What this means for user stories?• Locate what really works and what doesn’t  – Turn up what is good  – Remove what isn’t•...
Mediating ArtefactMediating artefacts include any artefacts thatare brought into coordination in the completionof the task...
The Tangible Nature of the Artefact
The Story WallAn external representation of the progress to agoal.
Representational-Goal Parity
Information Hub      PARKING LOT                    Information                    Buffer
Blah, blah, blah, etc – the referencesEd Hutchins• Cognition in the Wild• How a cockpit remembers its speeds• His distribu...
Any Questions?
Upcoming SlideShare
Loading in …5
×

Looking at User Stories through a Distributed Cognition lens

441 views
326 views

Published on

Presenter: Karen Chance.

What is it that makes user stories successful? If a team places the user stories in a list, there is little to distinguish user stories from conventional requirements. However, it is the use of user stories that makes the difference.

This talk explores recent research into one Agile implementation in Auckland. I’ll identify ways by which a software development team “distributes” work through members of the team, artefacts, and the physical environment to ease the task of software development.

Intended Audience: Managers, agile teams, BAs

Level of expertise: Beginner: for organisations kicking off with Agile, or for colleagues newly exposed to Agile but also, for those using user stories at the moment and not getting all they could from them.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
441
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Looking at User Stories through a Distributed Cognition lens

  1. 1. How software development teams use user stories: adistributed cognition perspective
  2. 2. Studying user stories in a real-life context• Mature agile implementation• Interviews to build a user story process• Distributed Cognition for Teams Framework (DiCot)
  3. 3. The traditional idea of the mind is “I think, therefore I am” A brain in a vat The Computer as a Model of the Brain
  4. 4. Distributed CognitionMind inescapably part of the worldPeople share and create new thinking with• Other People• Artefacts• Physical Environment
  5. 5. Airspeed indicator with a speed bugImage thanks to Wikipedia and Creative Commons
  6. 6. What this means for user stories?• Locate what really works and what doesn’t – Turn up what is good – Remove what isn’t• Relate it empirically sound DiCot framework
  7. 7. Mediating ArtefactMediating artefacts include any artefacts thatare brought into coordination in the completionof the task (Furniss, 2004).
  8. 8. The Tangible Nature of the Artefact
  9. 9. The Story WallAn external representation of the progress to agoal.
  10. 10. Representational-Goal Parity
  11. 11. Information Hub PARKING LOT Information Buffer
  12. 12. Blah, blah, blah, etc – the referencesEd Hutchins• Cognition in the Wild• How a cockpit remembers its speeds• His distributed cognition course is online http://hci.ucsd.edu/102a/schedule.htmlDonald Norman• Things that Make Us Smart• The Design of Everyday ThingsDominic Furniss• Codifying Distributed Cognition
  13. 13. Any Questions?

×