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

How To Keep Development Scope From Growing Wild

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

A big problem with a garden is that it doesn’t stop growing. And so does the scope of a software development project.

A lot of effort is invested by gardeners in fighting the growing garden. They are constantly weeding, pruning, and trimming to control how the garden looks and to make sure it best serves its purpose.

How much are you investing in weeding your scope?

There you are, walking along the paths of your software development garden, listening, and looking for things that shouldn’t be there.

Suddenly you notice something odd. There is a lot of commotion around a new screen. You see it has spectacular features. You don’t remember asking for it to be so prominent – users rarely go there. You raise your machete and – Slash! Trim it to its right size.

You are in a design review. You notice the level of detail for this stage is much above what is required. A waste! Hack! You stop the discussion.

As you practice it becomes easier:

  • Swoosh! Why are we investing time in these validations? What is the chance of getting the such message?
  • Crack! Why are we fixing this defect? It is not important now and as a matter of fact, I don’t see when will it be important. (you have to be very creative with the sound you make to make the right impression).
  • Smack! We are investing too much in this framework. Let’s build only what we need now.
  • Ploing! Entering a string here is good enough. No need for the fancy widget now. (you get into the rhythm and start a dance).
  • Zeeeeng! Remember, our goal is to get feedback on the concept at this stage. Don’t mess with this end case.
  • Bloop! You just stepped into something left here by the legacy system…

The only way for a software project to be on time and meet the desired outcome is to constantly prune and trim the ever growing scope. This need to be done by everyone: from the product manager who sees the garden from above and identifies unwanted patterns in the growth, through the product owner who sees things from a close distance, to the developer who is there when little defects only germinate and new unnecessary but fascinating ideas sprout.

Subscribe for Email Updates:

Categories:

Tags:

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