Story Points

What is a User Story?

• A detailed technical specification

• A simple statement about what a user wants to do

• A project management tool

• A type of software bug

Who approves the User Story?

• The Stakeholders

• The Scrum Master

• The Product Owner

• The Development Team

What is the purpose of Story Points?

• To track project expenses

• To assess the relative weight/effort level of a User Story

• To measure the time required for a task

• To define project scope

Which of the following is a common pointing system used in Agile?

• Fibonacci Series

• Binary Code

• Linear Scale

• Decimal System

What does Velocity measure in Agile?

• The time taken to complete a project

• The total number of User Stories

• The number of Story Points completed during a Sprint

• The speed of the development team

What should be considered when sizing User Stories?

• The budget of the project

• The number of team members

• The location of the team

• The complexity of the User Story

What is a drawback of using Story Points?

• They provide precise time estimates

• They are universally applicable across all projects

• They can lead to inflation in estimates

• They are easy to calculate

What is the first step in pointing stories?

• Discuss team roles

• Review the project budget

• Assign random points to stories

• Identify a base story

What is the significance of the base story in pointing?

• It serves as a reference for comparing other stories

• It is the first story in the backlog

• It is the most complex story

• It is the last story to be completed

What does the term 'architectural maturity' refer to?

• The budget allocated for architecture

• The age of the project

• The existing functionality that does not need to be designed/coded/tested

• The number of team members