As you walk through the prototype, ask questions that will help you identify
missing stories, such as:
• What will the user most likely want to do next?
• What mistakes could the user make here?
• What could confuse the user at this point?
• What additional information could the user need?

Most readers of
this type of story will mistakenly associate the extra detail with extra precision.

Nagyon hasznos, bár kissé idejétmúlt összefoglaló a "user story"-k használatáról az agilis szoftverfejlesztés területén. (Kéne egy jó magyar fordítás a "user story" kifejezésre, én eddig a "felhasználói követelmény"-t hallottam, de az nem az igazi, sőt, kicsit szembe is megy a kívánt szellemiséggel.) Meglátszik a könyvön, hogy 2004-ben íródott, a Scrummal kapcsolatban például vannak pontatlan állítások benne (példa: 30 napos sprint).

A hangvétel telitalálat, valahol a kézikönyvön innen, a motivációs íráson túl. Kicsit azért száraz. Korábban olvastam tőle az "Agile Estimating and Planning"-et, az sokkal élvezetesebb.

Great book! I only think that some examples about user acceptance testing could make use of specification by example explicitly, although the author talk about this practice along the reading. I strongly recommend this book, especially for business analysts.

This book covers using User Stories to express features that are useful to end-users, instead of focusing on technical implementation and documentation.

It presents reasons why using user stories to drive design and project planning is better than attempting comprehensive upfront design, and techniques on writing effective stories.

It also tackles planning but a better book for that is the author's next book, Agile Estimating and Planning, a great follow up.

I highly recommend this book, especially for teams that want to improve customer focus. I'd also recommend this for customers who have had trouble with outsourcing software development where the end results often aren't what you need.