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