Chapter 3: Requirements

After specification, requirements should be inspected to ensure they are (select all that apply):

• Correct

• Precise

• Complete

• Consistent

• Verifiable

When building user stories, what do we use to confirm that a story was implemented satisfactorily?

• Acceptance test

• Sprint Review

• Product Demo

• Product Owner

User stories should have what properties?

• Independent

• Negotiable

• Valuable

• Estimable

• Small

What do we call user stories that require multiple sprints to complete?

• Epics

• Tasks

• Releases

• Spikes

• Tops

What do we call the practice where developers independently decide to elaborate on certain stories or requirements without the customer’s input?

• Gold plating

• Requirements Engineering

• System Analysis

• A Typical Capstone

• Product Ownership

In agile, what is a spike?

• Tasks for knowledge acquisition or for creating a proof-of-concept implementation

• A sudden increase in the number of user stories added to the product backlog.

• A special type of sprint where only bug fixes are addressed.

• A metric used in Agile to measure how quickly the development team delivers features.

According to the textbook, what are the 3 steps of building an MVP? (select all that apply)

• Build

• Measure

• Learn

• Plan

• Deploy

If an MVP is successful, what are the next steps?

• Invest more resources and implement a more feature-complete and robust system.

• Freeze development and keep the MVP as the final product.

• Discard the MVP, document lessons-learned, and build the product from scratch.

If an MVP fails, what are potential next steps? (select all that apply)

• Abandon the venture

• Pivot

• Scale up

• Repeat the experiment

What is the purpose of A/B testing?

• Used to choose between two versions of a system based on user interest.

• To stress-test the system’s performance under heavy load.

• To ensure that all system components are integrated correctly.

• To identify and eliminate all software bugs before release.