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:

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