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

COVID-19 and Agile

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

A fresh perspective on uncertainty, complexity, empiricism, and flow and what to do about it.

The COVID-19 pandemic gives us plenty of opportunities to think about uncertainty, and complexity, and how to deal with those using Empiricism.

When it comes to our work in Agile teams and organizations, the first thing we need to acknowledge is that the first thing that happened to most of us is that we tumbled all the way down from Maslow’s hierarchy of needs top levels down to the bottom – to our physiological needs. At the time we’re hoarding Toilet paper is probably not the right time to talk about Self-actualization and esteem or Mastery and Purpose if you want to use Dan Pink’s intrinsic motivation model.

Maslow's hierarchy of needs - Wikipedia

In parallel to this tumble, many of us were still expected to continue with the business as usual of running Sprints and Program Increments. Some of us were even expected to adjust courses to help our organizations deal with the impact of COVID-19. After all – this is what business agility is about isn’t it?

When I ask my students, clients, and friends in the agile community, the majority say that the importance of agility has gone up significantly, while actually being agile has become harder due to the physical distancing we’re all facing combined with additional responsibilities at home we have to juggle.

I find that the first step towards dealing with this new reality is acknowledging it. A tool I like to use to acknowledge uncertainty and complexity around WHAT we should build and HOW to do it is the Stacey Matrix.

Current times bring to the front a somewhat neglected axis of the model – WHO are the people on our team/group and what kind of interactions are they having? If the WHAT/HOW dimensions range from simple/known all the way to uncertainty and lack of agreement, when we look at the WHO aspect it’s about how effective are the interactions between the people. You could look at it as how far along the Tuckman model (Forming, Storming, Norming, Performing) they are. Drawing the three-axis it kind of looks like an uncertainty spider/radar.

Many of my clients are facing increased uncertainty around WHAT to build. All of them are facing teams, groups, and ARTs that are back to Storming or even Forming from a team/group dynamics perspective because so much has changed in how they collaborate.

Moving from in-person interactions when you can have a certain level of focus throughout the work day to the limited communication bandwidth we’re getting when physically distant from our teammates combined with some challenges focusing, mean our implicit/explicit rules of engagement/working agreements aren’t necessarily working well for us anymore.

So what can we do? You can start by making this reality transparent. Talk about the uncertainty spider and its dimensions with your team. Self-assess where you were before the pandemic and where you are right now. Start a discussion about what to do about the differences/changes you’re facing.

Some concrete steps I’m seeing teams take are to run a team health self-assessment, discuss adjusted working agreements for a work-from-home environment, re-evaluate forecasts/commitments – e.g. by taking another confidence vote with the entire team (or Agile Release Train) and replan as appropriate.

Generally, historical velocity is even less predictive during this significant shift in how we work. YMMV (Your Mileage May Vary) definitely applies. Some teams take on less work into their Sprint and pull in more work if they see they’re doing ok.

Some teams see so much volatility in their Product Backlog that they shorten their Sprint Length because planning too far in advance doesn’t make sense.

Other teams focus on Goals for their Sprint rather than a detailed Sprint Backlog. (Teams I’m working with that are leveraging Kanban/Flow practices are more likely to think this way by the way).

Teams aware of their WIP (Work in Process) are starting to see the bigger picture of everything that is in the process – not just the work on the team but also whatever’s going on at home and in life in general. When they do that they realize that it might make sense to reduce the WIP because we’re suddenly juggling more things while working.

The Daily Scrum becomes more important for many teams because they’re not sitting next to each other anymore and they lack the natural osmosis that happens in a team space. Some teams have multiple Scrums a day. Other teams set up an ongoing live video conference while they’re working individually which reduces the overhead of reaching out to team members and allows for a fun vibe of togetherness. Other teams use real-time chat rooms like Slack or MS Teams for this. Virtual Happy Hours. Watercooler Zooms.

Are all of these good ideas? Many of them will probably turn out to be good practices in the right context.

The important thing is that these agile practitioners acknowledge that things are different and that even during these stressful times and maybe especially during these times it is important to use an empiric process of seeing what works, and what doesn’t, inspecting and adapting while keeping the spirit of collaboration, transparency, empiricism, and flow in mind.

Subscribe for Email Updates:

Categories:

Tags:

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