Being Agile in a ROWEnvironment

It has been almost seven years since I started working at Edmunds.com and the last 18 months of it was spent doing Project Management. One of the unique responsibilities as an Edmunds’ project manager was to be a consulting Agile coach. This meant that my team and I coached Agile software development in both Scrum/Kanban format for development teams that were struggling to manage their workload, teams that just need a few pointers, and everything else in between. Since the adoption, we’ve iterated our way to success, and made it ours by becoming truly Agile.

Agile was already deeply integrated into Edmunds project culture when leadership in the company started to really focus on creating the best possible work/life balance experience. This is when we were introduced to a culture shift called ROWE (Results-Only Work Environment). This change came with a set of principles when summed up in one sentence was: “Work whenever you want, wherever you want, as long as the work gets done.” While this may seem like a great idea for everyone, those who are familiar with Agile development that haven’t heard of ROWE might already be asking a few questions. As a seasoned Agile coach, I had to be detailed about this adoption, but the devil in the details was much bigger than I thought.

ROWE and Agile development by definition have a few contradicting principles:

Agile: The most effective form of communication is face-to-face.
ROWE: Work wherever and whenever you want.

Agile: Business people and developers must work together daily throughout the project.
ROWE: Work wherever and whenever you want.

Agile: At regular intervals the team reflects on how to become more effective then tunes and adjusts the behavior accordingly.
ROWE: Work wherever and whenever you want.

While the comparison of principles are meant to be (somewhat) humorous, there is a superficial theme that emerges:

Agile methodology encourages teamwork, while ROWE would seem to emphasize individual results.

What is often missed in the ROWE strategy, is the “R” for “Results”. I have seen time and time again where folks in the team won’t see eye-to-eye on what it means to deliver results. There are principles in ROWE like “all meetings are optional”, that make a lot of folks forget about results. While it may seem like this is not going to work out, the main point - when understood correctly - makes it all come together:

“We win and lose as a team”

The principles in ROWE, while it may seem so, never encourages individualism. ROWE, in textbook terms, is an environment in which the emphasis is on the actual work done. How or when that work is accomplished is less important (source WhatIs.com). It makes perfect sense in an Agile community as long as we understand the aforementioned point. Yes, this requires some bending of the principles, but Agile - like the name - requires us to adapt quickly to any given situation. While these two working styles may seem counter-productive, both cultures will encourage you to be:

  1. Proactive - take ownership of your own work
  2. An adult - gives you responsibility and holds you accountable
  3. Communicative - requires you to actually talk to your teammates

Below are some of the guidelines for ROWE principles and how we made it work for us

ROWE principles Edmunds guidelines
People at all levels stop doing any activity that is a waste of their time, the customer’s time, or the company’s time Think about your actions and assess whether or not this is something that will benefit the company and/or your personal development
Employees have the freedom to work any way they want Don’t work only when it’s convenient for you. Work together, win together
Work isn’t a place you go, it’s something you do. “R” in ROWE is for “Results”, not “Remote”. If it’s proven that being in the office to achieve best results, you should be there when necessary
Every meeting is optional Think about whether or not attending a meeting will help you drive results, and make the right choice
There are no work schedules Be an adult about when you work. Communicate, collaborate, participate.
No judgement on how you spend your time Let others know that you will be unreachable, and have a backup plan for time-sensitive issues

We iterated again and again in short intervals until we got it right. Being in a constant “beta” stage made us work out our differences and built even more trust in the team. We saw people happily sacrificing their own time for the greater good of the team. These good deeds were reciprocated with gratitude and trust, not a continued increase in workload. Much of our petty arguments or debates to posture and prove “rightness” fell to the wayside in the collective interest of achieving the expected result because we truly valued this freedom. We achieved success by understanding and fully embracing the true purpose of each culture. This gave us a whole new meaning to agility in being Agile. Most importantly, we understood our own environment and made Agile + ROWE something unique to Edmunds through great cohesion and teamwork.

Shawn Kim has been driving with Edmunds for more than six years, originally as a data developer, then as a technical project manager. He enjoys various outdoor activities including snowboarding, surfing, biking, and golfing. He works on many different areas of the organization as an Agile coach, innovation manager, and PMO strategist.

What drives us?

At Edmunds we’re not just about making car buying easier, we're also passionate about technology!

As with any website that has millions of unique visitors, it's a necessity that we maintain a scalable and highly-available infrastructure with reliable services.

We are excited by software design and strive to create engaging exper-iences while using coding practices that promote streamlined website production and experimentation. We embrace continuous delivery, dev ops, and are constantly improving our processes so we can stay lean and innovative. We also prioritize giving back to the community by providing open APIs for our auto-motive data and open sourcing projects whenever possible.

Recent Posts

  1. An IT Director’s Perspective on Troubleshooting
  2. Find Your Inspiration and Start Coding
  3. Being Agile in a ROWEnvironment
  4. Is Migrating to the Cloud a Financial Win for Your Company?
  5. Self-Governing Code - Using Static Analysis and Automated Testing to Eliminate Word-of-Mouth Standards
  6. The Unexpected Bonuses of Microbonuses
  7. Edmunds.com Expands Automotive Accelerator Program with Announcement of 2015
  8. Creating Innovation Paths at Edmunds
  9. Buying a Car is as Easy as a Conversation at Edmunds.com
  10. The Edmunds Revolution - One of Top 7 Best Technology Places to Work in LA
  11. Edmunds.com Updates Mobile Car Shopping App with Cutting-Edge Messaging Platform
  12. Academia and Industry Team Up to Give College Students Big Data during Annual DataFest Competition
  13. Building a Data Warehouse for Business Analytics using Spark SQL - Spark Summit 2015