Back to List

20 Ways to Adapt Agile Best Practices to Remote Work

Rachael Wilterdink Rachael Wilterdink  |  
Mar 24, 2020
 
The author of our Basic and Advanced Agile Transformation eBooks shares how you can adapt agile best practices to enable your workforce to be effective working remotely from home, the beach, or anywhere in the world (with reliable internet).
 
With COVID-19 disrupting nearly every aspect of daily life, organizations across the United States (and the world) are scrambling to figure out how to handle remote working. I’ve been a consultant for many years, and I’ve almost never worked on a team that didn’t have some sort of remote component to it.
 
In this blog, I’ll share 20 helpful tips to adapt your agile environment to a virtual working world where you can still be successful.
 

1. Set up a work environment

Set up a comfortable and distraction-free environment to work in. Wear comfy clothes. Practice good ergonomics. Have good lighting, temperature controls, coffee, hydration, and anything else that you would find at your office desk (including a tub of jelly bellies or red vines).
 
Make sure you have all the same tools and capabilities that you would have if you were in an office building. Ensure you have reliable, high-speed internet. Use hard-wired connections versus wi-fi, if possible. If you normally work with dual monitors, make sure you have the same set-up at your remote location. Use a high-quality audio headset for calls.
 

2. Have a working agreement

When a team first forms, I always create a working agreement that the team members all agree to follow. This agreement is regularly revisited in the retrospective and, if adjustments are needed, they are made. The key is making sure that you’re all respecting the agreement that was made. This serves as a guide to the team to hold each other accountable if they’re not following the rules the team agreed to.
 

3. Establish overlapping working hours

Find a window of business working hours that overlaps, and plan for communication/meetings during these time periods. Everyone may need to adjust and be flexible.
 

4. Share your calendar

Make sure that all team members are aware of each other’s holidays and time off. These can cause real problems if you don’t consider them, and it’s important to plan for these non-working days.
 

5. Use tools to enable interaction

Leverage the amazing technology that exists to improve communication, including (but not limited to): video conferencing, audio conferencing, digital white-boarding, collaboration tools, instant messaging, or any other tools your team prefers (like these).
 

6. Prioritize face-to-face conversations

One of the original principles from the Agile Manifesto is to prioritize people and interactions over processes and tools. Face-to-face is always better than just audio, and face-to-face doesn’t necessarily mean in the same physical space. Turn on the video portion of your video-conferencing tools. This lets you see the facial expressions and body language of the other participants.
 

7. Be available

This is a hugely important aspect of remote working. Make sure your availability status is up to date in whatever collaboration tools you are using so people will know whether they can interrupt you or not. If you are not going to be available for a period of time during your shared working hours, let the team know in advance. If someone pings or calls you and you are available, respond! Don’t wait. This is equivalent to going over to someone’s cube and asking a question. You wouldn’t ignore someone if they were standing right in front of you; don’t do it digitally either.
 

8. Be present

One of my biggest pet peeves is people who think they can multi-task. There’s no such thing. A person can only truly focus on one cognitive task at a time. So don’t try to multi-task. It doesn’t work and it’s rude to your co-workers. Instead, pay attention when people are communicating, and actually listen in order to understand. Don’t make your co-workers repeat themselves and waste everyone else’s time because you weren’t tuned in to the conversation.
 

9. Be responsive

Even if you can’t answer someone right away, at least acknowledge that you received their message, and let them know when you’ll be able to respond. Communication involves sending and receiving, and if the sender doesn’t know their message has been received, they’ll be left hanging and frustrated.
 

10. Collaborate

Just because you’re working remotely doesn’t mean you are no longer able to collaborate. You can use collaboration software that lets you work on the same documents at the same time as others like Google docs or Microsoft O365. If you’re also on a call together at the same time, these can be very productive sessions. Don’t let your remote status prevent you from working closely with your colleagues.
 

11. Stick to your time-boxes

The events of Scrum are time-boxed for a reason, and this won’t change just because you are working remotely. In fact, it may even make your events run more quickly and efficiently since you can watch the clock while you’re meeting in a digital environment.
 

12. Record important sessions

Due to time zone differences and working schedules, it’s not always possible to have all relevant parties in attendance at important meetings. If your organization allows it, record those meetings and make them available for later viewing by additional stakeholders.
 

13. Avoid meetings on Fridays and/or Mondays (other than the daily Scrum)

Now, you should never skip the daily Scrum, but that’s not to say you can’t modify how you do it. The team I am on right now agreed to post the answers to the three Scrum questions on our collaboration tool on Fridays. It’s probably not as effective as meeting, but it’s an acceptable substitute.
 
Most agile teams I’ve worked on or coached have agreed to a rule that either Friday or Monday (or both) are no-meeting days (when possible). These are days that people tend to take off, and it allows the individual team members to have some dedicated focus time.
 

14. Allow for focus time

