InfoQ Homepage User Stories Content on InfoQ
-
How Stopping Estimations Helped a Team to Become More Predictable
When making estimations using story points didn’t feel helpful, a team decided to experiment with #NoEstimates. Breaking down stories into smaller tasks gives them insight into their velocity and has made them more predictable. It also helps them to spend less time on process and have more time available for delivering value.
-
The Importance of Learning, Psychological Safety, and Continuous Delivery: Agile on the Beach 2017
At the Agile on the Beach 2017 conference, run in Cornwall, UK, several hundred speakers and attendees gathered to discuss the latest developments within the field of agile and post-agile software development methodologies.
-
Combining User Story Mapping with Domain-Driven Design
User Story Mapping can be a simple yet valuable pattern when adopting Domain-Driven Design (DDD) in projects dealing with complex domains. It can help creating shared domain knowledge among developers and domain experts, Eriksen Costa claims in a blog post discussing advantages combining User Story Mapping with Domain-Driven Design (DDD).
-
Defining and Managing Requirements with Interactive Prototypes
An interview about recent developments in requirement definition and management, how agile teams handle requirements and which problems they face in their daily work, using interactive diagrams and prototypes for conveying requirements, how interactive prototyping can be used with a lean startup approach, and what the future will bring us in requirements definition and management.
-
Impact of Splitting User Stories on the Original Estimates
Product backlog refinement is a practice in which product backlog items are split and often re- estimated. This post is based on user story splitting and re-estimations.
-
Measuring the Business Value in Agile Projects
Technique of "value points" to determine the value delivered by any software project.
-
How Agile Can Learn from Behavioral Economics
People often don’t decide and act rationally, according to studies from the area of behavioral economics. Pierre Hervouet describes how our brain takes decisions, talks about experiments on using personas and the IKEA effect and explains what we can learn from these experiments for agile software development.
-
Using a Definition of Ready
Many teams use the Definition of Done to check if a user story is finished and the product is ready to be delivered. But what about the user stories that a team receives from their product owner? Teams can check the quality of the user stories using a Definition of Ready.
-
Agile Estimation for Release Planning
Estimations are used by agile teams and product owners for prioritizing work and to plan releases of products. They can be done on different levels and in various ways.
-
Upcoming Book by Gojko Adzic on Improving User Stories
Would better user stories improve software delivery? Gojko Adzic thinks applying small changes to the way teams manage their user stories can have a huge impact on the actual outcomes of their software delivery. He announced that he wants to write a book about improving user stories if at least 5000 people show that they are interested by pre-registering themselves in January.
-
How Individuals Can Adopt an Agile Way of Working
Organization mostly do an agile transformation for a whole team, project, or organizational unit, given that agile is a team driven approach. But there are also professionals who start using agile practices individually, or who are working agile as a one person team. How can individuals adopt agile, and what kind of benefits can it give them?
-
Product Backlogs with Process Maps or Story Maps
When you have a large backlog with many user stories, structuring a product backlog with story maps or process maps can help to keep an overview and see the bigger picture.
-
Should You Create User Stories for Technical Debt?
Agile teams sometimes struggle with the planning of pure technical tasks that have no direct value for the user of a system, but have to be done to deliver working software. Should you create user stories to handle such technical tasks and technical debt, or not?
-
New Scrum Kickoff Planner Aims To Help Agile Teams Start on The Right Track
A new "Scrum Kickoff Planner" has just been released by Adam Weisbart with the aim of facilitating team discussion around the important facets of starting a new Agile team or project.
-
Is it Time to Stop Estimating User Stories?
Most new Agile teams transition from hours based estimates to relative estimation using story points, but do we even need estimates at all?