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:

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