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