AGILE 1 PRACTICE GUIDE

Question 1

This is a method used for managing projects and developing products that involves executing each of the four parts of the cycle iteratively throughout a project. Both Traditional and Agile Project Management use the iterative PDCA Cycle.

Answer 1

Plan-Do-Check-Act (PDCA)

Question 2

An ordered list of user-centric requirements that a team maintains for a product.

Answer 2

BACKLOG

Question 3

The net quantifiable benefit derived from a business endeavor. The benefit may be tangible, intangible, or both.

Answer 3

BUSINESS VALUE

Question 4

A Project management approach that provides finished deliverables that the customer may be able to use immediately.

Answer 4

INCREMENTAL LYFE CYCLE

Question 5

Project Management approach that allows feedback on partially completed or unfinished work to improve and modify the work.

Answer 5

ITERATIVE APPROACH

Question 6

This method involves continuously improving and detailing a plan as more detailed and specific information and more accurate estimates become available. It allows a project management team to define work and manage it to a greater level of detail as the project evolves.

Answer 6

PROGRESSIVE ELABORATION

Question 7

A regularly occurring workshop (usually at the end of sprint) in which participants explore their work and results in order to improve both process and product.

Answer 7

RETROSPECTIVE REVIEWS

Question 8

This is an iterative planning technique in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level. Use both in Traditional and Agile P.M.

Answer 8

ROLLING WAVE PLANNING

Question 9

A technique used for breaking larger sets of customer requirements into smaller pieces until they can be understood and implemented by the dev team. In Trdn - WBS. In Agile, high-level rqmnts are first broken down to Features, Epic Usr Stories, Detailed User Stories, Tasks.

Answer 9

DECOMPOSITION

Question 10

A concept - every project team member should constantly be thinking about ways to not only improve the quality of the product being delivered but also the processes that are being used by the project team throughout the project.

Answer 10

CONTINUOUS IMPROVEMENT

Question 11

A brief description of deliverable value for a specific user. It is a promise for a conversation to clarify details

Answer 11

USER STORY

Question 12

Number of Average Stories or story points completed per iteration

Answer 12

VELOCITY

Question 13

A term used in business and Information Technology to describe the in-depth process of capturing a customer’s expectations, preferences, and aversions.

Answer 13

VOICE OF THE CUSTOMER

Question 14

A special area where your team can discuss your project and solve problems together without calls and emails.

Answer 14

WAR ROOM

Question 15

Any unique and verifiable product, result, or capacity to perform a service that is required to be produced to complete a process, phase, or project

Answer 15

DELIVERABLE

Question 16

A method used to create and evolve a product, service, or result during the project life cycle, such as predictive, iterative, incremental, adaptive, or hybrid method

Answer 16

DEVELOPMENT APPROACH

Question 17

A rhythm of activities conducted throughout the project

Answer 17

CADENCE

Question 18

A collection of logically related project activities that culminates in the completion of one or more deliverables

Answer 18

PROJECT PHASE

Question 19

The series of phases that a project passes through from its start to its completion

Answer 19

PROJECT LIFE CYCLE

Question 20

A method of collaboratively creating acceptance test criteria that are used to create acceptance tests before delivery begins.

Answer 20

ACCEPTANCE-TEST DRIVEN DEVELOPMENT (ATDD)

Question 21

The progressive elaboration of project requirements and/or the ongoing activity in which the team collaboratively reviews, updates, and writes requirements to satisfy the need of the customer requests.

Answer 21

BACKLOG REFINEMENT

Question 22

A system design and validation practice that uses test-first principles and English-like scripts.

Answer 22

BEHAVIOUR-DRIVEN DEVELOPMENT (BDD)

Question 23

A brief, daily collaboration meeting in which the team reviews progress from the previous day, declares intentions for the current day, and highlights the obstacles anticipated. Also known as Daily Standup.

Answer 23

DAILY SCRUM

Question 24

A team’s checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use.

Answer 24

DEFINITION OF DONE (DoD)

Question 25

A visible, physical display that provided information to the rest of the organization enabling up-to-the-minute knowledge sharing without having to disturb the team.

Answer 25

INFORMATION RADIATOR

Question 26

A product quality technique whereby the design of a product is improved by enhancing its maintainability and other desired attributes without altering its expected behavior.

Answer 26

REFACTORING

Question 27

An organization structured in such a way that it only manages to contribute a subset of the aspects required for delivering value to customers. For contracts, see Value Stream.

Answer 27

SILOED ORGANIZATION

Question 28

The practice of attempting to solve problems by just using specific predefined methods, without challenging the methods in light of experience.

Answer 28

SINGLE LOOP LEARNING

Question 29

The practice of using a lightweight set of tests to ensure that the most important functions of the system under development work as intended.

Answer 29

SMOKE TESTING

Question 30

Describes a timeboxed iteration in Scrum

Answer 30

SPRINT