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:

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