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:

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