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
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.


Similar posters

RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
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.