LSST Tech Talk: Story mapping, and the tragedy of the flat backlog
or how I learnt to love my annoying, inconsistent, and utterly incoherent users
Eric Saunders, Software Team Lead, Las Cumbres Observatory
Most developers are aware of the existence of agile practices, and the concept of the " user story" - a description of what someone actually wanted, which you can go and build. A typical agile workflow involves creating stories, storing them in a "backlog", and then making them, one by one, iterating over your own personal for loop until done.
Yet anyone who's actually done this for any length of time starts asking uncomfortable questions. Why is it so hard to make good, actionable stories? Why are my stories often too big, too hard, or just not very useful? When am I done? What's the big picture? Are my users happy? Why aren't my users happy? Why haven't we finished anything releasable yet?
These are important questions, since they cut right to the purpose of the work we do every day. If we make the wrong stuff, it doesn't matter how good our programming is.
In this informal talk, I will discuss story mapping, a technique for improving your relationship with your users, identifying what really matters, prioritising your backlog, and building stuff that people might actually use.
Streaming Details will be emailed 15 minutes prior to the talk & posted on the Data Management hipchat