|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
User Stories Applied: For Agile Software Development
und über 1 Million weitere Bücher verfügbar für Amazon Kindle .
Erfahren Sie mehr
| ||||||||||||||||||
 Gutschein erhalten
Tauschen Sie jetzt User Stories Applied: For Agile Software Development (Addison Wesley Signature Series) gegen einen Amazon-Gutschein in Höhe von EUR 11,35 ein - einlösbar für Tausende von Artikeln bei Amazon.de. Entdecken Sie mehr eintauschbare Bücher im Bücher Trade-In Shop. Bitte beachten Sie die Teilnahmebedingungen.
 Jetzt für Amazon Student anmelden und um 20% erhöhten Eintauschwert sichern. |
Wird oft zusammen gekauft
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
› Besuchen Sie die Seite von Mike Cohn auf Amazon
› Besuchen Sie die Seite von Mike Cohn auf Amazon
Produktbeschreibungen
Kurzbeschreibung
The concept of user stories has its roots as one of the main tenets of Extreme Programming. In simple terms, user stories represent an effective means of gathering requirements from the customer (roughly akin to use cases). This book describes user stories and demonstrates how they can be used to properly plan, manage, and test software development projects. The book highlights both successful and unsuccessful implementations of the concept, and provides sets of questions and exercises that drive home its main points. After absorbing the lessons in this book, readers will be able to introduce user stories in their organizations as an effective means of determining precisely what is required of a software application.
Synopsis
The concept of user stories has its roots as one of the main tenets of Extreme Programming. In simple terms, user stories represent an effective means of gathering requirements from the customer (roughly akin to use cases). This book describes user stories and demonstrates how they can be used to properly plan, manage, and test software development projects. The book highlights both successful and unsuccessful implementations of the concept, and provides sets of questions and exercises that drive home its main points. After absorbing the lessons in this book, readers will be able to introduce user stories in their organizations as an effective means of determining precisely what is required of a software application.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Tags, die Kunden mit diesem Produkt verbinden(Was ist das?)Klicken Sie zum Suchen verwandter Artikel, Diskussionen oder Personen auf ein Tag.
|
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
3 von 3 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch|Von Amazon bestätigter Kauf
Das Buch erklärt wie man Kundenwünsche am besten erfassen kann. Die Denkweise die erklärt wird, steht im Kontrast zu Techniken, welche zu Projektbeginn alles bis ins letzte Detail in Dokumenten festhalten. Stattdessen regt Mike Cohn dazu an, den Kunden aktiv am Projekt zu beteiligen (wie es bei agilen Techniken halt üblich ist) und User-Stories nur kurz zu halten und als Gedankenstütze zu verwenden, damit der Entwickler stets angeregt ist, mit dem Kunden zu kommunizieren.
Begonnen wird mit dem Finden der Stakeholder, was tun wenn man nicht genügend Stakeholder zur Verfügung hat, wie findet man die User Stories, wie detailliert müssen diese sein bzw. wie müssen diese ausschauen, beleuchten von Testaspekten etc. Das Buch finde ich sehr spannend, da Mike Cohn Textpassagen immer mit Fallbeispielen aus seiner Karriere untermauert und auch immer auf mögliche Probleme hinweist. Ebenfalls hervorzuheben sind die kompakten Kapitel. Das Buch ist nicht sonderlich dick ' trotzdem hat man nicht das Gefühl, dass etwas zu kurz gekommen ist ' einfach super.
All in All ' ein Buch das man auf jeden Fall gelesen haben sollte ' egal ob man aus der agilen Ecke kommt oder nicht.
Begonnen wird mit dem Finden der Stakeholder, was tun wenn man nicht genügend Stakeholder zur Verfügung hat, wie findet man die User Stories, wie detailliert müssen diese sein bzw. wie müssen diese ausschauen, beleuchten von Testaspekten etc. Das Buch finde ich sehr spannend, da Mike Cohn Textpassagen immer mit Fallbeispielen aus seiner Karriere untermauert und auch immer auf mögliche Probleme hinweist. Ebenfalls hervorzuheben sind die kompakten Kapitel. Das Buch ist nicht sonderlich dick ' trotzdem hat man nicht das Gefühl, dass etwas zu kurz gekommen ist ' einfach super.
All in All ' ein Buch das man auf jeden Fall gelesen haben sollte ' egal ob man aus der agilen Ecke kommt oder nicht.
2 von 2 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Es handelt sich hierbei würde ich sagen um ein Standardwerk der agilen Softwareentwicklung, das man gelesen haben sollte.
Folgende Fragen werden beantwortet:
- Was ist der Vorteil von Userstories?
- Warum komm ich mit klassischem Requirement Engineering nicht so weit wie mit Userstories?
- Was sind gute Userstories? Wie schreibe ich gute Userstories?
- Wie war das gleich mit Usecases? Ist das was anderes?
Das Buch eignet sich sehr gut, um sich aufzumunitionieren gegen Vertreter der alten Zunft und Wasserfall-Jünger. Zum Zeitpunkt als ich dieses Buch gekauft habe versuchte ich gerade, einen Scrum-artigen Prozess in meiner Firma einzuführen und hatte es mit allerlei Bedenkenträgern zu tun. Jeder Prozess kann torpediert werden bei der Ausführung. Was nützt einem die schöne Theorie, wenn einem der Product Owner trotzdem ein Lastenheft alter Couleur hinkippt? Da helfen nur Argumente, was Userstories besser machen und was an Requirements allein fehlt. Genau hierauf bietet das Buch Antworten.
Es beschreibt darüber hinaus auch Themenbereiche wie das Schätzen von Stories, welche meiner Ansicht nach gar nicht der Kern dieses Buches sein sollten, denn da streift es schon sehr stark Scrum und andere Prozesse. Es ist hier auch nicht so genau und umfassend wie ein gutes Scrum-Buch. Ich empfehle hierfür eher Boris Glogers Scrum-Bibel.
Alles in allem aber ein sehr guter Helfer und es gibt einem alles Wissenswerte, was man sich zum Thema Userstories vorstellen kann. Letzten Endes beschreibt es einen der neuralgischsten Punkte bei der agilen Softwareentwicklung, nämlich das Erstellen von verständlichen, guten Stories, Do's and Don'ts. Deshalb absolut empfehlenswert für jeden, der agile Softwareentwicklung praktisch als Scrummmaster oder ähnliches begleitet oder in einer Firma einführen möchte. Das Buch richtet sich weniger an Entwickler.
Folgende Fragen werden beantwortet:
- Was ist der Vorteil von Userstories?
- Warum komm ich mit klassischem Requirement Engineering nicht so weit wie mit Userstories?
- Was sind gute Userstories? Wie schreibe ich gute Userstories?
- Wie war das gleich mit Usecases? Ist das was anderes?
Das Buch eignet sich sehr gut, um sich aufzumunitionieren gegen Vertreter der alten Zunft und Wasserfall-Jünger. Zum Zeitpunkt als ich dieses Buch gekauft habe versuchte ich gerade, einen Scrum-artigen Prozess in meiner Firma einzuführen und hatte es mit allerlei Bedenkenträgern zu tun. Jeder Prozess kann torpediert werden bei der Ausführung. Was nützt einem die schöne Theorie, wenn einem der Product Owner trotzdem ein Lastenheft alter Couleur hinkippt? Da helfen nur Argumente, was Userstories besser machen und was an Requirements allein fehlt. Genau hierauf bietet das Buch Antworten.
Es beschreibt darüber hinaus auch Themenbereiche wie das Schätzen von Stories, welche meiner Ansicht nach gar nicht der Kern dieses Buches sein sollten, denn da streift es schon sehr stark Scrum und andere Prozesse. Es ist hier auch nicht so genau und umfassend wie ein gutes Scrum-Buch. Ich empfehle hierfür eher Boris Glogers Scrum-Bibel.
Alles in allem aber ein sehr guter Helfer und es gibt einem alles Wissenswerte, was man sich zum Thema Userstories vorstellen kann. Letzten Endes beschreibt es einen der neuralgischsten Punkte bei der agilen Softwareentwicklung, nämlich das Erstellen von verständlichen, guten Stories, Do's and Don'ts. Deshalb absolut empfehlenswert für jeden, der agile Softwareentwicklung praktisch als Scrummmaster oder ähnliches begleitet oder in einer Firma einführen möchte. Das Buch richtet sich weniger an Entwickler.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
56 Rezensionen
55 von 56 Kunden fanden die folgende Rezension hilfreich
The user story bible
25. Juli 2004
Format:Taschenbuch
'User Stories Applied' was a book that long stood on my Amazon wish list with a 'must have' rating. I'm not disappointed. I loved the book. Now let me explain why.
First of all, running the planning aspect of an XP project, for example, well is essential for reaping the benefits of agile software development. Yet, relatively little has been written to guide practitioners in doing that. I, for example, have made all the mistakes Cohn enumerates in the chapters for guiding the user towards writing *good* user stories (usually more than once). These sorts of things make you realize you shouldn't put the book on the shelf to gather dust! The author doesn't cover just writing good user stories, but the whole spectrum from putting together the customer team to estimating stories to discussing the stories to writing acceptance tests for the stories.
Second, it's a pleasure to read. The structure makes sense, each chapter is followed by a useful summary, and there's a set of questions -- along with answers -- to make sure you understood what the chapter talked about. Usually these kinds of Q&A sections simply force me to skip them over. The questions in this book did not. I read each and every one of them and I think there was only one set of questions that I did 'pass' with the first try, usually having forgotten some rather important aspects to consider (concrete evidence of their usefulness to me). To finish, the last part of the book, an example project, nicely ties together all the threads.
As usual, there were some things I experienced not so well. I believe the chapter on applying user stories with Scrum could've been left out without breaking the plot. Also, I think a typical user wouldn't have been bothered about dropping the appendix introducing Extreme Programming.
In summary, this is the book to get if you're involved with user stories. I had to pause reading every few pages to scribble down some specific tips. I'm confident that you will too.
First of all, running the planning aspect of an XP project, for example, well is essential for reaping the benefits of agile software development. Yet, relatively little has been written to guide practitioners in doing that. I, for example, have made all the mistakes Cohn enumerates in the chapters for guiding the user towards writing *good* user stories (usually more than once). These sorts of things make you realize you shouldn't put the book on the shelf to gather dust! The author doesn't cover just writing good user stories, but the whole spectrum from putting together the customer team to estimating stories to discussing the stories to writing acceptance tests for the stories.
Second, it's a pleasure to read. The structure makes sense, each chapter is followed by a useful summary, and there's a set of questions -- along with answers -- to make sure you understood what the chapter talked about. Usually these kinds of Q&A sections simply force me to skip them over. The questions in this book did not. I read each and every one of them and I think there was only one set of questions that I did 'pass' with the first try, usually having forgotten some rather important aspects to consider (concrete evidence of their usefulness to me). To finish, the last part of the book, an example project, nicely ties together all the threads.
As usual, there were some things I experienced not so well. I believe the chapter on applying user stories with Scrum could've been left out without breaking the plot. Also, I think a typical user wouldn't have been bothered about dropping the appendix introducing Extreme Programming.
In summary, this is the book to get if you're involved with user stories. I had to pause reading every few pages to scribble down some specific tips. I'm confident that you will too.
24 von 26 Kunden fanden die folgende Rezension hilfreich
Finally! Practical advice on writing user stories, and more
14. März 2004
Format:Taschenbuch|Von Amazon bestätigter Kauf
This excellent book is a must-have for anyone on an agile team - developers, testers, business experts, analysts - and for anyone who struggles with requirements, planning, or estimating on any software project.
User Stories Applied is easy to read and digest. As the title suggests, its techniques are easy to apply and deliver huge value. Each chapter summarizes developer and customer responsibilities, and has questions whose answers are provided in an appendix. The book is full of real-life, concrete examples, allowing you to learn from the successes and failures of others.
This book will give you many tools to help your projects succeed. Just a few of the most valuable topics:
When are user stories too big, too small, too detailed, too general, too open ended, when are they not user stories, and how to correct all these.
Why use user stories.
How to handle requirements for infrastructure, performance, qualitative aspects, UI.
How to ask questions to elicit requirements.
How to cope when you don't have `on-site customers'.
Practical ways to estimate stories.
Monitoring velocity and progress.
When to keep and when to discard artifacts.
Mike explores the differences between stories and other techniques for delivering requirements: IEEE 380, use cases, scenarios. He points out many positive side effects of user stories, such as encouraging participatory design and tacit knowledge accumulation.
I particularly like that the book emphasizes the team's responsibility to successfully complete each iteration. I enjoy Mike's illuminating bits of wisdom, such as the "everything takes 4 hours" example. I love the comprehensive example in Part IV. No matter what your level of experience, you'll put the ideas in this book to immediate and productive use.
10 von 10 Kunden fanden die folgende Rezension hilfreich
For XP enthusiasts
4. November 2005
Format:Taschenbuch|Von Amazon bestätigter Kauf
Writing user stories is one of the twelve practices of the XP software development methodology. User stories summarily describe features of the software that must be developed, from the point of view of the user. This means that no implementation detail is present on stories.
As with all the XP practices, the emphasis is on traveling light, producing only those artifacts that are absolutely necessary. Thus, user stories contain a brief description of the feature as a reminder, to the developers and to the customer, that sometime in the future they will need to meet and flesh out the details. This is in contrast to techniques like use cases, which might seem similar but are much more formal and rich.
User stories also play a fundamental role in the planning game, one of the other XP practices. During the planning game, the development team and the customer together discuss the stories, the developers estimate the time necessary to implement each story, in terms of story points and the customer prioritizes them. During the next iteration, developers will implement those stories that the customer deemed more urgent, up to a number whose total sum of points does not exceed the estimated team velocity.
All of this is explained in a couple of the XP series books, namely Extreme Programming Explained: Embrace Change and Planning Extreme Programming You'd better have already read at least the former of those before picking up Mike Cohn's book.
User Stories Applied does a good job explaining in detail what user stories are, what goes into them -and what doesn't -, how they should be estimated and what to do with them after the stories have been implemented.
There's a lot of good sense advice in this book, which might induce someone to think that user stories and all other XP practices are just a bunch of generic suggestions that you might apply or not, as you wish. That's certainly not true, as XP is a methodology whose effectiveness lies in the combined action of all the practices when they are taken to the limit. This takes determination and discipline and, in my experience, it's just too easy to fall into the habit of following only some of them, say when you're not under deadline pressure, and still pretend that you're an XP shop.
I would have liked more real-life stories in this book, in order to spice it up a little. As it is, everything that is there sounds highly reasonable (at least to me) but it wouldn't convince anyone who is skeptic of XP's supposed benefits. The example at the end of the book sounds contrived and hollow.
On the other hand, if you have been already convinced by Kent Beck's white book and want to start adopting XP, I can heartily recommend Mike Cohn's book.
As with all the XP practices, the emphasis is on traveling light, producing only those artifacts that are absolutely necessary. Thus, user stories contain a brief description of the feature as a reminder, to the developers and to the customer, that sometime in the future they will need to meet and flesh out the details. This is in contrast to techniques like use cases, which might seem similar but are much more formal and rich.
User stories also play a fundamental role in the planning game, one of the other XP practices. During the planning game, the development team and the customer together discuss the stories, the developers estimate the time necessary to implement each story, in terms of story points and the customer prioritizes them. During the next iteration, developers will implement those stories that the customer deemed more urgent, up to a number whose total sum of points does not exceed the estimated team velocity.
All of this is explained in a couple of the XP series books, namely Extreme Programming Explained: Embrace Change and Planning Extreme Programming You'd better have already read at least the former of those before picking up Mike Cohn's book.
User Stories Applied does a good job explaining in detail what user stories are, what goes into them -and what doesn't -, how they should be estimated and what to do with them after the stories have been implemented.
There's a lot of good sense advice in this book, which might induce someone to think that user stories and all other XP practices are just a bunch of generic suggestions that you might apply or not, as you wish. That's certainly not true, as XP is a methodology whose effectiveness lies in the combined action of all the practices when they are taken to the limit. This takes determination and discipline and, in my experience, it's just too easy to fall into the habit of following only some of them, say when you're not under deadline pressure, and still pretend that you're an XP shop.
I would have liked more real-life stories in this book, in order to spice it up a little. As it is, everything that is there sounds highly reasonable (at least to me) but it wouldn't convince anyone who is skeptic of XP's supposed benefits. The example at the end of the book sounds contrived and hollow.
On the other hand, if you have been already convinced by Kent Beck's white book and want to start adopting XP, I can heartily recommend Mike Cohn's book.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
