CSM-001 Certified Scrum Master (CSM) Questions and Answers

Maintaining the Product Backlog with current information

Working with stakeholders to determine and detail product features

Assigning tasks to team members

Prioritizing the Product Backlog

A beginning of the day

Immediately after lunch

4:30 PM

7:00 PM

Team Members Name

Number of Product Backlog Items Completed

Number of Tasks Remaining

Work Hours Remaining

A sprint is a specific amount of days for a team to test and resolve any issues prior to product release or shipment

A sprint is a specific amount of days for a team to work at a sustainable pace to finish select work.

A sprint is an agreed upon period of time for team members to select individual items from the product backlog to work on.

A sprint is a specific amount of days for a team to work as many hours as needed to finish assigned work

Evaluating Data for Agile Marketing

Focus on Customers

Focus on Employees

Evaluating Data based on Current trends

The Product Backlog is equal to the Sprint Backlog

The Product Backlog is a subset of the Sprint Backlog

The Sprint Backlog is a subset of the Product Backlog

The Sprint Backlog is owned by the Product Owner

Alphabetically first and then by list order in the Product Backlog

Grouped by business features first and then chronologically by date of original business request

Prioritized by business importance first. The items that result in biggest ROI, must be priorized first;

Chronologically by date of original business request first and then by list order in the Product Backlog

Understanding what functionality the Product Owner desires within the next Sprint and figuring out how to do it.

Updating the scope of the release with all Sprints, end dates, and costs

Reviewing current functionality that binds the software solution

Recalculating empirical velocity, adjusting team capacity accordingly, and projecting end dates

Complete the project as estimated when the date and cost are committed to the Product Owner.

Turn the Product Backlog it selects into an increment of potentially shippable product functionality.

Do all of the development work, but not the types of testing that require specialized testing, tools, and environments.

Remove Carlos from the team.

Use Carlos as an asset, particularly during risk identification

Ignore him and hope it goes away

Escalate the issue with the higher authorities

A sustainable pace, usually from 7-8 hours per day.

An "ideal day" measuring only when he or she is productive.

However many hours are needed to get the work done.

14 hours.

Extra features

Task Switching

Path Analysis

Process Integration

Yes

No

User Stories

Use cases

Line items

Tasks