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:

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