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:

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