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:

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