View 4 excerpts, cites background. View 1 excerpt, cites background. An approach based on design practices to specify requirements in agile projects.
The growing interest for integrating agile methodologies and usability has brought various challenges to practitioners. This research focuses on a specific part of these challenges that is related to … Expand.
View 7 excerpts, cites background and methods. Print this content. 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. Features Learn to build robust software that more closely meets the customer's needs through applying the concept of user stories.
Table of Contents Foreword. About the Author s Mike Cohn is the founder of Mountain Goat Software, a process and project management consultancy and training firm. Backcover Copy Agile requirements: discovering what your users really want. With this book, you will learn to: Flexible, quick and practical requirements that work Save time and develop better software that meets users' needs Gathering user stories -- even when you can't talk to users How user stories work, and how they differ from use cases, scenarios, and traditional requirements Leveraging user stories as part of planning, scheduling, estimating, and testing Ideal for Extreme Programming, Scrum, or any other agile methodology Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software.
User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other "proxies" Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum PearsonChoices Give your students choices!
Mike Cohn's breakthrough book gives us not only the philosophy, but also the guidelines and a proven set of tools that we need to succeed in planning, estimating, and scheduling projects with a high uncertainty factor. At the same time, the author never loses sight of the need to deliver business value to the customer each step of the way.
The concept of user stories has its roots as one of the main tenets of Extreme Programming. The Classroom Performance System in-class quizzing and classroom management system is also available. The content comes alive for students as they are encouraged to apply key concepts.
This supplement contains detailed solutions and explanations for even-numbered problems in the main text. Also other file formats may be included in this archive: pdf, epub, fb2, mobi.
Sections are listed along the left side of the window show me. Each section can have multiple pages inside of it. To organize or add sections, click the "Organize Sections" link show me.
You can rename any section by clicking on the icon that appears, rearrange sections by clicking and dragging them, or delete sections by clicking the icon. Sections have multiple pages. You can see the list of pages for the current section on the right side of the window show me. Now you're editing! About Features Learn to build robust software that more closely meets the customer's needs through applying the concept of user stories.
User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other "proxies" Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum What Is a User Story?
Where Are the Details? What Will the Process Be Like? Planning Releases and Iterations. What Are Acceptance Tests? Why Change? Valuable to Purchasers or Users. Developer Responsibilities. Customer Responsibilities. User Roles. Role Modeling Steps.
Two Additional Techniques. Elicitation and Capture Should Be Illicit. User Interviews. Story-Writing Workshops. The Users' Manager. A Development Manager. Domain Experts. The Marketing Group. Former Users. Trainers and Technical Support. Business or Systems Analysts. More Information.
0コメント