YAGNI
Agile Prioritization

YAGNI

Use it or do not do poster. YAGNI or You Ain't Gonna Need It is a principle for saving costs for things that are not required at the moment.
Read more
Get PDF
Tags
Abbreviation Acronym Agile Ain't Aren't Cost of building Cost of carry Cost of delay Cost of repairs Gonna image It Need Prioritization Software YAGNI YAGNI Principle You
Article

YAGNI


You Ain’t (Aren’t) Gonna Need It

A term coming from Extreme Programming’s (XP) Simple Design: Only the things that are needed at the moment are built.
  • More robust solution built now for the future benefits increases the cost of building as the plans can be changed and today’s solution can be unusable in the future.
  • The cost of delay appears as the result of building something we do not need now instead of something which can generate revenue earlier.
  • More robust solution also introduces more complexity and the cost of carry as a further modification which can be harder.
  • As everything evolves, past, not used, solutions most probably accumulated a technical debt and the cost of repairs connected to that.

Consider Yagni on both project level decisions and also smaller ones during development itself. It does not apply to effort to make the software easier to modify.


Resources
martinfowler.com agilenutshell.com medium.com wikipedia.org wiki.c2.com

Similar posters

Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.
Little's law
Little's law Little’s Law is a theorem for queuing systems. It determines the average number of items in a stationary queuing system
User Story Creation
User Story Creation Creating a User Story is a continuous process based on the 3Cs phases, supported by INVEST, 5Ws, and the Definition of Done.
Radical Candor
Radical Candor Radical Candor is a framework describing four different behaviors. In order to become Radically Candid you need to understand all four types.
GSD / Get Stuff Done Whee
GSD / Get Stuff Done Whee Get Stuff Done Wheel is a framework for aligning and guiding the work of a team. It allows teams to deliver remarkable results more quickly
AIDA Model
AIDA Model The AIDA model is a model, where a persona moves through a series of steps to make a purchase decision, used in marketing, sales, planning...