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:

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