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:

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