In software development and product management, a user story is an informal, natural language description of features of a software system. They are written from the perspective of an end user or user of a system, and may be recorded on index cards, Post-it notes, or digitally in project management software. Depending on the project, user stories may be written by different stakeholders like client, user, manager, or development team.
User stories are a type of boundary object. They facilitate sensemaking and communication; and may help software teams document their understanding of the system and its context.
1997: Kent Beck introduces user stories at the Chrysler C3 project in Detroit.
1998: Alistair Cockburn visited the C3 project and coined the phrase "A user story is a promise for a conversation."
1999: Kent Beck published the first edition of the book Extreme Programming Explained, introducing Extreme Programming (XP), and the usage of user stories in the planning game.
2001: Ron Jeffries proposed a "Three Cs" formula for user story creation:
The Card (or often a post-it note) is a tangible physical token to hold the concepts;
The Conversation is between the stakeholders (customers, users, developers, testers, etc.). It is verbal and often supplemented by documentation;
The Confirmation ensures that the objectives of the conversation have been reached.
2001: The XP team at Connextra in London devised the user story format and shared examples with others.
2004: Mike Cohn generalized the principles of user stories beyond the usage of cards in his book User Stories Applied: For Agile Software Development that is now considered the standard reference for the topic according to Martin Fowler. Cohn names Rachel Davies as the inventor of user stories. While Davies was a team member at Connextra she credits the team as a whole with the invention.
2014: After a first article in 2005 and a blog post in 2008, in 2014 Jeff Patton published the user-story mapping technique, which intends to improve with a systematic approach the identification of user stories and to structure the stories to give better visibility to their interdependence.
This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.
How can we turn digital technologies and data into meaningful user experiences? How can we face societal issues raised by digital evolution? This course proposes an immersion in design research, user
Introduction à la technologie du bâti: défis environnementaux et sociétaux, exigences techniques et fonctionnelles du bâtiment dans la durée, équilibre statique des ossatures, matériaux de constructio
Human Factors Engineering theory and research methods will be covered through an interdisciplinary focus on human cognition, behavior and physiology (ergonomics) in the design, development and evaluat
Scrum is an agile project management system commonly used in software development and other industries. Scrum prescribes for teams to break work into goals to be completed within time-boxed iterations, called sprints. Each sprint is no longer than one month and commonly lasts two weeks. The scrum team assesses progress in time-boxed, stand-up meetings of up to 15 minutes, called daily scrums. At the end of the sprint, the team holds two further meetings: one sprint review to demonstrate the work for stakeholders and solicit feedback, and one internal sprint retrospective.
In software and systems engineering, the phrase use case is a polyseme with two senses: A usage scenario for a piece of software; often used in the plural to suggest situations where a piece of software may be useful. A potential scenario in which a system receives an external request (such as user input) and responds to it. This article discusses the latter sense. A use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language (UML) as an actor) and a system to achieve a goal.
In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements. Requirements analysis is critical to the success or failure of a systems or software project.cite book |editor1= Alain Abran |editor2=James W.
The need to produce more sustainable concrete is proving imminent given the rising environmental concerns facing the industry. Blended cement concrete, based on any of the prominent supplementary cementitious materials (SCMs) such as fly ash, ground granul ...
Recent advances in composing Cloud applications have been driven by deployments of inter-networking heterogeneous microservices across multiple Cloud datacenters. System dependability has been of the upmost importance and criticality to both service vendor ...
Despite scientific and technological advances in the field of assistive technology (AT) for people with visual impairment (VI), technological designs are frequently based on a poor understanding of the physical and social context of use, resulting in devic ...