Sep 19, 2013 · 5:30 PM
Everyone's pretty clear on using User Stories as the primary Product Backlog Item (PBI) to ensure good scope control through iterations, prioritisation, shaping, splitting, story-mapping, etc. But what about the technical stuff - it still takes time/effort and needs to be prioritised and tested. We'll share our experiences using Technical Stories (derived from Architectural Spikes & Architectural Requirements).
Feel free to bring along some of your own technical challenges to see if using a Technical Story approach can help bring clarity.