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:

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