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:

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