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:

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