US/Canada Home (/index.asp) Contact (/contactus.

asp)
(../index.asp) Register (/MemberRegister.asp) Login (/Signin.asp)

Search SCRUMstudy

Why Scrum? (/why-scrum.asp) Certication (/certication.asp) Enroll in Courses (/enroll-in-courses.asp)

Partners (/scrumstudy-partners.asp) SBOK Guide (/sbok-guide.asp) Corporate Training (/corporate-training.asp)

Free Resources (/free-resources.asp) About Us (/about-us.asp)

Like what you see? Share with friends

Scrum and Agile Glossary

Home Free Resources Scrum and Agile Glossary

Important Terms and Concepts

(/scrum-cse.asp) (Take printouts and Fold at the center to make Flashcards for quick reference)
Scrum Master Certied
Terms Definition

The product characteristics, specied by the Product Owner, that need to be satised
(/scrum-cae.asp) before they are accepted by the user, customer, or other authorized entity. These are
Acceptance Criteria
Agile Master Certied used as standards to measure and compare the characteristics of the nal product with
specied characteristics.

These tests are run from a business and customer point of view. These tests check the
(/scrum-spoc.asp) Acceptance Test requested and implemented feature and determine whether these features match the
Scrum Product Owner Certied business and the customer requirements

Acceptance-Test-
A system or product development method in which the acceptance criteria are
Driven
discussed extensively by the participants, through the use of examples and well-
Development
designed acceptance tests on the basis of the these criteria before development begins.
(ATTD)

Accuracy The degree by which the measured value is very close to the true value (PMI).
Accuracy The degree by which the measured value is very close to the true value (PMI).

It is the process of conrming and securing the team necessary to complete the a
Acquire Project
project. Skill, experience and availability of resources are important parameters
Team
considered while acquiring project team.

Desirable characteristic in a person, team, process or system measured in the

Adaptability ability/capability to adapt or being adapted. In organizational context, it refers to the
ability to change something or oneself to t to occurring changes.

Modication in the product being developed or in the process of product development.

Adaptation Variations in the actual value and true value trigger the need for control and
modication of the product or process.

Agile methodologies reduce waste by cutting back on work that does not add value.
Planning a project does not directly add business value. Therefore, planning at any stage
Adaptive planning of a Scrum project should be as ecient as possible. Planning ahead for the whole
project is considered waste, because Agile projects are prone to a high rate of change.
Therefore, planning is done Just in Time (JIT).

Adaptive Project Management is a structured, iterative process of management which

focuses on less up-front planning, unlike Waterfall methods. This creates a fairly
adaptable environment for teams where they focus on only the immediate tasks at
Adaptive Project
hand, complete them, and then move to the next tasks. If there are any changes in
Management
requirements, then they are incorporated into the next Sprint. This ensures you to be on
track with the quick changing market and technology scenario, enabling you to deliver
the greatest value in the shortest time to your customers.

This is done to take care of risks that were not initially identied or when the impact of a
Additional Risk
risk on objectives is greater than expected. The existing risk response planning may not
Response Planning
be enough to control the risk.

Agile is a group of iterative and incremental software development methods. It

Agile encourages exibility and speed in responding to change. It requires collaboration
between self-organized, cross-functional teams to generate requirements and solutions.

Agile Unied Process (AUP) is a renement of the "IBM Rational Unied Process (RUP)"
Agile Unied rst described by Craig Larman in 2001. Agile concepts and techniques are used to
Process select elements from RUP. Iterations are classied into two types: Development and
Release.
 A sequential development process in which the output from the previous step is used as
All-Before-Any
input for the next step in the process using a batch size of 100%.

The method used, or steps taken in, setting about a task or problem by the Scrum team.
Approach
The approach diers from team to team.

Any concrete by-product formed during the development cycle. Example of artifacts
Artifact
includes the Product Backlog and the Sprint Backlog.

Assumptions Factors which, for planning purposes, are considered to be true, real or certain.

A project management exercise that explores the validity of assumptions that were
Assumptions made at the beginning of the project to identify any potential project risk conceived and
Analysis developed because of the inaccuracy of any assumption. It also identies risks because
of any instability, inconsistency, or incompleteness of assumptions.

Basic Unied BUP is a simpler variation of Rational Unied Process (RUP) developed in 2005. It was
Process (BUP) optimized for small projects by IBM.

Behavior driven development (or BDD) is a software development process which

