We're hiring!

We're actively seeking designers and developers for all three of our locations.

Integrated Design and Development Backlogs

I’ve previously written about Atomic’s poly-skilled team approach and mentioned some of the related challenges from integrating design and development.

One challenge of integrating designers and developers into poly-skilled teams is the management of design and code related tasks. Atomic has tried working with both integrated and non-integrated backlogs.

On the myGRcitypoints project, we opted for an integrated backlog approach.

The integrated backlog approach was very useful for:

  • Designers and developers sharing responsibility on middle ground tasks like Information Architecture or CSS & HTML
  • Interleaving design and code tasks to expose dependencies and potential future bottlenecks
  • Having a single place to capture and manage the entire scope of the project

MyGRCityPoints Backlog

The above screen capture shows a portion of myGRCity Points integrated backlog.

We used a convention to identify tasks types:

  • D: General Design (sometimes abstracted tiny visual design and markup tasks)
  • C: General Code
  • X: Information Architecture and Interaction Design
  • M: CSS & HTML Markup
  • V: Visual Design

You can see how we staggered individual profile design tasks ahead of code tasks. Keeping design tasks ahead of code tasks reduces scrap and rework effort. The team tried to subordinate themselves to working in a design first manner as much as possible.

The team decided who would work on what tasks depending on skill sets, strengths and dependencies. If we had a glut of V tasks, the coders would help give support in X & M tasks. If we were getting bottlenecked on C tasks, the team designer would do more work in X & M tasks.

Integrating a backlog with design and development tasks gives rise to other project management considerations about scope and velocity tracking. We maintained an integrated burn chart that included total team velocity and total backlog scope. We kept the burn chart integrated due to consistent team member allocation. Not all projects should take the same approach.

In the future, I’ll be posting more observations about benefits realized from the integrated backlog approach and related project management techniques.

Shawn Crowley (53 Posts)

Shawn is a Vice President of Atomic Object and works in Atomic’s Grand Rapids office. Shawn is involved Atomic’s pre-project consulting work and helps clients understand how Atomic can develop their next product. Shawn is involved in operational management, growth initiatives, and the maturation of Atomic’s deep integration of design and development practices.

This entry was posted in Project & Team Management and tagged , , . Bookmark the permalink. Both comments and trackbacks are currently closed.


  1. João Nelas
    Posted July 28, 2011 at 7:10 am

    What software do you use to track the backlog?

  2. Shawn Crowley
    Posted July 28, 2011 at 10:22 am

    Thanks for your comment Mark. You are correct, we use a customized version of strac.

    There are many other great tools available. We like strac because we can modify it (hack the source code) to suit our needs when we want to tweak our process.

2 Trackbacks

  1. [...] Shawn Crowley | Published: August 28, 2011 During the myGRcitypoints project we used a backlog that integrated design and development tasks. To minimize rework, we strived to complete design and markup tasks before writing the related [...]

  2. By Balanced Team Conference 2011 | Atomic Spin on September 26, 2011 at 10:56 pm

    [...] Balanced Team group.My presentation tied together several blog posts I’ve recently written.Integrated Design and Development BacklogsManaging agile, Poly-skilled Teams with Intermediate MilestonesThe conference organizers have done a [...]