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:

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