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:

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