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:

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