Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Handling Reminisces of a Glorious Waterfall Past

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

As a coach, I’ve had several opportunities to be involved in the process of big organizations moving from waterfall to agile. You usually start with frowning faces, people coming to meetings reluctantly, armed with a load of cynicism and skepticism. Then after some time, something magical happens – things change to the better. Spring has arrived!

During those first months, at the beginning of the implementation, times are hard. People are struggling. And very soon you start to hear complaints and people telling you how great it was before all this. Before all this agile. When design documents were design documents. When they had time to work. Suddenly the past becomes a lost haven. In training, in coaching sessions, you hear people reminiscing about some glorious past.

The key to addressing these issues is to find out how exactly was it at those times.

“In the past, we had time to write thorough and in-depth designs!”: One of the first issues is how to move from big design documents (many times part of the contracting process with the client) to a more agile process. A good question to ask is whether those designs were actually implemented as is or were any changes made during development. Initial designs should still be made, of course, to see the big picture and set the path ahead, yet the focus is more on the conversation and less on a detailed document.

“What do you mean you did not meet your commitment? In the past, people would die to make it on time!”: Very fast, managers see that teams do not meet the sprint’s commitment, and questions about meeting the overall timeline start to surface. At first, you might get the (false) impression that when the waterfall was used, everything ended on time. This is usually not the case. Start asking how things really happened. Was everything working when they finished? Were any defects detected by the client? In addition, it should be noted that it takes time for a team to find out it how much it is that they can do in iteration. For that you need patience.

“How come everything breaks down on the first week of development? In the past at least the first few months were calm”: Agile brings up issues very early in the process, unlike the waterfall process, in which things surface late in the game. This early flood of issues raises a concern in management. This should be anticipated.

”Since we started this agile thing we are under constant pressure! In the past, we could bide our time”: As stated in the previous point, while in a waterfall there’s a long quiet time (before the chaos starts) in agile there should be (but that isn’t always the case) constant healthy pressure. If the pressure is not healthy, it is a good time to find out why. In addition, never forget that people need time to adapt to the change, and to think of the little tweaks they need to do to make it work. Being under heavy pressure is key to failure.

“Suddenly people are coming up with ideas about how we should do things, questioning decisions about what we do. In the past, we didn’t waste so much time on that!”: when the implementation goes well, you see oppressed people transforming into thinking people who care, people with ideas, which is good but changes the dynamics of the organization, specifically at lower ranks. This is something to discuss when starting the implementation.

”Product Owners? We don’t have the budget for that. We used to do just fine without it.”: Product owners were always there, hidden under the disguise of team leaders and experts (and sometimes, others). Someone always needs to make the requirements clearer – it is good to ask who did it and then uses it to explain why no new budget is required – it was part of what they did. If nobody did it, it was probably manifested in quality issues and someone should probably start doing it.

Making a change is always hard. Moving from waterfall to agile is a big change. Always remind people why they are doing this change and always help them to remember how it really was back in the good old days.

Subscribe for Email Updates:

Categories:

Tags:

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