https://concremoubybe.tk/gas-systems-and-torches-manufacturing-jewellery-book.php What Stories Are Not Ch. A Catalog of Story Smells Ch. Using Stories with Scrum Ch. The User Roles Ch. Estimating the Stories Ch. The Release Plan Ch. The Acceptance Tests Pt. Notes Includes bibliographical references pages and index. Related resource Table of contents at http: Other links Inhaltsverzeichnis at http: Set up My libraries How do I set up "My libraries"? These 10 locations in All: Open to the public ; Open to the public ; QA University of Sydney Library.
Open to the public. University of South Australia Library. These 4 locations in New South Wales: This single location in Queensland: This single location in South Australia: These 3 locations in Victoria: This single location in Western Australia: None of your libraries hold this item. Found at these bookshops Searching - please wait We were unable to find this edition in any bookshop we are able to search. These online bookshops told us they have this item: Tags What are tags? Public Private login e. Add a tag Cancel User story. Lists What are lists?
Login to add to list.
Be the first to add this to a list. I recently learned a fundamental dichotomy in expressing oneself: The exoteric writer says exactly what she means, minimises ambiguity and tries to do everything with explicit reasoning, for the largest audience they can, with imagery and irony only as decoration. The esoteric writer — distinct from, but often coextensive with the woo-woo mystical metaphysics fans also called esoteric — does the converse.
Most ancient writers wrote esoterica I recently learned a fundamental dichotomy in expressing oneself: Most ancient writers wrote esoterically, which is one reason that undergrads and other fools, like me, think that ancient writers are vague and low on content. Up to now, I have been confusing the rhetorical stance - see Heidegger, Deleuze, Derrida, Caputo - with the magickal crap.
The exoteric intention strikes me as firstly just good manners and important for intellectual honesty accountability, critical clarity. But one thing I dislike about studying computer science is that all the materials are utterly exoteric. I crave art and irreverence in formal contexts, and those are always at least somewhat esoteric.
I was very impressed with how this subject was treated. Very clear, plenty of background explication, just the kind of clear approach that I wish I was better at. Cohn did a good job. However, some subjects are no longer relevant in modern agile dev, such as esti Fantastic! However, some subjects are no longer relevant in modern agile dev, such as estimating using story points.
Almost all non-functional requirements can and should be expressed as Stories; Mr. Cohn glosses over this with a silly example. If a requirement exists - functional or otherwise - it must deliver value to a customer, which means it can be expressed as a Story. Overall, the book does what the cover suggests and it does it well. I might even buy them each a copy Jun 15, Ben Clohesy rated it liked it.
Overall, it's not too bad - I'm on the 3.
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, Overall, it's not too bad - I'm on the 3. 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. Aug 27, Bart Decaigny rated it it was ok Shelves: Two stars might not seem much 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. Good for somebody just starting with some agile concepts, but too simp Two stars might not seem much 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.
I believe as I am reading this in , there are some inherent biases I have about how to write a user story. All in all, a good read indeed, for those who are just starting with user stories, this book will definitely help. I liked the part where Mike has explained the core of story-pointing. When estimating I believe as I am reading this in , there are some inherent biases I have about how to write a user story. When estimating the stories, I am going to use those tips for sure!
Aug 30, Daniel Irvine rated it really liked it. Without that, tracking velocity and finding a sustainable pace becomes so much harder. Interestingly, it also includes a section on XP rather than scrum, which is a real bonus. Feb 20, Dalan Mendonca rated it really liked it. Great way to wrap your head around the topic. Has a good amount of examples to help one understand the concepts and process well. Book feels a bit dated with now laughable lines like "Most software projects will do best with a new release every two to six months. Certain website projects may release even more frequently" but nonetheless most of the content felt useful even in Aug 10, Iryna Lomachynska rated it really liked it.
Great book for those who are new for User Stories. It explains clearly and with many examples the User Stories lifecycle: Most parts are good, coming from the author's own experience and opinion. However, this book refers to oudated, sometimes contradicted concept of the latest ScrumGuide. I expected some budgeting and financial planing for projects and releases but didn't see them in this book. Aug 01, Steven Ricks rated it liked it. This book has largely become unnecessary since it's initial publication.
The contents are still accurate and relevant, but an hour or two on Google and Wikipedia or a couple of days attending agile ceremonies will entirely preclude the need to read this book.
Apr 17, Ana Schiopu rated it liked it. Quite well defined terms, rules, roles, workflows etc. Nov 01, Oleg Prozorov rated it really liked it Shelves: Mar 18, Tiago Palhoto rated it really liked it. GReat book from the master of the user stories. Jun 29, Ankit Agrawal rated it really liked it. Great read, a complete insight into user stories with questions and an example project!!
What else could you ask for Jul 02, Hung Cao rated it it was amazing. Must read for BA doing agile. Dec 04, Amr added it Shelves: Skimmed it quickly to refresh my mind. Here are some quotes: The child's father has filled the bath tub and is helping his child into the water. The young child, probably two or three years old, dips a toe in the water, quickly removes it, and tells her father "make it warmer. After thinking about his child's request for a moment, the father realizes they are miscommunicating and are using the same words to mean different things.
The child's request to "make it warmer" is interpreted by any adult to be the same as "increase the temperature. For example, it is easy to imagine that the drug dealer and a woman with several boyfriends may each want to maintain multiple separate schedules in case the PDA is seen by the police or a boyfriend. The Pope probably has less need for secrecy but may want a larger font size.
One team may decide to define a story point as an ideal day of work. Yet another team may define a story point as a measure of the complexity of the story. While it is possible to archive story cards, many teams simply rip them up. We shifted focus to a shared document and away from a shared understanding.
Nov 18, Gleb Sevruk rated it did not like it Shelves: This is not that bad as original scrum books from Ken Swabner, but still has a little to do with agile. Author is in the same boat with scrumalliance and selling certificates. You should learn history and got to know that Evo Project Management established in Here is the source of agile: Authors claim that is mathematically impossible to fail the project using Evo.
What does Mike Cohn offer? Just write user story and do retrospective? What do you need to become Product Owner? Sit down and listen for "coach" cockroach for 2 days and receive certificate. The supporting arguments are far from reality, the examples are so far from software development and you will wonder: The answer is no. Some scrum founders worked at rational software.
Just download Rational Rose and see with your eyes WHAT you will develop using agile The truth is that best people will not write any books on topic. You will have to learn by yourself.
It is a pity that no one can really tell what is the main idea of Agile. All best practices were in software for 30 years, and now you say that I should forget about use cases, and use user stories instead. Forget about function points analysis and estimate in 3,5,? Can anyone tell what IS user story, what is epic? Epic in this book was a login page to web-site that should take 3 sprints and 6 weeks of work for full team. Do not forget about planing and mandatory inspect-and-improve cycle from CMMI level 5 so stolen by scrum founders and called retrospective.
Is it the way to develop software nowadays? Is it agile mindset? We could say RIP for all software industry when this methodology was cloned from Kaizen and screwed up entire idea. Remember that Kaizen is only related to predictable manufacturing of real-world products and not for virtual products. This goes even worse. Being sold the scrum for IT company, every second the least competent persons becomes either product owner or scrum master.
In this book you will find only buzzwords about them and not the actual responsibilities. It is not at all clear who should do what.
It is pretty short, not a bad thing per se, but it also tries to cover a great range of topics. Book feels a bit dated with now laughable lines like "Most software projects will do best with a new release every two to six months. The University of Sydney. You'll discover practical ways to gather user stories, even when you can't speak with your users. He is a trainer on Scrum and agile software process techniques and helped popularize Planning poker which he provides as a free online planning tool. University of South Australia Library. Nov 18, Gleb Sevruk rated it did not like it Shelves:
Being misinterpreted by top-management, invalid definition will be then communicated to the team, and team will follow invalid practices without understanding principles behind. You can read more in "Agile good hype and ugly", and understand why I was so critical. Mar 02, David Workman rated it really liked it Shelves: This is probably one of the best books I've read for a long time for software design. The method of using user stories as laid out in this book is a great way of obtaining a high level view of the requirements of a system, and the constant communication and feedback with customers that the described development strategy suggests is a good method of moving from the high level stories down towards the nitty gritty details of an implementation.
Possibly the most useful part of the book though is the This is probably one of the best books I've read for a long time for software design.