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