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:

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