User Story Quiz

User Story:

As a developer, I want to finalize the database schema for the next release so that we don't have to make changes later.

This is not a good user story primarily because?

• The story is open ended and hard to ESTIMATE the effort.

• The story has no business VALUE and a user who is not really an end user.

• The story is not TESTABLE because it has vague criteria of success.

• No reason as this is a good user story.

User Story:

As an online student, I want the names of participants in a course to be displayed in different colors - RGB = #ff0000 for instructors, #A52AFA for students, and #808000 for TAs - so that I can quickly identify their role.

This is not a good user story primarily because?

• The story has no business VALUE and a user who is not really an end user.

• The story is not SMALL and should be broken into multiple stories.

• The story is not NEGOTIABLE because it specifies exactly how the programmer should implement the solution.

• The story is not TESTABLE because it has vague criteria of success.

User Story: 

As the system, I need to store student account info and their current enrollment in the database so that I can track which students can join a class. 

This is not a good user story primarily because?

• The story has no business VALUE and a user who is not really an end user.

• he story is not NEGOTIABLE because it specifies exactly how the programmer should implement the solution.

• The story is not INDEPENDENT.

• The story is not SMALL and should be broken into multiple stories.

User Story: 

As an online student, I want something that stands out about participants to tell at a glance who is an instructor, student, and TA so that I can quickly identify their role. 

This is not a good user story primarily because?

• The story has no business VALUE and a user who is not really an end user.

• The story is not SMALL and should be broken into multiple stories.

• The story is not NEGOTIABLE because it specifies exactly how the programmer should implement the solution.

• No reason as this is a good user story.

User Story: 

As an instructor, I want to be able to share presentations created in different formats including: PDF, PPTX, KEY, etc; be able to quickly switch to breakout rooms; and have virtual office hours so that I can stay within the platform for all my instruction. 

This is not a good user story primarily because?

• The story has no business VALUE and a user who is not really an end user.

• The story is not SMALL and should be broken into multiple stories.

• The story is not NEGOTIABLE because it specifies exactly how the programmer should implement the solution.

• All the previous reasons and more.

User Story: 

As a student, I want the service to randomly shut down and be offline for 5 to 10 minutes so that I can have time to relax and catch up on Candy Crush.

This is not a good user story primarily because?

• The story is not INDEPENDENT of other stories.

• The story is not SMALL and should be broken into multiple stories.

• The story is not NEGOTIABLE because it specifies exactly how the programmer should implement the solution.

• No reason as this is a good user story.

User Story: 

As a teaching assistant, I want the yet-to-be-implemented breakout room feature to let me pull all the students with missing assignments to a specific breakout room so that I can quickly follow up with struggling students. 

This is not a good user story primarily because?

• The story is not INDEPENDENT of other stories.

• The story is not SMALL and should be broken into multiple stories.

• The story is not NEGOTIABLE because it specifies exactly how the programmer should implement the solution.

• The story has no business VALUE and a user who is not really an end user.

User Story: 

As a teaching assistant, I want a user-friendly interface so that it is easy to use the service. 

This is not a good user story primarily because?

• The story is not INDEPENDENT of other stories.

• The story is not TESTABLE because it has vague criteria of success.

• The story is not NEGOTIABLE because it specifies exactly how the programmer should implement the solution.

• The story has no business VALUE and a user who is not really an end user.

User Story: 

As an online student, I want the option to blur my background so that people don't see how messy my dorm room is.

This is not a good user story primarily because?

• The story has no business VALUE and a user who is not really an end user.

• The story is not SMALL and should be broken into multiple stories.

• The story is not NEGOTIABLE because it specifies exactly how the programmer should implement the solution.

• No reason as this is a good user story.

User Story: 

As an instructor, I want to have an intelligent filter to prevent students from raising their hands if they have a dumb question so that they do not interrupt the class.

This is not a good user story primarily because?

• The story has no business VALUE and a user who is not really an end user.

• The story is open ended and hard to ESTIMATE the effort.

• The story is not NEGOTIABLE because it specifies exactly how the programmer should implement the solution.

• No reason as this is a good user story, or at least a properly formed user story.