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