We respond to an article on user stories that has some good points (user stories are prompts for conversations) and, in our view, misses the mark on others (claiming that tasks are better than user stories for technical work). This leads us to propose "human stories" which may not involve traditional users but do involve humans who are affected by the software we're building in some way (partners, investors, regulators, and more). Finally, we apply these ideas to answer a question from a listener on handling complex technical changes with user stories.
SHOW LINKS:
User stories article: https://www.lullabot.com/articles/not-everything-is-a-user-story
Rant on non-functional requirements: https://soundcloud.com/troubleshootingagile/squirrels-rant
Agile Manifesto episode on face-to-face interaction: https://soundcloud.com/troubleshootingagile/efficiency-effectiveness-through-face-to-face-conversation
---
Our new book, Agile Conversations, is out now! See https://conversationaltransformation.com where you can order your copy and get a free video when you join our mailing list!
We'd love to hear any thoughts, ideas, or feedback you have about the show.
Email us at info@conversationaltransformation.com
Troubleshooting Agile