Question

Which of the following things is wrong with this business user story?

As a user, I need a system should be built using the Meteor platform for making web and mobile apps in JavaScript.

Difficult to estimate

Describes implementation technologies

Uses technical jargon that the customer may not understand

All of the above

Answer 1

The business user story is faulty because it includes technical jargon, specifies implementation technologies, and is difficult to estimate, all of which can contribute to poor design decisions that fail to meet users' needs.

Step-by-step explanation:

The user story you've mentioned is problematic for several reasons. Part of creating an effective user story in business and software development is to ensure that it is easily understandable, can be used to gauge the work required, and does not dictate the specific technology to be used unless it's essential for the end user. Let's look at why the user story mentioned is considered faulty:

Difficulty estimating: Good user stories should be clear enough to provide a basis for estimating the effort and time required to implement them.

Describes implementation technologies: User stories should focus on the end user's needs rather than specifying technologies unless it is a core requirement for the user.

Uses technical jargon: User stories should be written in simple language that is accessible to all stakeholders, including non-technical individuals. Using terms like 'Meteor platform' might be confusing to some.

All these factors contribute to the poor design of the user story and could lead to difficulty in development that might not meet the user's actual needs.