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:

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