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:

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