In a world run amok with meetings, it’s easy to end a day of work wondering if you did anything valuable that day. Providing for and encouraging focus time for individual team members is important. While collaboration is important, too, the most difficult cognitive work often requires concentration. If every day of the week is chopped up by meetings, it will be difficult to achieve the best results.
 

15. Be proactive

If you need something and it could potentially keep you from moving forward toward accomplishing the sprint goal, don’t wait to ask. Escalate anything that could be an impediment right away. There’s no good reason to wait until the next daily Scrum to express your needs. Your team is there to support you, so lean on them (even if you can’t literally lean on them).
 

16. Have a plan

Come to each meeting or event prepared with a plan but be flexible in applying it. Planning is important, but it’s more important to be responsive to the needs of others. You may even provide an agenda, but please recognize when it makes sense to stick to it versus engaging in valuable conversation about something that may not have been on the list.
 

17. Know your audience

If I’ve learned one key lesson about communication in my years of professional experience, it’s that you always need to consider who your audience is and adapt to their wants and needs. Some people like to keep the chit-chat to a minimum, while others are social butterflies who can’t stop talking. You need to understand where the other person is coming from and adapt your own style accordingly. As a consultant, I’ve worked with all kinds of people, and trust me, if you adapt yourself to your audience, you’ll have much greater success.
 

18. When in doubt, overcommunicate

It can be easy for something to get lost in translation using digital communication. More communication is better than no or low communication. If you’re unsure that something was understood by the recipient, seek confirmation or clarification to make sure they understand.
 

19. Streamline meetings, meetings and more meetings

Each of the Scrum events has a very specific, defined purpose. None of these meetings should be skipped, or you’re not really following Scrum. That said, if you want to reduce the stop/start cycle of multiple meetings, try to schedule your events back-to-back. If one ends early, you can roll right into the next one to be most efficient with everyone’s time. What you’re trying to avoid by scheduling meetings this way is context switching. Streamlining meetings will allow your team members to have less interruptions and more focus time.
 

20. Model your requirements

Don’t just write them. For most people (especially developers), pictures are preferable to words. Write your user stories, but when building out your acceptance criteria, make sure that you are including models along with the text. The models should support the written description and provide a holistic view of the requirements for the developer.
 
Modeling could come in the form of digital prototypes, data models, entity relationship diagrams, use case diagrams, context diagrams, flowcharts, data dictionaries, etc. (see my previous blogs on these modeling techniques). Whoever is responsible for creating the user stories and acceptance criteria should select the best models to clearly communicate the requirements.
 

You can be agile at home

As we all adapt to our changing environment, it doesn’t mean you have to stop working in an agile fashion. Anyone who can work remotely can drive their organizations’ missions forward from the comfort of their own home. All it takes is a little bit of adjustment, and it will almost be like you are still in the office.
 
Agile

 

Love our Blogs?

Sign up to get notified of new Skyline posts.

 


Related Content


Blog Article
Agile User Story Splitting by Data Variations and Boundaries
Rachael WilterdinkRachael Wilterdink  |  
Jul 07, 2020
In this blog series, Rachael Wilterdink (CBAP, PMI-PBA, PSM I, CSM) dives into 25 different techniques for approaching story splitting that she has used throughout her career. Make sure to stop by each week to catch all 25! This is a two-for-one special. Joking aside, data is another great way...
Blog Article
Agile User Story Splitting by Device, Platform, and Channel
Rachael WilterdinkRachael Wilterdink  |  
Jun 30, 2020
In this blog series, Rachael Wilterdink (CBAP, PMI-PBA, PSM I, CSM) dives into 25 different techniques for approaching story splitting that she has used throughout her career. Make sure to stop by each week to catch all 25! As I think we all know by now, there are countless possible combinations...
Blog Article
Agile User Story Splitting by Business Rules
Rachael WilterdinkRachael Wilterdink  |  
Jun 16, 2020
In this blog series, Rachael Wilterdink (CBAP, PMI-PBA, PSM I, CSM) dives into 25 different techniques for approaching story splitting that she has used throughout her career. Make sure to stop by each week to catch all 25! Before I dig into this story splitting technique, let me give you a...
Blog Article
Agile User Story Splitting by Acceptance Criteria & Test Cases
Rachael WilterdinkRachael Wilterdink  |  
Jun 09, 2020
In this blog series, Rachael Wilterdink (CBAP, PMI-PBA, PSM I, CSM) dives into 25 different techniques for approaching story splitting that she has used throughout her career. Make sure to stop by each week to catch all 25!   As I mentioned in one of my previous blogs in this series...
Blog Article
6 Real Truths About Project Leadership Learned from Trial & Error
Kari VondracekKari Vondracek  |  
Mar 17, 2020
About the author: Kari Vondracek (MBA, CSM, PMP, PSM I) is a project manager at Skyline Technologies. Since 1996 she has been leading projects in a variety of industries. When I was a young, know-it-all, 25-year-old, I was put into my first managerial position. I was a fresh college...