Behavior Driven
involves collaboration between non-technical or business participants and people with
Development
technical insight like developers, QA etc.

A group activity or creativity technique that can be used to generate and analyze ideas
Brainstorming
or to identify issues, risks, or even to determine solutions to problems.

A graphical representation of the amount of work completed/done versus the elapsed

time period. It is used to estimate the time needed to complete the project. The vertical
Burn down Chart
axis represents the planned work, and the horizontal work axis represents the time. The
general trend in the graph is to "burn down" to a point where no work remains.

A graphical representation of the amount of work completed against planned over a

period of time. The graphical trend line moves upward toward the goal line, hence called
Burn up Chart
"burn up" in contrast to "burn down." It is used to estimate the time needed to complete
the project.

In a commercial project environment, a seller could be any entity (subcontractor,

Buyer-Seller
vendor, or supplier) who manages the work of the project or delivers the product of the
relationship
project and the buyer is the customer who outsources the work to the seller.
 Cadence is the approach to achieving commitment and reliability with a system. It is a
Cadence measure of balance and the rhythmic ow of the process. Sprints of regular time
interval or duration establish a cadence for a development eort.

CMMI is a process improvement product suite. It was developed by the CMMI project as
Capability Maturity
a collaborative industry, government, and academic eort, which combined best
Model Integration
practices for software development. It is very eective for projects involving dened
(CMMI)
processes.

Capacity is dened by the amount of work that can be accomplished within the available
Capacity
resources.

A formal act or set of acts performed as prescribed by ritual or custom. Core Scrum
Ceremony activities like spring planning, daily scrum, sprint review, and sprint retrospective are
referred to as ceremony by the Scrum team.

The state of crisis that needs to be immediately addressed to prevent further harm or
Chaotic Domain
loss and re-establish the order. It calls for quick response.

A fable used in the Agile Project Management to dene the type of role an attendee can
play in Scrum. It derives from the fable of a chicken and a pig that planned to open a
Chickens and Pigs
restaurant together. Both of them are involved but only the pigs are committed. Pigs
have to get the project completed according to the requirements.

Chief Product The person responsible for the overall Product Backlog in product development with
Owner multiple Scrum Teams.

Chrysler C3 was a project to have a single payroll system for everyone in Chrysler. This project
Comprehensive ran from 1993 until DaimlerChrysler (after Chrysler was bought out) stopped the C3
Compensation project on February 1, 2000. Many Agile software development techniques were
System Project (C3) developed during this project; chief among them was Extreme Programming (XP).

A technique used in software development for restructuring/redesigning an existing

body of code without changing its behavior. The purpose of re-factoring is to improve
Code Refactoring
non-functional attributes of the software, e.g., managing technical debt or making
coding faster.

Collect Process of dening and documenting stakeholder's needs to meet the project
Requirements objectives.
Collective In a Scrum Project environment, the whole team is collectively responsible for ensuring
accountability that the work agreed on for a Sprint is completed in a timely manner.

Commitment means a conscious choice to do something. To bind or obligate oneself to

Commitment
a cause, person, or action, as by pledge or assurance.

Communications
Technologies or methods to transfer information among project stakeholders.
Technology

Complex Adaptive Numerous entities governed by common simple localized rules, which interact with each
System other in various ways and receive constant feedback.

A domain in the Cynen framework wherein the situation is unpredictable and the
Complex Domain
correctness of the answer is only known in hindsight.

Component teams are specialized teams organized around the architecture of the
product under development. A team that focuses on the creation of one or more
Component Team components of a larger product that a customer would purchase. Component teams
create assets or components that are then reused by other teams to assemble
customer-valuable solutions.

Conditions of satisfaction are the acceptance criteria specied by the product owner,
Conditions of which determine the desired behavior of the product that to be accepted. These are the
Satisfaction conditions under which the product owner is satised with the outcome of each product
backlog item.

Continuous Delivering the product or each product feature to its users immediately after it is
Delivery integrated and tested by the developer.

Continuous Delivering the product or each product feature to its users immediately after it is
Deployment integrated and tested by the developer.

On most traditional projects, lessons learned are compiled at the end of the project so
they can be applied to future projects. However, applying lessons to future projects
does not add value to the current project. Future projects may not be similar to past
Continuous
projects. Therefore, Agile aims to continuously learn during each project and apply
Improvement
lessons learned within the current project. Several tools, techniques, knowledge sets,
and skills can continuously improve Agile projects - e.g. retrospective meetings,
knowledge sharing etc.
 Monetary loss incurred due to delay in work, process, or achieving production targets.
