Search the World's Largest Database of Information Science & Technology Terms & Definitions
InfInfoScipedia LogoScipedia
A Free Service of IGI Global Publishing House
Below please find a list of definitions for the term that
you selected from multiple scholarly research resources.

What is User Story

Encyclopedia of Information Science and Technology, Fourth Edition
A high-level requirement statement that contains minimally sufficient information to produce a reasonable estimate of the effort to implement it.
Published in Chapter:
Developing a Glossary for Software Projects
Tamer Abdou (Suez Canal University, Egypt), Pankaj Kamthan (Concordia University, Canada), and Nazlie Shahmir (WestJet Airlines Limited, Canada)
Copyright: © 2018 |Pages: 12
DOI: 10.4018/978-1-5225-2255-3.ch644
Abstract
The success of a software project depends intrinsically on effective communication among stakeholders. The purpose of a glossary is to ensure that the knowledge of the domain underlying a software project be communicated properly to all the stakeholders of that project. This chapter provides the context, the rationale, and the means for developing a glossary for software projects. In doing so, it proposes a process for developing a glossary. This process is independent of any particular application domain, software development methodology, and information technology. The approaches for representing and presenting a glossary, for the consumption of humans as well as that of machines, are discussed.
Full Text Chapter Download: US $37.50 Add to Cart
More Results
A Tale of Two Agile Requirements Engineering Practices
A high-level requirement statement that contains minimally sufficient information to produce a reasonable estimate of the effort to implement it.
Full Text Chapter Download: US $37.50 Add to Cart
Using Wiki for Agile Software Development
A high-level requirement statement that contains minimally sufficient information to produce a reasonable estimate of the effort to implement it.
Full Text Chapter Download: US $37.50 Add to Cart
Product Backlog and Requirements Engineering for Enterprise Application Development
A short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.
Full Text Chapter Download: US $37.50 Add to Cart
Requirements on Dimensions for a Maturity Model for Smart Grids Based on Two Case Studies: Disciplined vs. Agile Approach
From the user's perspective, the product owner formulates the requirements for a software product or a business solution (processes/methods) in user stories ( Schwaber & Sutherland, 2017 ).
Full Text Chapter Download: US $37.50 Add to Cart
A Comparison of Use Cases and User Stories
A high-level requirement statement that contains minimally sufficient information to produce a reasonable estimate of the effort to implement it.
Full Text Chapter Download: US $37.50 Add to Cart
Using Wiki for Managing Knowledge in Agile Software Development
A high-level requirement statement that contains minimally sufficient information to produce a reasonable estimate of the effort to implement it.
Full Text Chapter Download: US $37.50 Add to Cart
Disciplined or Agile?: Two Approaches for Handling Requirement Change Management
User Story is a concise description of a user's need for the product (that is, a “requirement”) from that user's point of view. User Story seeks to describe this need in a simple and light way.
Full Text Chapter Download: US $37.50 Add to Cart
eContent Pro Discount Banner
InfoSci OnDemandECP Editorial ServicesAGOSR