Writing Effective User Stories: As a User, I Can Express a Business Need in User Story Format To Get the IT Solution I Need (Business Analysis Fundame
Hathaway, Tom; Hathaway, Angela
Idioma: inglés
Editorial: CreateSpace Independent Publishing Platform, 2015
Serie: Libro 7 de 7 - Business Analysis Fundamentals - Simply Put!
- Tapa blanda
- Nuevo
Librería: Read&Dream, SAINT LOUIS, MO, Estados Unidos de AmericaRead&Dream
Vendedor de AbeBooks desde 2 de febrero de 2021
Condición: Nuevo
EUR 6,47
Cantidad disponible: 1 disponibles
Añadir al carritoN° de ref. del artículo 17B6X1028-19043-N-12-25-2024
- Título
- Writing Effective User Stories: As a User, I Can Express a Business Need in User Story Format To Get the IT Solution I Need (Business Analysis Fundame
- Autor
- Hathaway, Tom; Hathaway, Angela
- Editorial
- CreateSpace Independent Publishing Platform
- Año de publicación
- 2015
- Estado
- New
- Encuadernación
- Encuadernación de tapa blanda
- Idioma
- inglés
- ISBN 10
- 1519100493
- ISBN 13
- 9781519100498
- Serie
- Libro 7 de 7: Business Analysis Fundamentals - Simply Put!
User Stories are a great method for expressing stakeholder requirements, whether your projects follow an Agile, Iterative, or a Waterfall methodology. They are the basis for developers to deliver a suitable information technology (IT) app or application. Well-structured user stories express a single action to achieve a specific goal from the perspective of a single role. When writing user stories, stakeholders knowledgeable about the role should focus on the business result that the IT solution will enable while leaving technology decisions up to the developers. Good user stories are relevant to the project, unambiguous, and understandable to knowledge peers. The best user stories also contain crucial non-functional (quality) requirements, which are the best weapon in the war against unsatisfactory performance in IT solutions.
This book presents two common User Story structures to help you ensure that your User Stories have all the required components and that they express the true business need as succinctly as possible. It offers 5 simple rules to ensure that your User Stories are the best that they can be. That, in turn, will reduce the amount of time needed in User Story elaboration and discussion with the development team.
After reading this book you will be able to:
- Translate business needs into well-structured User Stories
- Write User Stories that express the what and avoid the how
- Apply five simple rules for writing effective User Stories
- Clarify assumptions in User Stories by adding context
- Identify and remove ambiguous and subjective terms and phrases in User Stories
- Select the appropriate format for expressing User Stories for Agile Projects
- Write stakeholder requirements in User Story format that solve business problems
Elaborate User Stories to identify measurable non-functional requirements
AUTHOR'S NOTE:
The term “User Story” is a relative new addition to our language and its definition is evolving. In today’s parlance, a complete User Story has three primary components, namely the "Card", the "Conversation", and the "Criteria". Different roles are responsible for creating each component.
The “Card” expresses a business need. A representative of the business community is responsible for expressing the business need. Historically (and for practical reasons) the “Card” is the User Story from the perspective of the business community. Since we wrote this book specifically to address that audience, we use the term “User Story” in that context throughout.
The “Conversation” is an ongoing discussion between a developer responsible for creating software that meets the business need and the domain expert(s) who defined it (e.g., the original author of the “Card”). The developer initiates the “Conversation” with the domain expert(s) to define the “Criteria” and any additional information the developer needs to create the application. There is much to be written about both the “Conversation” and the “Criteria”, but neither component is dealt with in any detail in this publication.
A well-written User Story (“Card”) can drastically reduce the time needed for the “Conversation”. It reduces misinterpretations, misunderstandings, and false starts, thereby paving the way for faster delivery of working software. We chose to limit the content of this publication to the “User Story” as understood by the business community to keep the book focused and address the widest possible audience.
“Sinopsis” puede pertenecer a otra edición de este título.
Reseña del editor
User Stories are a great method for expressing stakeholder requirements, whether your projects follow an Agile, Iterative, or a Waterfall methodology. They are the basis for developers to deliver a suitable information technology (IT) app or application. Well-structured user stories express a single action to achieve a specific goal from the perspective of a single role. When writing user stories, stakeholders knowledgeable about the role should focus on the business result that the IT solution will enable while leaving technology decisions up to the developers. Good user stories are relevant to the project, unambiguous, and understandable to knowledge peers. The best user stories also contain crucial non-functional (quality) requirements, which are the best weapon in the war against unsatisfactory performance in IT solutions.
This book presents two common User Story structures to help you ensure that your User Stories have all the required components and that they express the true business need as succinctly as possible. It offers 5 simple rules to ensure that your User Stories are the best that they can be. That, in turn, will reduce the amount of time needed in User Story elaboration and discussion with the development team.
After reading this book you will be able to:
- Translate business needs into well-structured User Stories
- Write User Stories that express the what and avoid the how
- Apply five simple rules for writing effective User Stories
- Clarify assumptions in User Stories by adding context
- Identify and remove ambiguous and subjective terms and phrases in User Stories
- Select the appropriate format for expressing User Stories for Agile Projects
- Write stakeholder requirements in User Story format that solve business problems
Elaborate User Stories to identify measurable non-functional requirements
AUTHOR'S NOTE:
The term “User Story” is a relative new addition to our language and its definition is evolving. In today’s parlance, a complete User Story has three primary components, namely the "Card", the "Conversation", and the "Criteria". Different roles are responsible for creating each component.
The “Card” expresses a business need. A representative of the business community is responsible for expressing the business need. Historically (and for practical reasons) the “Card” is the User Story from the perspective of the business community. Since we wrote this book specifically to address that audience, we use the term “User Story” in that context throughout.
The “Conversation” is an ongoing discussion between a developer responsible for creating software that meets the business need and the domain expert(s) who defined it (e.g., the original author of the “Card”). The developer initiates the “Conversation” with the domain expert(s) to define the “Criteria” and any additional information the developer needs to create the application. There is much to be written about both the “Conversation” and the “Criteria”, but neither component is dealt with in any detail in this publication.
A well-written User Story (“Card”) can drastically reduce the time needed for the “Conversation”. It reduces misinterpretations, misunderstandings, and false starts, thereby paving the way for faster delivery of working software. We chose to limit the content of this publication to the “User Story” as understood by the business community to keep the book focused and address the widest possible audience.
“Acerca de” puede pertenecer a otra edición de este título.
Read&Dream
SAINT LOUIS, MO, Estados Unidos de America
Vendedor de AbeBooks desde 2 de febrero de 2021
Tarifas de envío en Estados Unidos de America
| Artículo | De 5 a 14 días hábiles | De 3 a 6 días hábiles |
|---|---|---|
| Primer artículo | EUR 0,00 | EUR 7,73 |
Métodos de pago
Especialidad
Fiction, Non-Fiction, Mystery, Textbooks etcInformación empresarial del vendedor
Read and Dream LLC
10847 Midwest Industrial Boulevard
St. Louis, MO Estados Unidos de America 63132
Derecho al desistimiento
Si es un consumidor, puede rescindir el contrato de acuerdo con lo siguiente. Por consumidor se entiende cualquier persona física que actúe con fines ajenos a su actividad comercial, empresarial, oficio o profesión.
Información sobre el derecho de desistimiento
Derecho legal de desistimiento
Tiene derecho a rescindir este contrato en un plazo de 14 días sin dar ningún motivo.
El periodo de desistimiento vencerá a los 14 días desde que usted, o un tercero que no sea el transportista e indicado por usted, adquiera la posesión física del último bien o del último lote o pieza.
Para ejercer el derecho de desistimiento, complete de forma electrónica y envíe una declaración clara en nuestro sitio web, desde "Mis compras" en "Mi cuenta". Le enviaremos sin demora un acuse de recibo de dicho desistimiento a través de un soporte duradero (por ejemplo, por correo electrónico).
Para cumplir con el plazo de desistimiento, basta con que envíe su comunicación relativa al ejercicio del derecho de desistimiento antes de que venza el periodo de desistimiento.
Efectos del desistimiento
Si rescinde este contrato, le reembolsaremos todos los pagos que hayamos recibido de usted, incluidos los gastos de envío (excepto los gastos adicionales que surjan si elige un tipo de envío que no sea el tipo de envío estándar más económico que ofrecemos).
Podemos hacer una deducción del reembolso por la pérdida de valor de cualquier bien suministrado, si la pérdida es el resultado de una manipulación innecesaria por su parte.
Efectuaremos el reembolso sin demoras indebidas y, a más tardar, 14 días después de que se nos informe de su decisión de rescindir este contrato.
Efectuaremos el reembolso utilizando el mismo medio de pago que utilizó para la transacción inicial, a menos que haya acordado expresamente lo contrario; en cualquier caso, no incurrirá en ningún cargo como resultado de dicho reembolso.
Podremos retener el reembolso hasta que hayamos recibido los bienes o hasta que nos haya presentado una prueba de que los ha devuelto, lo que ocurra primero.
Deberá devolver los bienes o entregarlos a Read&Dream, SAINT LOUIS, Missouri, U.S.A., sin demoras indebidas y, en cualquier caso, en un plazo máximo de 14 días a partir del día en que nos comunique su desistimiento del presente contrato. El plazo se cumple si devuelve la mercancía antes de que venza el periodo de 14 días. Tendrá que asumir los gastos directos de devolución de los bienes. Usted solo es responsable de la disminución del valor de los bienes como resultado de una manipulación distinta a la necesaria para establecer la naturaleza, las características y el funcionamiento de los bienes.
Excepciones al derecho de desistimiento
El derecho de desistimiento no se aplica a lo siguiente:
- La entrega de periódicos, diarios o revistas, con la excepción de los contratos de suscripción; y
- El suministro de contenido digital que no se proporcione en un soporte tangible (por ejemplo, en un CD o DVD) si, al hacer el pedido, aceptó que podíamos empezar a entregarlo y que no podría desistir una vez iniciada la entrega.