Acceptance Testing Backlog

Agile Backlog Grooming

Agile Manifesto Backlog Item

Binary Scale Backlog Item Effort

 An ever-evolving list of product requirements (user stories),
prioritized by the customer representative that conveys Formal testing conducted to determine whether or not a
features to implement. A top level backlog, known as a system satisfies its acceptance criteria and to enable the
product backlog or release backlog feeds the iteration or sprint customer to determine whether or not to accept the system.
backlog.

The process of adding new user stories, re-prioritizing existing Collection of incremental and Iterative development methods
stories, creating estimates for previously un-estimated stories, that provide customer value by resulting in working SW
and decomposing large stories. Backlog grooming is both an (shippable) at the end of each iteration (Sprint)
ongoing process and a meeting aka Story Time.

Four Statement Values:

A unit of work, usually a story or a task, listed on the project - Individual Integration vs Process / Tools
backlog. - Working SW vs Comprehensive Documentation
- Customer Collaboration vs Contract Negotiation
- Change Responsive vs Plan Centric

Vague units to estimate effort of product backlog items, not Best for user stories with high degree of variance because the
duration, not to be confused with actual working hours (used higher the value the greater the gap. Includes the values
for estimating sprint backlog). Common units: ideal 0,1,2,4,8,16, 32
engineering days, story points, t-shirt size, etc.
 Burn Down Chart Chief Programmer

Sprint Burndown Chart Class Owner

Characteristics of Successful Agile Crystal Methodologies

Crystal Yellow Crystal Clear

 Plots units of work that remain to accomplish (Y axis) against
(FDD) Responsible for completing business functionality. units of time (X axis). In Scrum, the Burn Down Chart is a
Oversees design & development of relevant feature sets key artifact.

A publicly displayed chart that depicts the total daily task

hours remaining in the Sprint in relation to achieving the
(FDD) Developer reporting to the Chief Programmer who Sprint goals. The X-axis represents days in the sprint, while
designs code, tests, and documents the Y-axis is effort remaining (usually in ideal engineering
hours).

- Small Teams (12 or less)

- Collocation
Highly Flexible and Lightweight people oriented approach, - Motivated, seasoned developers; self guiding
Family of adaptable methodologies; Scalable with 3 main - Lean Governance; team members are empowered to make
components: Chartering, Delivery cycles, and project wrap up decisions
- Customer Involved; Engaged Product Owner for continuous
feedback and End-of-Sprint Review

6 or less team members 6 - 20 team members

 Crystal Orange Date Drive [Planning]

Crystal Red Decomposition

CRUD Development Manager

Distributed Development Team Disaggregation

The release date is fixed and the variables are the features &
no of story points that can be reasonably developed.

No of Remaining Weeks / No Weeks per Iteration = No of 20 - 40 team members

Iterations;

No of Iterations * Team Velocity = Total Available Story

Point

The process of breaking epics and user stories down into a)

smaller, more executable user stories or b) tasks.
Decomposition is usually performed during backlog grooming 40 - 80 team members
and iteration planning, and is an important precursor to story
sizing (estimation).

(FDD) Coordinates daily activities of the dev team, resource Create, read, update and delete approach to classifying
balancing and management operational boundaries

Splitting user stories based on data or operation boundaries, Refers to development teams that work on the same project
cross-functional features, non-functional performance but are located across multiple geographic locations or work
requirements, or priorities of associated sub stories sites.
 Domain Expert Epic

Domain Model Exploratory 360 Degrees

DSDM Feasibility Fail-Fast

Fibonacci Feature Driven [Planning]

 A large, vague user story that is broken down into smaller
stories. Often a placeholder for new ideas that require more Business SME
investigation. Epic stories help agile development teams
effectively manage and groom their product backlog.

Executive Sponsors assesses the soundness of the project or Information model describing the application domain that
business value, requirements, domain model, etc. Used in creates a shared language between business and IT.
Crystal Development methodologies

Likelihood of meeting customer business requirements and

includes:
- Suitability of DSDM methodology
A property of a system or module with respect to its response - Scope
to failures. A fail-fast system is designed to immediately - risks
report at its interface any failure or condition that is likely to - Technical Solutions
lead to failure. - Cost Estimating
- Timescale (Schedule)
- QA Tests

