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:

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