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:

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