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:

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