Cost of Delay
This concept emphasizes that the time associated with project has a nancial cost.

Cross Functional A project team that has expertise from the dierent elds, like designers, developers,
Team and testers who have skills required to complete the work eectively and eciently.

The Crystal family of methodologies was developed by Alistair Cockburn in the mid-
1990s. The methodologies are named after colors and/or gemstones to indicate the
"weight" of methodology needed (as per the team attributes or strategic needs). The
Crystal
most famous is also the lightest, called "Crystal Clear," used for small teams with co-
located members working on noncritical tasks. The family focuses on eciency and
habitability as constituents of project safety.

The daily standup meeting, or Scrum meeting, is a daily team meeting in the Scrum
Framework. The name comes from the practice of the attendees standing up. This
Daily Stand-Up
encourages the members to keep the meeting short. It gives the team a regular
opportunity to monitor progress along the sprint plan.

A well-dened process that produces the same output for the same input every time
Dened Process (minus the minor variations within the range). The inputs, outputs and the steps
involved are clearly stated in such process.

Dened Process A process control approach used for dened processes. This model primarily involves
Control creating and maintaining processes that produce expected output.

Conditions that need to be satised by the product backlog item before it is considered
Denition of Ready
ready to pull into a sprint during sprint planning.

The Delphi Method is an estimation/surveying method in which estimates and opinions

Delphi Method are collected anonymously from a panel. This reduces the bias that may arise due to the
power/inuence of certain panel members.

A development team is formed with members from dierent areas of functional

Development Team expertise. It has to be self-organized, and it must drive toward a single goal. This team is
collectively responsible developing of an acceptable product.

This is one of the domains in the Cynen framework. This is a dangerous stage, and the
Disorder Domain priority should be to come out of this domain because we either don't understand or
can't make sense of the situation we are in.
 This technique is used for identifying items with higher priority. Participants have to cast
their vote by placing a colored dot against one item among the listed, and the item with
Dot Voting
most dots is considered an item of higher priority. This technique is frequently used
during the sprint retrospective.

Economic lter is used as a decision-making criterion by the organization to evaluate the

Economic Filter
economic benets of the project under consideration and whether to fund it or not.

A process control approach used when processes are incompletely dened and the
Empirical Process
output is unique. This model leverages frequent inspection, adaptation and
Control
transparency. Scrum enables empirical process control for project management.

End uncertainty is the uncertainty surrounding the properties of the nal deliverable of
End Uncertainty
a project or process.

An epic is a large user story, typically one that is too big to t in a single sprint. Epics
Epic need to be broken down into smaller user stories at some point before implementation
as part of a sprint.

An Agile Method sourced from Rational Unied Process (RUP), Capability Maturity Model
Integration (CMMI) and Agile processes. Used primarily for software development, it was
Essential Unied developed by Ivar Jacobson, one of the original contributors to RUP, as an improvement
Process on the Rational Unied Process. It is practice centric rather than focused on
processes/roles. It relies on Separation of Concerns, a principle of separating the
product into separate sections, each addressing a separate concern.

A rough calculation of the number, quantity, or size of product backlog items, portfolio
Estimation
backlog item, and sprint backlog task.

A technique used during sprint retrospective, which involves chronological depiction of

Event Timeline
events that occurred over a period of time.

Judgment provided by expert (s) in specic area on matters or activities being

performed in that area. Expert could be a person or group with specialized training or
Expert Judgment
education, knowledge and skill. The expertise could also be acquired with time and
experience.

Estimating or predicting future project status and progress based on knowledge and
Forecasting
information available at the time of forecasting.

Functional Testing usually describes what the system does. Here functions are tested by
 Functional Testing usually describes what the system does. Here functions are tested by
feeding input and examining the output. It is type of 'Black Box Testing' where we do not
Functional Test
consider the internal program structure and mostly compare the actual and expected
outputs.

In Japanese, this means "go and see for yourself." It is the conviction that real time
experience is more useful than theory. One must see the problem to understand the
Genchi Genbutsu
problem rather than hear about a problem from someone else. This will help in making
an informed decision about the solution.

Group Decision Used to generate, classify, and prioritize product requirements. Some methods used to
Making Techniques reach group decisions are: unanimity, majority, plurality, and dictatorship.

