A good quality user story does NOT have the following characteristic:

Question

BlackTom AI · Accepted Answer

The question asks which characteristic a good quality user story does NOT have. I will evaluate each option in turn to identify which one is inconsistent with good practice for user stories.
Option 1: 'It can be discussed and evolve as required' — This is a hallmark of good user stories in agile contexts. Stories should be conversations starters that can be refined over time as understanding grows, and they should not be rigidly fixed before implementation. This option describes a desirable property, so it is not the characteristic that a good user story would lack.
Option 2: 'It specifies the technologies need to develop the story' — A strong sign that a user story is not well crafted. Good user stories focus on who, what, and why (the user, the outcome, and the value) rather than prescribing specific technologies. Tying a story to particular technologies can reduce flexibility, hinder collaboration, and create unnecessary constraints. This option clearly describes an anti-pattern for a quality user story.
Option 3: 'It is of a size that can be ‘done’ in a sprint' — This aligns with the INVEST criteria for good user stories (specifically 'Small' and 'Estimable'), ensuring the story can be completed within a sprint. A story that cannot be finished in a sprint is typically too large and may indicate a need for splitting; thus, this is a desirable attribute, not a trait of a poor story.
Option 4: 'It can be developed separately from other stories' — The ability to implement a story independently is another positive attribute, supporting modularity and reducing dependencies. While dependencies can exist, being able to deliver a story on its own is aligned with good story design. Therefore, this is not the characteristic the question seeks to identify as undesirable.
In summary, the option that describes prescribing technologies for the story stands out as the incorrect practice for a high-quality user story, since it undermines adaptability and user-focused outcomes. The other options describe favorable characteristics consistent with well-formed user stories.

A good quality user story does NOT have the following characteristic:

View Explanation

Log in for full answers

Similar Questions

The template of a user story is:

Which one of the following user stories is a complete user story with all the required detail?

When a story is too big, it is sometimes referred to as:

Who is the source of Agile user stories?

User story is:

What is a key benefit of using user stories in Agile development?

Which of the following best represents the standard format of a user story?

A good quality user story does NOT have the following characteristic:

More Practical Tools for Students Powered by AI Study Helper

Homework AI Solver

Stylized AI Paper Writer

Plagiarism Checker Assistant

Citation AI Academic Writing Tool

In-Class Translation Assistant

AI Note Generator

AI Quiz Answers

Past Exam Questions from University Test Bank

Smart Practice Assistant

Adaptive Practice

Making Your Study Simpler