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:

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