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:

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