Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Develop it when it’s ripe

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

We need good metaphors to better understand software development. Good metaphors from our day to day can help us better understand this elusive domain.

Some time ago I wrote about traffic and not long ago I wrote about handling scope the same way you would handle a growing garden. In this short article, I would like to discuss the great opportunity for a better understanding of software development, hidden in fruits. Yes, fruits.

When I start coaching a team I will usually find that the backlog grooming is neglected. Backlog grooming is the process of preparing the scope for the sprint. We do this to reduce variability during the sprint. We do this to avoid surprises. It does have a cost, though – it means we need to invest time in things we will develop later, now.

There is the question of when is a story ready for development. We recommend having a “Definition of Ready” written and reviewed by the team, a list that will evolve as the team gains experience and understanding.

However, having a list will not solve your problems. Moreover, adhering too much to such a definition may cause more problems. We need to be flexible.

And so we come to fruits. For instance, let’s take a peach, one of my favorite fruits.

How do you know whether a peach is ripe?

First, it is very personal. Ripeness is a relative definition. Some people like soft peaches and some prefer more solid ones.  More than that, hungry soft-peaches-lovers may eat them solid (I’m not sure regarding the opposite, though).

In the same manner, you need to decide when a story is ready. First, it should be per team. Some teams would rather do most work during the sprint and some would prefer to have longer preparations. Second, taste changes. Some teams start with demanding very ripe scope but with time prefer to start more upstream.

To know whether a fruit is ripe you need to look at it and sometimes hold it and smell it. Same for a backlog item. You need to read it, you need to discuss it, you need to feel it.

Some fruits keep ripe for a longer time and some rot very quickly. The same with software. Be sure not to get too much backlog ripe too soon or bad smell will spread around the office.

One thing is sure: After you start eating fruit you should finish it very quickly! Do you know what nasty things happen to partly eat fruit? And the same goes for software. When you start on a story you need to finish it as fast as you can, otherwise, nasty things start to happen and one day you find something green lying on the bottom shelf of the refrigerator, right behind that jam that looked so good in the supermarket.

Now go eat a banana!

Subscribe for Email Updates:

Categories:

Tags:

Agile Release Management
Agile Development
System Integration Environments
Test Driven Development
Lean Budgeting
Agile Product Ownership
LPM
Amdocs
Slides
The Agile Coach
Games and Exercises
Software Development
Limiting Work in Progress
Atlaassian
Lean Agile
Lean Risk Management
Agile Basics
Advanced Roadmaps
Agile Product Development
Scrum With Kanban
LAB
Agile Testing Practices
Product Management
Elastic Leadership
Webinar
Reading List
NIT
ScrumMaster Tales
Achieve Business Agility
Kanban Game
Acceptance Test-Driven Development
ATDD
Nexus and SAFe
Risk-aware Product Development
Agile Delivery
Agile Israel Events
Agile and DevOps Journey
Manage Budget Creation
Scrum.org
Introduction to Test Driven Development
An Appreciative Retrospective
Applying Agile Methodology
speed @ scale
Agile Community
Hybrid Work
Effective Agile Retrospectives
Value Streams
Large Scale Scrum
TDD
Kaizen Workshop
Jira
Lean Agile Basics
Operational Value Stream
Pomodoro Technique
agileisrael
ARTs
SA
System Team
ATDD vs. BDD
Agile Exercises
Continuous Deployment
Implementation of Lean and Agile
Perfection Game
lean agile change management
Daily Scrum
What Is Kanban
Code
Legacy Code
Lean Startup
Kanban Basics
SAFe DevOps
Lean Software Development
Agility
Sprint Planning
Tips
Systems Thinking
Rapid RTC
Lean and Agile Principles and Practices
Iterative Incremental Development
AgileSparks
Agile Program
Principles of Lean-Agile Leadership
Professional Scrum Product Owner
RTE
Agile in the Enterprise
Managing Risk on Agile Projects
QA
Software Development Estimation
Planning
Agile Mindset
Portfolio for Jira
A Kanban System for Software Engineering
Lean-Agile Budgeting
Continuous Integration
BDD
Agile Risk Management
Artificial Intelligence
Video
SPC
Releases Using Lean
POPM
Agile Project Management
PI Planning
Introduction to ATDD
Program Increment
Presentation
Jira admin
speed at scale
ROI
Continuous Delivery
Legacy Enterprise
Jira Cloud
Kaizen
Sprint Retrospectives
Risk Management on Agile Projects
Self-organization
EOS®
AI Artificial Intelligence
Agile Games
Managing Projects
Risk Management in Kanban
Agile
Story Slicing
Tools
Agile Assembly Architecture
Lean Agile Leadership
LeSS
GanttBan
Nexus Integration Team
Nexus and Kanban
Business Agility
AI
Product Ownership
SAFe
SAFe Release Planning
Release Train Engineer
Lean and Agile Techniques
IT Operations
Certified SAFe
Change Management
Agile Games and Exercises
Agile Contracts Best Practices
Scrum Master
Jira Plans
Professional Scrum with Kanban
Development Value Streams
Engineering Practices
The Kanban Method
Agile Release Planning
Sprint Iteration
Certification
ALM Tools
Scrum Primer
Agile Project
Agile Outsourcing
Quality Assurance
System Archetypes
Entrepreneurial Operating System®
Implementing SAFe
Scrum and XP
Built-In Quality
Agile Marketing
Kanban 101
Accelerate Value Delivery At Scale
Scrum Master Role
Agile Israel
Lean Agile Organization
Nexus vs SAFe
ART Success
Scrum
Scaled Agile Framework
Agile Techniques
DevOps
Enterprise DevOps
Process Improvement
Continuous Planning
Continuous Improvement
Spotify
Lean-Agile Software Development
Agile for Embedded Systems
Agile India
Atlassian
Professional Scrum Master
Frameworks
WIP
predictability
Kanban Kickstart Example
Coaching Agile Teams
Scrum Guide
PI Objectives
Scrum Values
Kanban
RTE Role
RSA
Covid19
Lean Agile Management
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart