Remembering My First Scrum Team Common Area Experience.

When I first heard about common areas for teams to work I have to admit I wasn’t too keen on the idea. I wanted my own space and privacy which I had come accustom to. I also thought that there would be too many distractions that would negatively affect my productivity. Most engineers I worked with at the time felt the same way. It wasn’t too long after that I would find myself working with a new team that worked in a common area. It was definitely a bit uncomfortable at first as I was new to the team and I would be spending the majority of my day with them working on our sprint deliverables. Much to my surprise, it turned out to be a very positive experience. I was able to bond quickly with the team and contribute right a way. I believe working in the common area was a big reason for that. There was quite a bit of collaboration on a daily basis as we worked through our tasks, their integration and testing. And the distractions I was so worried about, didn’t really happen and when they did, they were good distractions. Meaning, they were necessary for the team’s sprint success. Whether it was answering questions about design or helping with a weird compile error, it ultimately went towards achieving our team goals. And isn’t that what its all about? So if you have reservations about working in common areas, I get it, but I do recommend giving it a chance if you have the opportunity. Your experience may be as positive as mine.

What are your thoughts on common areas? Any good or bad experiences? Feel free to share in the comments below.