Agile A to Z
- Ritesh Chopade

- Feb 16, 2022
- 1 min read

Thought came in my mind that I should write vocabulary words for Agile methodology. This will help to understand spread key words in Agile.
Alphabet | Word | Meaning |
A | Agile | Agile is a software development methodology. Based on iterative & incremental approach where design & solution evolve through collaboration between self organized & cross functional teams |
B | Backlog | In Agile, backlog is continuously evolving prioritized list of requirements which are considered as nacessary and sufficient to complete working software or release. |
C | Customer Satisfaction | The highest priority of Agile is a happy customer, which is achieved by frequently delivering value to the consumer. |
D | DoD & DoR | Definition of Done and Definition of Ready are (checklist) explicit policy set by Scrum team to reduce the handoff, improved collaboration & bring in common understanding among team members. |
E | Empirical Approach | Agile foundation is Empirical approach. Empirical approach is research that is based on observation, measurement of phenomena & Inspect and adopt. The data thus gathered may be compared against a theory or hypothesis, but the results are still based on real life experience. |
F | Fail Fast | One of the basic strategy or principle in Agile where working software is continuously deployed so that we can get rapid customer feedback (positive or negative) which can be used by teams to continuous improvement of their software or product. This mindset of FAIL FAST leads to success more quickly than old way of waiting over long period to see software as a whole (Waterfall approach) |
G | Grooming Backlog | Scrum Teams conduct a backlog refinement / backlog grooming meeting where team brainstorm and understand the requirements which are satisfying DoR criteria. Team clarifies all their doubts and estimate the user stories from backlog with PO & BA. |
H | Highly motivated people | In Agile self-organizing team teams have highly motivated individuals who take ownership & collaborate directly with other teams if required |
I | Individuals and interactions | Another of the four Agile values is “individuals and interactions over processes and tools” which is a value that responds to the needs of the modern employee. |
J | Jira | Jira is Agile project management tool. It manages product backlog, stories bugs. It provides agile boards and reporting feature using which agile projects can be planned tracked and managed in single tool. |
K | KanBan | KanBan is one of the most flexible & popular framework used for agile & lean ways of working. In KanBan emphasis is on continual software delivery flow while not overburdening the development team. It works on 3 fundamental principles 1. Visualize the work flow (2) Limit WIP (3) Improve FLOW |
L | Lean | Agile is inspired from Lean philosophy. Agile Software Development uses various Lean principles. Lean has 7 principles for Software Development: Eliminate waste, Build Quality, Faster delivery, Respect people and empower them, Delay in decision making & Optimise the whole. |
M | MVP | Minimum Viable Product, is an technique where new products are developed with sufficient features to get early customer feedback. Based on initial version customer feedback; agile team enhance features in subsequent releases of the product. |
N | Niko-niko Calendar | A Niko-niko Calendar is updated daily with each team member’s mood for that day. Over time the calendar reveals patterns of change in the moods of the team, or of individual members. |
O | Outcome Measure | Agile & product mindset promotes outcome measurement over output. The outcomes are business value which customer want or needs to achieve. And Output are the actions which we take to achieve an outcome. |
P | Pair Programming | Pair Programming is an Extreme Proramming practice. In this practice two programmers work together on the same code sharing single workstation. One programmer will type the code and the other will be reviewing each line of code as it is getting typed. |
Q | Quick Design Session | When “simple design” choices have far-reaching consequences, two or more developers meet for a quick design session at a whiteboard where they assess alternative based on consideration such as simplicity. |
R | Retrospective | One of the most important ceremony in Agile Scrum Framework. This is time boxed meeting at the end of each sprint in which team Inspect or examines how we have performed as Team. Team do Inspect and see what learning we can adapt in next sprint to improve. Retrospective is key to continuous improvement. |
S | The team aims for a work pace that they would be able to sustain indefinitely. | |
T | Time Boxed | Time management technique in Agile help perform & manage work and meetings effectively. |
U | User stories | In collaboration with the customer or product owner, the team divides up the customer requirement / work to be done into small unit of work called as “user stories.” |
V | Velocity | In Agile velocity is a measure of teams predictability that how much work they can complete in a sprint / iteration. Velocity is calculated an average number of story points delivered by a team in last 3 to 5 sprints. |
W | Working Software | Agile Team aim to produce working software after each sprint with customer collaboration & continuous feedback loop. |
X | XP - Extreme Programming | Extreme Programming (XP) is an agile software development framework that puts emphasis on customer involvement, transparency, Quick and frequent value delivery by using engineering practices. |
Y | YAGNI | You Aren't Gonna Need It - This is an XP framework principle which advocate avoid any adding of functionality which does not add value to customer. |
Z | Zombie mindset | Zombie Agile is blindly adopting Agile without the right mindset which is required to implement effective Agile. |



Comments