Grundbog og lærebog omkring hvordan man skriver og arbejder med user stories.
Godt og padagoisk skrevet, men ikke meget nyt

great book

Досить непогана книга і як напрочуд досі актуальна. В свій час допомогла розібратися з написанням User stories та зрозуміти як надалі писати тестову документацію (тест кейси, чек лісти), складати тест плани та планувати роботу в подальшому.

Can't seem to get through this one. Tried to start a couple of times but somehow this one is not compelling. Back to the shelf

I read this book in a few days after being given a new assignment to go onto a high profile customer site for 3 weeks and define the requirements for a new computer system in a complex area of financial process. These requirements would be brought back into an agile development team, so I wanted to provide the best possible quality of requirements for the team.
The book did the job and answered a lot of questions for me. The requirements were done on time and in a format the worked well with the development time and was easy to manage.

Two stars might not seem much... but I honnestly don't think it should be much more. It's worth reading for having a baseline of the concept of user stories, but a whole book about a (simple) concept is quite a lot, especially as the example used throughout the book is pretty shallow. In practice, half of what is gone over quickly (e.g. non-functional requirements, refactoring): that simply doesn't work out with user stories. Good for somebody just starting with some agile concepts, but too simplistic to even consider using stand-alone. Fortunately (albeit too slowly) methodologies used have started taking the shortcomings into account and use a fuller framework.

This short book promises to explain what User Stories are, what they aren't, how to create and utilize them within an Agile/XP approach, and finally how to bring everything together in a short, yet relatively realistic case study. It delivers exactly what it promises and the exercises at the end of the chapters, although not always very well crafted, help the reader to capture the essence of each chapter, as well as focus on the pitfalls. It is not repetitive and does not try to be everything for every type of software developer, and that I consider another positive point.

No matter what methodology you use, software development is a challenging task, and even if your favorite method is Agile or a variation of it, you'll need hard earned experience and probably more than just one book, but if I had to recommend only one introductory book to someone who wants to get the essence of creating User Stories to capture most of the aspects of end user software, then this book would be it

awesome book. some earlier chapters felt a little overly simplified. but that is probably somewhat because i am already familiar with the basic concept. some of the later chapters we much more valuable to me. the best intro to scrum ive read yet.

after reading (most) of this book i am much more confident about trying to introduce user stories at work.

Excellent book as overview of working with requirements from User Stories prospective. I highly recommend everyone in software development to read this book, for developers as well as business analysts

É impressionante a quantidade de detalhes aplicada a apenas um tema. Mas bastante instrutivo.

Overall, it's not too bad - I'm on the 3.5 rating really (4 stars for me is "yes I'll read again). I'll probably refer back to it every now and then, but am more likely to go to Mike's website if I want more specific information.

I came at this as a BA with a fair bit of experience and was looking a quick light and easily digestible overview of stories - which this is. However, as another reviewer has noted, this book is definitely coming at the topic from the perspective of a software engineer, not a BA or requirements person. So if you're a BA and reading this book, check your chip on your shoulder at the door, then just plow through it.

The book is pretty well written and very easy to read - there feels to be a little bit of padding but that's fine. Feels a little out of date in some ways, but would recommend as a primer.

- B.

After reading the book you are definitely left with a more clear sense on how to direct development projects through the use of user stories. It's a very UX and business value focused approach.