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:

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