|
|
Hi,
First of all, Happy Holidays and I wish you all the best in the new year. As a kind of a holiday present, I'm offering you a free copy of my next e-book.
I’ve worked with several teams last year that had reasonably good tech practices, but things coming into their work stream were not defined well, not split well, not valuable enough in isolation, and generally not the kind of user stories that give people the
big benefits that they expect. Applying a few small changes to the way they manage user stories made a huge impact on the actual outcomes of their software delivery. This got me thinking that perhaps this is a wider problem and other teams could benefit from
the ideas we applied. So I’m thinking about writing a book about that. I want to write about how to define better stories, how to spot and fix common issues, how to split them so that they are valuable but small, how to deal with difficult stuff like cross-cutting
concerns, long-term effects and “non-functional” requirements, and above all, how to get the promise of agile and iterative delivery by ensuring that the right stuff gets discussed and agreed between delivery team members and stakeholders.
Before I jump into a few months of writing, I’d like to know if I’m right or wrong thinking that other people out there have the same issues. This is where you come in! So here’s the deal: if the situation I’ve described sounds familiar, and improving user
stories would potentially make a big impact on what you deliver, pre-register for the book and if 5K people do that in January I’ll write it, and you get a free (ebook) copy.
Here's how you can make me write it: http://bit.ly/Jw7OWh
Gojko
|
|
