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:

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