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