Planning based on early inclusion of high priority user stories.

To calculate estimated completion date: Is a series of numbers in which each number is the sum of the
previous two numbers. This results in increasingly larger
Total No Story Points / Team Velocity = No of Iterations; intervals between numbers as the series progresses: 1,2, 3, 5,
8, 13, 21 …
No of Iterations * Weeks per Iteration = Total No of Weeks
(aka Target Date)
 Happy Path Incremental

Hybrid Waterfall Information Radar

Ideal Days Iterative

Kanban Iteration Burn Down

 Focus is on delivery of fully functional core features, less on
Delivery in short release cycles bugs, errors, and exception handling, which is captured in the
Backlog for a Bug-Fix iteration

Highly visible representation of project status; e.g. state of

user story, % of system tests failed, features removed. Phased based development method that allows for overlaps
Typically a large, visible board

Estimated no of days for a single developer to build, test and

release the user story functionality under ideal circumstance.
Repeatable process for developing SW These are NOT actual as they disregard delays, unexpected
events, absences, waiting time, distractions, and other
commitments.

The point value of work remaining in a Sprint Burn Down A form of Lean Development using a signaling system of
chart, which is based on the Team’s velocity and graphed cards to control the flow of work and show task status. The
daily. In Scrum, no new work allowed, so the trend line will board allows work to be "pulled" through based on availability
not rise unlike XP, where work may be added, so the trend of the successive step in the process rather than "pushed"
line may rise
Kano Model Milestone Table

Lean MoSCoW

Linear Scale Osmotic Communications

Pair Testing Pair Programming

 Graph based tool to objectively survey the customer for
(FDD) to track the progress (date and percent complete) of requirement priority: Y axis is customer satisfaction
each feature or feature set. Include 6 milestones: (1) Domain (Disappointed to Delighted). X axis is degree of
Walk-thru, (2) Design, (3) Design Inspection, (4) Code, (5) implementation (Poor to Good). Features are distinguished as
code Inspection, (6) promote to build Must-have, Linear, and Exciters

A DSDM prioritization scheme; "Must have, Should have,

Could Have, Would have" Must = Mission / business Set of guiding principles to complement other Agile
essential,; Should = Include if possible / can succeed without; development methods. Encourages development of only the
Could = Optional / doesn’t affect the business; Would = only necessary and discarding non-value add functionality.
if time / funds permit

Crystal principle where collocated team members The intervals are consistent between the values, e.g. 1,2,3,4.
unconsciously transfer information from one another through Planners may group values, e.g. 1 -4 and 7-9 for estimating
the "barrier" of awareness

