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:

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