A factor that's causing a hindrance or blockage from performing scrum in an eective

Impediment
manner in a team or organization.

Impediment log captures or records impediments, description of the impediments,

impacts of the impediments, the solution, if any and status of the impediments. The
Impediment Log
format may vary. It is recommended that the Scrum Master update the log after each
Daily Stand-up.

Funding a part of the product development without committing to funding all of it. With
Incremental incremental funding, only a small part of the development eort is funded, after which
Funding the funding decision is critically valued to see what is being paid to get from this small
part.

Information A visual display that presents suciently detailed, up-to-date, and important
Radiator information to passersby in an easy self-interpretative format.

A mathematically intense process of dening, measuring, and communicating

Innovation improvements in innovation. This framework tries to identify the reasons for dierences
Accounting in innovative output between teams are dierent time periods. Commonly used as a
metric to measure progress of startups.

The opportunity lost to create an innovative solution. Usually occurs when a prescribed
Innovation Waste
solution is provided with a product backlog item.

The combination of various components of a product to form a coherent, larger-scope

Integration
work product that can be validated to function correctly as a whole.

Internal The stakeholders who are internal to the organization, i.e., those who are involved in
Internal The stakeholders who are internal to the organization, i.e., those who are involved in
Stakeholders product development. For example, senior executives, managers and internal users.

A formal or informal approach to obtain information from stakeholders by talking to

Interviews
them directly

Iterative Product In iterative product development, the nal product is developed over a few iterations
Development and delivered to the customer.

This term means "signboard" in Japanese. Taiichi Ohno adapted the word used for shop
Kanban signboards to depict the following philosophy: A down steam process must go and fetch
what it needs--similar to how we go and fetch what we need from a shop/store.

Named after Noriaki Kano, a Japanese professor Kano Model is used to map what is
valued by the customer by classifying the product attributes into basic, performance,
Kano Model
and excitement categories. It can be used to determine the minimally viable product
that a customer will feel satises his or her basic requirements.

A status category for technical debt that represents the debt that is known to the
Known Technical development team and has been made visible for future consideration. Contrast with
Debt "happened-upon technical debt" and "targeted technical debt." See also "technical
debt."

Lean Manufacturing or simply Lean focuses on the removal of waste from the
production. It is a practice for delivering more or same value with less resource by
Lean eliminating waste across organizations and business processes. Lean considers an
element or activity as 'Waste' if the same is used for purposes other than creating value
to the customers.

Lean Product LPD is the application of Lean Principles to product development. It is one of the initial
Development (LPD) Agile methods.

1. The total prot potential for a product over its lifetime. 2. The total prot potential of
Lifecycle Prots
the entire portfolio rather than a single product.

Means uncertainty is the uncertainty surrounding the means through which a

Means Uncertainty
deliverable will be created.

Minimum The smallest or minimum set of functionality related to a feature that must be delivered
Marketable for the customer to perceive value (for it to be marketable). Contrast with "minimum
Features (MMFs) releasable features."
Features (MMFs) releasable features."

Minimum Viable A product with just those minimal features that allow it to be deployed, and no more.
Product (MVP) Usually, MVP is the result of the rst sprint.

A technique used to categorize the importance of dierent attributes in a product from

Customer point of view to enable the development team to place importance on the
MoSCoW delivery of each requirement. This teaching is useful in dening the 'Acceptance Criteria'
of a product by specifying 'Must Have, Should Have, Could Have, and Won't Have'
requirements.

This is a Japanese term used to refer to any wasteful activity that has no value. Muda is
an essential factor in Kanban. In order to run a business, an organization has to produce
goods or provide services for the customer to buy or pay for. This requires a process,
Muda and this process makes use of resources. The waste factor comes into the picture when
resources are consumed unnecessarily. The Kanban approach increases awareness of
wasteful resource consumption and helps identify waste and unexploited prospects and
opportunities.

In Japanese, this term means unevenness or inconsistency in physical matter or

Mura human spiritual condition. In Kanban, Mura is reduced by equipping the process with
the exact part, at the exact time, in the exact amount.

This Japanese word is used for overburden, unreasonableness or absurdity. Kanban

avoids Muri through standardized work. First, a standard output is dened so that there
Muri can be an eective judgment of quality. Then, the elements in each process are
simplied for examination and recombination. The process is then standardized to get a
standard condition.

