Agile

Question 1

Sprint backlog

Answer 1

a list of work items your team plans to complete during a project sprint. These items are usually pulled from the product backlog during the sprint planning session.

Question 2

Product backlog

Answer 2

a prioritized list of work for the development team that is derived from the roadmap and its requirements. The most important items are shown at the top of the product backlog so the team knows what to deliver first.

Question 3

Product but up chart

Answer 3

a visual representation of a team’s work process. It displays the scope of a project and the work completed. Using a burn-up chart, a team can easily track their progress as they work towards completion of a sprint.

Question 4

Sprint burn down chart

Answer 4

A chart that shows the amount of work that has been completed in an epic or sprint, and the total work remaining. Burndown charts are used to predict your team’s likelihood of completing their work in the time available. They’re also great for keeping the team aware of any scope creep that occurs.

Question 5

Gulf of evaluation

Answer 5

the degree to which the system/artifact provide representations that can be directly perceived and interpreted in terms of the expectations and intentions of the user

Question 6

Exploratory testing

Answer 6

an approach to software testing that is often described as simultaneous learning, test design, and execution. It focuses on discovery and relies on the guidance of the individual tester to uncover defects that are not easily covered in the scope of other tests.

Question 7

User personas

Answer 7

An archetype user representing a set of similar end users described with their goals, motivations, and representative personal characteristics

Question 8

Caves vs. Commons

Answer 8

Caves: private spaces for one on one phone calls or conversations

Commons: primary work area

Question 9

Minimum viable product (MVP)

Answer 9

a product that has enough functionality and features so that early adopters are likely to use it or even purchase it.

Question 10

Definition of done (DOD)

Answer 10

an agreement between a product team on the set of conditions that must be true in order to consider backlog items truly done.

Question 11

Lead time

Answer 11

the time from the moment the customer makes a request to the time they receive something.

Question 12

Cycle time

Answer 12

the time it takes the development team to work on the request and deliver it. Cycle time is a a subset of lead time

Question 13

Defect cycle time

Answer 13

Amount of time between when the defect was discovered and when it was fixed

Question 14

product owner

Answer 14

Designated person that represents the customer on the project

Question 15

sprint planning meeting

Answer 15

meeting done by the agile team to determine what features will be done in the next sprint

Question 16

sprint backlog

Answer 16

Work the team selects to get done in the next sprint

Question 17

daily stand up meeting

Answer 17

A quick meeting each day to discuss project statuses, led by the Scrum Master. Usually 15 minutes

Question 18

sprint

Answer 18

iteration

Question 19

sprint review

Answer 19

An inspection done at the end of the sprint by the customers

Question 20

retrospective

Answer 20

Meeting done to determine what went wrong during the sprint and what when right. Lesson learned for the sprint.

Question 21

partially completed product

Answer 21

Customers Demo the product and provides feedback. This feedback adjust the next Sprint priorities

Question 22

release

Answer 22

Several Sprints worth of work directed to operations for possible rollout and testing

Question 23

Timebox

Answer 23

a fixed maximum time period you define for a process within a project that has its own tasks, a goal, and deliverables

Question 24

Wideband Delphi

Answer 24

a consensus-based estimation technique for estimating effort. Useful when estimating time to do a task. Participation of experienced people and they individually estimating would lead to reliable results. People who would do the work are making estimates thus making valid estimates.

Question 25

Product vision box

Answer 25

practical and collaborative exercise, usually carried out at the beginning of a new project, that helps team members to define and internalize the vision.

Question 26

Coarse grained requirements

Answer 26

Not to get too much into detail when defining requirements

Question 27

Kaizen

Answer 27

a strategy where employees at all levels of a company work together proactively to achieve regular, incremental improvements to the manufacturing process. In a sense, it combines the collective talents within a company to create a powerful engine for improvement.

Question 28

Ideal time

Answer 28

the time it takes from a resource to complete a task without any distractions for example: what time takes you without any traffic or problems to drive from home to work?

Question 29

Planning poker

Answer 29

also known as “scrum poker” and “pointing poker”, is a gamified technique that development teams use to guess the effort of project management tasks. These estimations are based on the entire group’s input and consensus, making them more engaging and accurate than other methods.

Question 30

Risk burn down chart

Answer 30

tool that project managers can use to show graphically how risk could affect project completion. It is designed to show risks that could be detrimental to the project as well as risks that could improve the project’s completion.

Question 31

Agile improvement process

Answer 31

Plan, develop, evaluate, and learn

Question 32

Pre-Mortem

Answer 32

a managerial strategy in which a project team imagines that a project or organization has failed, and then works backward to determine what potentially could lead to the failure of the project or organization.