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:

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