Must-have The set of features that must be present in the upcoming release for the release to be
Features viable.

Nice-to-have These are the features that are targeted as "would be nice to have" in an upcoming
Features release but can be left out if there is a shortage of funds to complete the project.

Objective Denition is part of a Sprint Planning Meeting, wherein the Product Owner
Objective
explains the prioritized items in the Product Backlog and the team commits to the
Denition
Product Backlog items to be completed during the Sprint.

An open source process framework developed by the Eclipse Foundation from Basic
Open Unied
Unied Process (BUP) of IBM. The Core principles are: iterative life cycle, collaboration,
Process
 Unied Process (BUP) of IBM. The Core principles are: iterative life cycle, collaboration,
Process
Management of requirements and Cognizance of architecture.

Organization Chart Charts that are used to show positions and relationships in a graphical format.

Pair programming is a programming technique in which two programmers working

together on a single system. This practice has been around since the 1950s. Many
Pair Programming studies have shown that pair programmers are more than twice as ecient; in code
production and especially in freedom from bugs, than one single programmer on a
single system.

Plan Risk
Process of dening how to conduct risk management activities for a project.
Management

An Agile estimation practice which is a variation of the wideband Delphi method of

consensus based estimation. It is used to estimate eort or relative size of user stories
Planning Poker
by assigning story points to each user story. This technique can also be used for
meetings where the team estimates risk in dierent modules.

The unfortunate phenomena of inating the value of product backlog size estimates in
Point Ination an attempt to conform to or optimize an unwisely conceived measure (such as achieving
a target velocity).

Highest level of backlog in Agile framework; it is composed of products, programs,

Portfolio Backlog
projects, or high-level epics. See also "portfolio planning."

Sessions scheduled for the purpose of rehearsing and performance improvement are
Practice called practice. For example, the principle of demonstrating progress is supported by
the sprint review Scrum practice.

Degree by which the values of repeated measurements are clustered and have little
Precision
scatter [PMI].

Prevention is an activity that can reduce the probability of negative consequences

associated with project risks whereas inspection measures to verify whether an activity,
Prevention vs.
component, product, or service conforms to specied requirements. The cost of
Inspections
preventing mistakes is much less than the cost of correcting the mistakes found during
inspection.

Principle of Least
Acting or developing work products in a way that is least likely to astonish the users.
Astonishment
Astonishment

Prioritization The process of ordering a list according to a given attribute.

Scrum believes in delivering the greatest amount of value in the least amount of time.
Prioritized Delivery This requires prioritized delivery in which "what will be done" has to be chosen from
"what has to be done" according to business value.

A prioritized list of work to be performed in a project. In the Scrum framework, this

Product Backlog
evolves with the business need and the environment .

Product Backlog The ltering of tasks on the product backlog based on their importance as per criteria
Grooming set by the product owner.

Product Backlog An item such as a feature or benet that is valuable to the process of product
Item (PBI) development.

Product Documents the characteristics of the product, or deliverable which the project is
Description undertaken to create.

Product
The entire scope of the eort put in to create or enhance a product or service.
Development Eort

The leader of the product development team. The voice of the stakeholder community
Product Owner
to the scrum team. The product owner denes what to do and in what order to do it

Product Owner A person authorized by the product owner to act on his behalf in particular situations.
Proxy See also "product owner."

A product road map is a high-level plan that shows when in the future new products are
expected to be developed or introduced by the organization/team. The requests to edit
Product Roadmap
the road map (usually by adding new products) come from the sales force or senior
management in the company when the marketing strategy is made.

Product Scope Features or services that characterize a product, result, or service

A statement describing the desired future state that would be achieved by developing
Product Vision and deploying a product. A good product vision is simple, easy to understand statement
and provides a coherent direction to the people who are asked to realize it.

Progressive Breaking-down, in an organized manner, large lightly detailed product backlog items
Progressive Breaking-down, in an organized manner, large lightly detailed product backlog items
Renement into a set of smaller, more detailed items.

The set of up-front work needed to dene a project at particular level of detail so that a
Project Chartering
funding decision can be made.

Project Closeout Processes and procedures developed for the closing or canceling of projects.

It can include correspondence, memos, meeting minutes, and documents describing the
Project Records
project.

The degree to which a set of inherent characteristics fulll requirements (t for

Quality
purpose).

