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:

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