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:

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