Describes in specic terms a project or product attribute and how it is measured by the
Quality Metrics
quality control process.

A term adapted from Lean Manufacturing. An inventory of items that wait for the next
Queue
action in the work stream.

Asoftware development processrst named and introduced in 1991. It prioritizes

Rapid Application
faster development and application maintenance facilitation over functionality and
Development
performance.

It is a combination of software development models created in 1996 in the Rational

Rational Unied Software Corporation. It is a process framework; where individual building blocks
Process could be chosen and adapted to suit the project at hand. It was aimed to give the
advantages of both waterfall and rapid application development models.

Recruitment
The policies, guidelines, or procedures that govern the recruitment of sta.
Practices

A term borrowed from Lean Manufacturing. The function of release planning is to

Release Planning synchronize projected range of potential delivery dates in the future with tasks to be
done today.

A technique of planning product releases on regular or cyclic time period. Made famous
Release Train by Cisco for its IOS software platform, each release is then decomposed into several
projects for Multiple Products.

One of the planned risk responses in which we try to avoid the risk entirely by changing
Risk Avoidance
 One of the planned risk responses in which we try to avoid the risk entirely by changing
Risk Avoidance
some aspect of the project.

A well-dened set of responsibilities that may be fullled by one or more people and for
Role which they are accountable. The three Scrum roles are product owner, Scrum Master,
and development team.

A common practice or generally prescribed method of action in a particular situation. A

Rule rule may be broken when the need of a situation dictate that a deviation from the
normal course of action is needed. The Scrum framework includes rules.

A methodology originally rened in 1995 by Ken Schwaber and Je Sutherland from

work done by Hirotaka Takeuchi and Ikujiro Nonaka. Named after the SCRUM in Rugby,
this is the most recognized Agile framework. It is an iterative methodology that treats
Scrum
major portions of development as a controlled black box. Iterations called sprints are
used to evolve the product which is ready to ship after each sprint [Schwaber, Ken
"SCRUM Development Process"].

Scrum board is used to plan and track progress during a Sprint which usually contains
three columns to indicate the progress of the estimated tasks for the Sprint: a To Do
Scrum Board column for the tasks not yet started, a Work in Progress column for the tasks
started but not completed, and a Done column for the tasks completed. Scrum
board also contains the Sprint burn down chart and space for unexpected items.

A set of principles, values, practices and rules that form the base for Scrum-based
Scrum Framework
development.

The Scrum Master is one of the three Core/Pig roles on a Scrum team. Scrum Master
Scrum Master facilitates Scrum and is responsible for removing obstacles; thus enabling the team to
deliver the sprint goal/deliverable.

Scrum of Scrums is analogous to the Daily Scrum. This meeting is facilitated by the Chief
Scrum of Scrum Scrum Master and usually conducted in large projects where multiple Scrum teams to
work in sync to ensure project progress.

There are three core roles in Scrum: The Product Owner, The Scrum Master, and the
Scrum Roles Scrum team (also called the development team). These are the people responsible for
completing the project objectives.

A Scrum team is composed of a product owner, Scrum Master, and development team,
Scrum Team
responsible for the high-quality and timely delivery of sprint commitments.
 responsible for the high-quality and timely delivery of sprint commitments.

A team or a group of people that manage themselves, their time and resources is said to
Self-Organized
be self-organized.

A sprint review activity where the product backlog items that are completed will be
Sprint Demo demonstrated. The intention is to encourage an information-rich discussion between
the Scrum team and other sprint review participants.

The sprint goal is what is to be accomplished by the end of the sprint. Its a summary
Sprint Goal of the activities/results elaborated by the product backlog items that the Product Owner
would like to accomplish during the sprint.

Sprint Planning The sprint planning meeting takes place at the beginning of each sprint. The purpose of
Meeting the meeting is to dene the objectives and tasks.

Sprint Its the review and analysis done at the end of every sprint. The aim is to improve the
Retrospective performance of the Scrum team and adopt better practices.

The sprint review meeting takes place at the end of each sprint. The delivery team
Sprint Review shows what they accomplished during the sprint. Activity attributes are reviewed,
modied, and reconciled at every sprint review meeting.

Stang Pool Characteristics of those prospective sta that is available to join a team.

Stang Denes what kinds of competencies are required from what kind of individuals or
Requirements groups and in what time frames.

Any person or entity who can aect an endeavor / project, or be aected by it, or be
Stakeholder
perceived itself to be aected is a stakeholder.

