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:

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