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:

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