Statistical Sampling Sampling which involves choosing part of a population of interest for inspection.

Status Review Meetings that are regularly scheduled to exchange and analyze information about the
Meetings project status and its performance.

The abstract measure of eort to implement a story is called a story point. Typically
Story Point
determined by engaging in planning poker.

The appropriately aggressive pace at which a team works so that it produces a good
Sustainable Pace
ow of business value over an extended period of time without getting burned out.
 ow of business value over an extended period of time without getting burned out.

Synchronization is the coordination of events to operate a system in unison. Frequently

Synchronization used to ensure that multiple Scrum teams work together in a coordinated way by
starting and ending their sprints on the same days.

Graphical representation of a process showing the relationships among various process

System or Process
steps. During quality planning, owcharts would assist the project team in anticipating
Charts
quality problems that might occur. Commonly used in waterfall methods.

A chart/board that depicts all the work the team is doing during a sprint. There are 5
Task Board
columns: "Story," "To do," "In progress," and "done."

The team breaks down the selected Product Backlog items into tasks and then the tasks
Task Estimation are estimated by the team members according to their complexity, risk involved,
potential time required, and so on using team exercises.

Team Building Activities specically taken by management and team members to help individual team
Activities members work together eectively, thereby improving team performance

A technique is a procedure used to accomplish a specic activity or task. Its a dened

Technique
procedure that is used to perform some or all of an activity or support an approach.

A xed duration of time during which an activity is performed. In Scrum, sprints are time
Time Box
boxed iterations.

Tolerances vs. Tolerances indicate specied range of acceptable results. Control Limits are the
Control limits thresholds, which indicate whether the process is out of control.

One of the key principles of Scrum is transparency, wherein the customer is constantly
Transparency aware of the product progress, and the team members are aware of their roles and
responsibilities.

A mathematical technique to forecast future outcomes based on historical results. This

Trend Analysis
is performed using run charts.

Also called symptoms or warning signs, they are indications that an event has occurred
Triggers
or is about to occur. Commonly used in Risk Management.

A User Story is a statement (or a group of statements) that expresses the desired end
User Stories user functionality. User Stories are generally simple, short, and easy to implement.
 User Stories user functionality. User Stories are generally simple, short, and easy to implement.
Longer User Stories are further broken down into multiple User Stories.

The Product Owner (PO) represents the stakeholders and is responsible for ensuring
Voice of that the team delivers value. The PO is responsible for ensuring clear communication of
Customer(VOC) product functionalities to the Scrum team and, therefore, is commonly called the Voice
of Customer.

The wideband Delphi method is a variation of the Delphi method. Here, after a round of
Wideband Delphi response collection, the panel members are shown the gathered data and the
Method originators of responses far from the mean are asked to justify their survey
response/estimate. This is then followed by another round of response collection.

Won't-have A set of features/options that are specically declared to not be available in the
Features forthcoming release.

Refers to work that has been undertaken but not yet completed. If large segments of
the project are WIP, it can pose several problems. Identifying bottlenecks in the project
Work In Progress becomes dicult when several tasks are WIP at the same time. Each WIP requires
capital and does not contribute to ROI until it becomes a completed, usable product.
Kanban boards are eective in placing limits on WIP.

SCRUMstudy Scrum Master, Scrum Product Owner, Agile Certication Rating: 4.8 out of 5 (3256 votes).

2015 SCRUMstudy.com. All Rights Reserved

Home (/index.asp) | Who we are (/why-scrumstudy.asp) | Why Scrum? (/why-scrum.asp) | Scrum Principles (/scrum-principles.asp) | Scrum Aspects (/scrum-

aspects.asp) | Scrum Fundamentals Certied (/introduction-to-scrum-course.asp) | Scrum Developer Certication (/scrum-developer-certication.asp) | Scrum

Master Certication (/scrum-master-certication.asp) | SCRUMstudy Agile Master Certication (/agile-certication.asp) | Scrum Product Owner Certication
(/scrum-product-owner-certication-training.asp) | Scrum Master Certied Classroom Courses (/scrum-master-certication-training.asp) | SCRUMstudy Agile

Master Certied Classroom Courses (/agile-certication-training.asp) | Scrum Product Owner Certied Classroom Courses (/scrum-product-owner-certication-

training.asp) | Contact (/contactus.asp) | Sitemap (/sitemap.asp)