Over a million developers have joined DZone.

How to Kick Off Your Agile Transition: Part IV

Stephan Wolpers explains why investing in a workspace that promotes Agile culture is important in your Agile transition.

· Agile Zone

Reduce testing time & get feedback faster through automation. Read the Benefits of Parallel Testing, brought to you in partnership with Sauce Labs.

If you want your organization to become Agile, adding more whiteboards to the workplace will not suffice. You have to abandon the idea that the workspace is an assembly line for white-collar workers. You need to let go Taylorism. We are now in the age of the creative worker.

To become Agile and reap its benefits, such as becoming more innovative, you need a diversity of workspaces to support all forms of creative work: focus, collaborate, learn, and socialize. Also, you have to let your creative workers choose which space is best suited for a task. 

The Agile Workspace: A Worthwhile Investment

Why would you spend time and money on creating a diverse workspace in the first place? Because creating it is a sound investment decision. 

Based on their proprietary Workplace Performance Index methodology, Gensler’s 2016 U.S. Workplace Survey uncovers "a statistical link between the quality and functional make-up of the workplace and the level of innovation employees ascribe to their companies." 

(c) Gensler WPS survey results 2016

SourceGensler

In other words: If your organization is trying to become Agile without investing in the workspace, it may realize a lesser return on investment. It may also fall behind a competitor that has invested in a diverse workspace for its creative workers.

Agile Workspace Anti-Patterns

Let’s have a look at some issues in workspace design that contradict the needs of the creative worker:

  • Open floor plans. These are often considered to be the ideal Agile workspace as they nurture collaboration and help spread news and information, thus keeping everyone in the loop. However, a lot of creative workers feel that their need for focus and deep work is challenged by the noise and sound level that often accompanies open floor plans. (Read more: Just shut up and let your devs concentrate, advises Stack Overflow CEO Joel Spolsky.) 
  • Having to grab a new desk every morning. This bean counter brainchild is toxic for collaboration among members of agile teams. The policy is likely to scatter a team all over the place instead of co-locating it. It also deprives everyone of an important part of the psychological safety net – an individual desk – that fosters trust building and collaboration among team members.

Scarce availability of whiteboards. Most walls within the workspace of an Agile organization should be by default whiteboards to encourage instant collaboration. Glass or brick walls may be aesthetically pleasing but will impede the agile transition as they prohibit spontaneous collaboration.

Agile workspace: the importance of whiteboards – Age of ProductSource: Adrian Kerry

Team members who prefer working from home are a good indicator that your workspace is not up to the Agile job. Those team members are by no means unfit for Agile (team) work. They probably just need to get deep work done that they cannot accomplish in the office. 

Another indicator for an unsuitable workspace is the widespread use of hearing protection devices or headphones by team members.

Being Agile Requires a Diversity of Workspaces

To become Agile, your organization needs a diversity of workspaces to support all forms of creative work: focus, collaborate, learn, and socialize:

  1. Agile requires a large, flexible space for trainings and public ceremonies (i.e., Sprint reviews and workshops). If you want to run user story mapping workshops with ten of your stakeholders, for example, you will need at least 10 meters (or 30 feet) of whiteboard space. (Rule of thumb: one meter per workshop participant.) 
  2. Form follows function. A stylish office may please the eye but does not necessarily satisfy the needs of the creative worker.Agile workspace: Stylish but hardly usable work space – Age of Product
  3.  Agile teams require defined team spaces to create a sense of togetherness, not just any area within an open space.
  4. Agile requires space for collaborating in small teams of two to maybe five or six people.
  5. Agile requires silent workspace to for deep, focused work.
  6. Agile requires space for informal, ad hoc meetings of two to three people.
  7. Agile requires social spaces, i.e., cafés, that encourage informal networking. Cafés provide the serendipity of meeting someone interesting unexpectedly.
  8. Being Agile also requires a budget for regular offsite events such as workshops to support pushing people gently out of their comfort zone. Familiar settings become less stimulating for innovation over time. Utilize the hardwired (sabre-toothed tiger-driven) need of humans to be more alert in unfamiliar places to your advantage.

How can a great Agile workspace be created? 

You create a great Agile workspace by including the teams as early in the planning process as possible. Don’t just present the concepts from architects or interior designers; live up to valued Agile principles such as transparency, interaction, and inclusion when your organization is designing an Agile workspace.

Conclusion

Transitioning to an Agile organization requires changing the available workspace in most cases. Buying a few additional whiteboards won’t get the job done.

Becoming Agile requires an environment that fosters all four forms of creative work: focus, collaborate, learn, and socialize. It should be up to the creative worker to choose the right space for each task. 

Last, but not least: Include your teams when designing an Agile workspace. People care about what they help create.

What changes to your workspace did you make during your transition to an Agile organization? Please share with us in the comments.

The Agile Zone is brought to you in partnership with Sauce Labs. Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure.

Topics:
agile adoption ,work culture ,agile

Published at DZone with permission of Stefan Wolpers, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}