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:

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