Agile Overview A-Z

Agile Overview
A-Z
By Jacqueline Sanders-Blackman

A is for Agile - It’s an approach on how you build software and
the software development lifecycle.
A is for Agile
copyright 2023 @ techexpressoconsulting.com

B is for Burndown Chart - Shows how much work is remaining
to be done in the project.
B is for Burndown Chart

Customer Collaboration - When the Agile team works constantly and
consistently with the product owner to to enhance and refine the product.
C is for Customer Collaboration

D is for Daily Scrum - It’s a 15-minute daily team meeting to share progress,
report impediments, and make commitments and forecasts.
D is for Daily Scrum

E is for Epic - A large user story that is a placeholder or describes a large
part of the solution that provides value and has to be broken down.
E is for Epic

F is for Face to Face Communication - Agile really emphasizes the
importance of face to face communication and collaboration.
F is for Face to Face Communication

NOTE: Due to the increasingly negative connotation of the word grooming, the industry is
replacing the word Grooming and discontinuing its use. The activity formerly know as
Grooming is now increasingly known as backlog refinement, backlog management
and/or “Story Time.” Grooming was originally used to reflect an organic approach to
maintaining the backlog: the intended imagery is that of trimming, pruning, cleaning, as
with a plant.
For More Information What is Backlog Refinement (Grooming)? | AgileAlliance.org
G is for Grooming
(The Word Grooming has been Replaced with Refining)

H is for High-Performing Team - A motivated and engaged team will want to do the right things.
They’d want to produce a high quality product and take pride in what they’ve produced.
H is for High-Performing Team

I is for Impediment - It’s anything that is standing in the team’s
way of achieving their stated or documented goals.
I is for Impediment

J is for Just-in-Time - A practitioner of accounting or accountancy
requirements should be delivered based on need rather than convenience.
J is for Just-in-Time

K is for Kanban Boards - A visual way of displaying our work on
a board.
K is for Kanban Boards

L is for Lean Development - Says to relentlessly eliminate anything that isn’t adding value
and only work on what we absolutely need to be doing at this moment in time.
L is for Lean Development

M is for Minimum Marketable Feature - Do the minimum
amount of work to deliver the best business value.
M is for Minimum Marketable Feature

N is for Negotiable - Anytime you attempt to influence or
persuade someone.
N is for Negotiable

O is for Osmotic Communication - It’s indirect information transferred through
overhearing conversations or simply noticing things happening around you.
O is for Osmotic Communication

P is for Product Owner - Responsible for decision-making and for driving
the direction of a product or a project related to their product.
P is for Product Owner

Q is for Quality - It’s a discussion and conversation around the
definition of “done” and “ready.”
Q is for Quality

Retrospective Meeting - It’s the meeting that occurs at the end of each Sprint to
reflect and to look for opportunities for continuous process improvement.
R is for Retrospective Meeting

S is for Sprint - It’s time-boxed increments or iterations, and in that timebox,
we commit on the front-end what we’re going to accomplish.
S is for Sprint

T is for Timeboxed - It’s defining a very discreet block of time to
complete an activity.
T is for Timeboxed

U is for User Story - It’s an “as a,” where you identify the person or the who, “I need/I want,” where
you identify the problem or scenario, and “so that,” where the value statement is defined. Put it all
together: As a _____, I want or I need _____ so that _____.
U is for User Story

V is for Velocity - It’s the measurement of the amount of work a
team can tackle during a single Sprint.
V is for Velocity

W is for Working Software - It’s fully integrated, tested, and ready
to be shipped to customers or deployed to production.
W is for Working Software

X is for XP Practices - Extreme programming stresses customer satisfaction. Instead of delivering
everything you could possibly want on some date far in the future, this process delivers the
software you need as you need it.
X is for XP Practices

Y is for Yesterday’s Weather - It’s an Extreme Programming
(XP) term to keep teams from over committing during
Sprints and iterations.
Y is for Yesterday’s Weather

Z is for Zero Defects - At the end of the day, it says setting a goal of absolutely zero defects is
unrealistic and can’t be done, especially in our world of software. However, set a limit to the
number of bugs that each developer can have outstanding.
Z is for Zero Defects

jsb@technologyexpresso.consulting
855-484-6837
linkedin.com/in/jacqueline007
@Jacqueline007
Stay in Touch
www.quora.com/proﬁle/Jacqueline-Sanders-Blackman

Agile Overview A-Z

Recommended

Recommended

More Related Content

Similar to Agile Overview A-Z

Similar to Agile Overview A-Z (20)

More from Jacqueline K. Sanders-Blackman, Agilist,CBAP,SSBB,CSM,SAFe

More from Jacqueline K. Sanders-Blackman, Agilist,CBAP,SSBB,CSM,SAFe (19)

Recently uploaded

Recently uploaded (20)

Agile Overview A-Z