More Effective Daily Scrums with the TFS 2012 Task Board

Some of my favorite new features in TFS 2012 are the significant improvements to the TFS web client. Sprint planning and execution has never been easier - especially for remote teams - when using the new team task board in TFS 2012.

###The Perfect World### I have been working with a remote team for the last two years and our biggest challenge has always been communication - especially because everyone is remote, not just one or two individuals. The Daily Scrum helps keep the communication lines flowing for the team at the beginning of each day. Being part of a remote team, this is usually handled with an audio conference bridge. And more often than not, it’s challenging to form a good understanding of what each team member is actively working on.

In a perfect world, if we were all colocated, this wouldn’t be an issue - the development team would reap the benefits of standing together as a group for our Daily Scrum, gathered in the same room, most likely in front of a physical task board used to track work throughout the sprint. Everyone would be able to identify what work has been completed, what is in progress, and what is remaining. We could even plot our own burndown on the white board to gauge if we will finish on time.

###Reality### Unfortunately, the colocated Daily Scrum isn’t an option for us, but the next best thing is for the team to review the new team task board together. The team task board, which ships with both Team Foundation Server 2012 and TF Service, is a virtual representation of the physical task board used by colocated teams. Virtual sticky notes can be moved from one swim lane to another, while updating the affected work items behind the scenes.
**Bonus: Have a touch-enabled desktop or Windows 8 tablet? The task board supports touch events, allowing users to drag virtual stickies from one swim lane to the next. **

TFS 2012 Task Board

Simply reviewing the task board together as a team on a daily basis not only helped ensure everyone was actively working on what we committed to at the beginning of the sprint, but also helped everyone on the team form a shared understanding of what each team member is working on and how that work fits into the team’s overall sprint goals. Team collaboration and communication for the win.

Related Posts

There Are No Problems, There Are No Challenges

The Ruby Koans Are Still Awesome

CSS3 Child Pseudo-Selectors: How To Single Out the Special Children

If We Aren't Focusing on Shipping, Then What The Hell Are We Doing?

CodeStock 2013 - Conference Wrap Up

CodeStock 2013 - Agile Retrospectives for High Performing Teams

Visual Studio 2012 Application Lifecycle Management Virtual Machine & Labs with VirtualBox

Organizing Your TFS Build Definitions with Inmeta Build Explorer

Webinar: Continuous Deployment with Team Build and MSDeploy

Heterogeneous Development with Team Foundation and Visual Studio 2010