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:

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