An Extreme Programming practice, in which two developers Pair Testing is an extension of Pair Programming. It works
work together at one computer doing one programming task. best when using heterogeneous pairing (pairing of unlike
One is typing while the other is watching. It is a continuous people, e.g. pair a developer with a tester.
real-time peer review.
Planning Game Product Owner

Planning Poker Project Manager

Pirate Metrics Prototyping

Release Reference Point

 Is a role and serves as the primary business representative or
“voice of the customer / business” to the sprint team. In larger XP planning process; it is a meeting per iteration (weekly)
projects, multiple people can serve as the product owner. and address iteration / sprint planning and release planning.
However, per The SCRUM Guide - only 1 PO

A process using cards to represent possible story point

numbers for a group to choose, estimate independently ,
(FDD) Administers all aspects of the project: budget, interim compare, discuss and revise thus arriving at a consensus of the
deliverable schedules, reporting, etc. no of required story points. It is an adaptation of wideband
Delphi.

Developing working models of SW at regular intervals to A set of metrics designed to support LSU analytics and
discover potential problems and for user feedback; DSDM validation. AARRR is short for Acquisition, Activation,
core technique Retention, Referral, Revenue

The movement of a software product or system from

An average size story to compare all others (the bread box development into production. An Agile principle is to release
litmus test) SW when a minimum marketable feature set can be delivered,
followed by frequent incremental releases.
Release Burn Down Chart Scrum Team

Scrum Master ScrumBan

Scrum Master Is NOT Small User Story

Stand-Up Meeting Spike

Small team of developers, engineers, designers, DB Admins, The Team’s primary tool for visualizing velocity. The units of
work are derived from the Release Backlog, which received
etc. Typically 5 -8 people. (The SCRUM Guide) estimated point value during Backlog Grooming.

Maintains the Scrum process and the overall team health;

assuring it is fully functional and productive; administering
Hybrid method of Scrum and Kanban the Scrum ceremonies, facilitating its organic self-
organization, and removing impediments in the team’s
progress.

- A task master, since the team is responsible for assigning its

Too small and granular, distracting from overall planning. own tasks.
When possible, merge related, small stories - A supervisor, as hierarchical relationships may interfere with
team self-organization

"A short, daily all-hands meeting in which members of an

Agile team address three key questions:
A story or task (doing some actual work) aimed at answering a
question or gathering information, rather than producing What did you get done since the last stand-up?
shippable product. It is given an estimate and included in the
sprint backlog. Is an XP term What will you do before the next stand-up?

What impediments stand in your way?

Story Point Timebox

Task User Story

Task Board Velocity

Waterfall Visual Modeling

 A time period of fixed length allocated to achieve an A fixed amount of development effort or work. Can be
objective. In agile development, iterations and sprints are viewed as ratings scale for a particular team as the to the size
examples of timeboxes that limit work in process and stage and complexity of the work (story) in comparison to other
incremental progress. Timeboxes are often used to avoid over- stories in the backlog. Not the duration or cost of the work.
estimating.

Tasks are descriptions of the actual work that an individual or

An Agile requirement, stated as a sentence or two of plain
English. A user story is often expressed from the user’s point pair does in order to complete a story. They are manageable,
doable, and trackable units of work. Typically, there are
of view, and describes a unit of desired functionality. several tasks per story.

Measures a team's rate of work / progress (productivity) that A chart that presents, at minimum, “to do”, “in progress”, and
can be completed in a time-boxed iteration. “done” columns for organizing a team’s work; can include
backlog, etc. Ideally is physical, but can be an on-line
Actual Dev Time / Ideal Hours (time) OR story points application and is populated with tasks or user stories.
completed per iteration

Diagrams and other visual representations to convey to

customers an idea of how the SW will function. Used to Top-down planned, phased based development methodology
confirm the business domain is addressed. DSDM core
technique
 Workshop Product Owner Roles

Agile Project Management Scrum Master Does

Planning Poker Values Task Attributes

Critical Path Method Relative Weighting

 - Establishing and communicating the product vision
- Creating and leading the developer team to provide value to
the customer Structured meetings with various stakeholders to gain clarity;
- Monitoring the project against its ROI, goals and an DSDM core technique
investment
- Deciding when to create an official release

The style of project management used to support Agile

- Proactively anticipates problems, opportunities for software development. Essential features include:
improvement, and conducts pre-planning. Iterative dev cycles,
- Allows the team to focus on delivering its commitments and Self-organizing teams,
keeps it honest Multi-level planning
- Identify opportunities to improve collaboration. Dynamic scope,
Frequent collaboration with customers

- Description of the work (tech or business)

- Time estimate (hours, days) The "deck" represents the rating scale and it need not be
- Owner linear. Most common values are ? , 0, 1/2,
- Exit criteria and verification method (test or inspection) 1,2,3,5,8,13,20,40,100 and a (infinity)
- Assigned party responsible for the verification

Prioritization approach for stories, features, or projects that Network Diagram based project prioritization planning
considers the positive benefit of a feature and the impact of its method (PERT); groups essential iterations linearly (Critical
absence Path) and allowing completion of other iterations in parallel
 Metaphor

Code Refactoring

CRC
XP means to unify a system architecture and provide naming
conventions. A simple shared story of how the system works,
a metaphor. This story typically involves a handful of classes
and patterns that shape the core flow of the system being built

The process of restructuring existing computer code, without

changing its external behavior. Improves nonfunctional SW
attributes: readability, simplicity, maintainability,
extensibility, etc.

Class, Responsibilities, and Collaboration system design. A

CRC session simulates the system through cards. This process
step-thru identifies weaknesses and problems. Design
alternatives can be proposed and explored quickly within the
CRC.