Scrum Master Certificate

Front 1

What are the 4 Agile Manifesto values?

Back 1

Individuals and interactions over processes and tools.

Working software over comprehensive documentation.

Customer collaboration over negotiating contracts.

Responding to change over following a plan.

Front 2

What are the 5 core Scrum Values

Back 2

Commitment

Focus

Openness

Respect

Courage

Front 3

What are 8 XP Practices that make Agile Scrum more powerful?

Back 3

Pair Programming

Test Driven Development

Re-factoring

Continuous integration

Simple Design

Coding Standards

System Metaphor

Planning Game

Front 4

What are the 3 Scrum Artifacts?

Back 4

Product Backlog

Sprint Backlog

Burn up / Burn down chart

Front 5

What are the 3 Scrum roles

Back 5

Product Owner

Team Member

Scrum Master

Front 6

What are the 4 meetings/ceremonies?

Back 6

Sprint Planning

Daily Scrum

Sprint Review

Sprint Retrospective

Front 7

What happens in Sprint planning?

Back 7

Meeting where the team pulls in items from the product owner's prioritized backlog up to the point they are confident they can commit to delivering.

Front 8

What happens in the Sprint Review?

Back 8

The finished product for the just completed Sprint is demonstrated, and the Product Owner decides which PBI's have been completed.

Front 9

What happens in the daily Scrum meeting?

Back 9

Each person says what they completed in the previous day's work, what they will complete today, and what are impediments to completing their work.

Front 10

What happens at the Sprint Retrospective meeting?

Back 10

This is the meeting for continous improvements.
What worked?
What didn't work?
What can be changed?

Front 11

What is a Sprint Goal?

Back 11

A high level elevator pitch describing the features the team expects to produce and demonstrate to the product owner.

Front 12

WAG

Back 12

Expression of pure relative complexity of a feature in 5 levels S/M/L/XL/XXL.

Front 13

What is an ideal hour?

Back 13

An hour of undistracted work.

Front 14

What is a story point?

Back 14

An abstract unit of relative complexity. For example a small task might be 1 story point, and a xxl task might be 13 story points.

Front 15

What is the Product Backlog?

Back 15

A wish list of forced rank high level, simply described features desired for the product.

Front 16

What is the Sprint planning meeting?

Back 16

A meeting before the spring where the PBL features that are in the sprint are broken down into detailed tasks and estimated in ideal hours. Dependency management also occurs in this meeting.

Front 17

What is the Spring Backlog?

Back 17

List of tasks in the current sprint estimated in ideal days. Largest items can only take 1/3 of Sprint duration.

Front 18

What are the 3 measurements of Sprint Capacity?

Back 18

Raw Capacity: Total time with 100% of time allocated to team.

Available Capacity: Raw minus PTO, sick, training, travel.

Effective Capacity: Available minus drag factor.

Front 19

What is Scrum-of-Scrums?

Back 19

Longer once a week version of Scrum with all Product Owners, Scrum Master and team leads. 3 questions are same except they are for team. Plus potential for this team blocking other teams goals.

Front 20

What is S cubed?

Back 20

Once per sprint version of the daily scrum. Over-all program progress is discussed as well as conflicting priorities.

Front 21

What is a User Story?

Back 21

A user centered functional requirement. User functional requirements and user value are the primary focus.

Front 22

What is an Epic?

Back 22

A large User story or set of releated user stories?

Front 23

What is a task?

Back 23

A technical or functional sub-story unit of work. User stories are broken down into tasks.

Front 24

What is Acceptance Criteria?

Back 24

Funcitonal description of criteria that must be fulfilled to partially determine if a User Story has been completely implemented.

Front 25

What is Doneness?

Back 25

The total functional and non-funcitonal requrements including documentation, metrics, user acceptance.

Front 26

What is a Spike?

Back 26

Creating a prototype early on for a risky aspect of the project to determine a solution and identify issues.

Front 27

What is a Vertical Slice / Thin Slice?

Back 27

A complete slice of all software required to make a functional product but with just a few features. As opposed to developing complete functionality in a single module, but not being able to have a functional product.

Front 28

What is Test Driven Development?

Back 28

A technique of developing acceptance criteria and test code before writing functional code.

Front 29

What is Continuous Integration?

Back 29

The practice of creating frequent builds that include automated tests to continuously insure that the software is working.

Front 30

What are Pigs and Chickens?

Back 30

Pigs are Scrum participants that are committed to creating the deliverables. These are the team members. Chickens are the product owners.

Front 31

What are the responsibilities of the Product Owner?

Back 31

The product owner is responsible for providing the guiding vision for a product. Determining user centered, business value priority for the functional requirements. Usually the author and maintainer of the product backlog.

Front 32

What are the responsibilities of the Scrum Master?

Back 32

Helps team members to adhere to Scrum rules. Facilitates all Scrum meetings and activities, and enforcing time boxes. Helps manage Scrum artificats.Clear obstacles identified in daily scrum meetings. Prevents outside meddling in the Scrum process.

Front 33

What are the responsibilities of the Scrum Team?

Back 33

They commit to the delivery, and develop the product. Work with PO to select prioritized features from PB. Break down PBIs into tasks.

Determine how much work goes into Sprint Backlog. Deliver complete demonstrable shippable product at the end of every Sprint.

Front 34

What is an Anti-Pattern?

Back 34

Practices that prevent adoption of agile best practices.

Front 35

What is Smell?

Back 35

Signs that anti-pattern is present.

Front 36

What is an Information Radiator?

Back 36

Visual display of information where passer-bys can see it.

Front 37

Story Wall / Card Wall

Back 37

A physical card which display color code user stores and tasks written on index cards. User stories are swim lanes that task cards move within columns that represent various states of doneness.

Front 38

What is Burnup chart?

Back 38

A chart representing task doneness that trends upwards as tasks are done.

Front 39

What is a Burndown chart?

Back 39

Same as burnup except doneness trends downwards.

Front 40

What metrics are valuable?

Back 40

Delivery, value, and defects.

Front 41

What diagnostics are used?

Back 41

Performance, accuracy, and obstacle rates.

Front 42

What is the team room?

Back 42

Bullpen style room where team members work together and display their Information Radiators, Charts, Metrics, and Designs.

Front 43

What is Capacity Based Planning?

Back 43

Planning method where available work capacity and remaing work are counted in ideal work hours. Bad method.

Front 44

What is commitment based planning?

Back 44

Planning method where the teams deep understanding of what they are capable of allows them to plan without using detailed capacity planning.

Front 45

What is drag factor?

Back 45

A percentage based on team experience, length of time together, and domain knowledge that accounts for the difference between available capacity and effective capacity.