Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

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