Transparent Project Management with Burn Up Charts

Uncertainty is inherent to software development — it’s impossible to precisely predict how long individual tasks will take. And that makes it very difficult to manage software projects using traditional project management tools. Bottom-up estimates and Gantt timelines created before a project starts are helpful for setting initial milestones and budgets. But once development is […]

Evolution of a Burn Chart

Burn charts have been a staple of Atomic-run projects for quite a while. They’ve also been the subject of much discussion both internally at Atomic and at-large in the Agile development community. The basic concepts are simple, and we’ve found them useful — especially when they are allowed to evolve as we learn how to […]

Pitfalls of Integrated Design and Development Burn Charts

When managing a software project that has both design and development scope, I have come to prefer using an integrated backlog of tasks and separate burn charts to track design and development efforts. Atomic continuously experiments with project management practices that help our poly-skilled teams manage their efforts and predictably deliver custom software products. I’ve […]

Moving Beyond Story Points, Iterations, and Burn Charts

If your team is not focused on delivering intermediate project milestones, they are missing what’s really of value. It’s easy to miss the forest for the trees if you’re only focusing on task-level points estimates and velocity tracking. I’ve become frustrated with how burn charts focus on showing progress through an entire backlog and don’t […]

Atomic Burn Charts

At Atomic, burn charts are an important component of our project management practices. A Burn chart is a high-level visual indicator that reveals project progress over time. Generating these charts at regular intervals provides key insights for both the business customer and the development team. Some of these insights include: Confidence about delivery dates Confidence […]

Breaking Down Epic Stories

A couple of years ago I wrote about how I was using Epic stories for early project estimations. Recently John Rusk posted a question in the comments: I have a question about this: “We make no attempt to restrict that the total number of points from the resulting stories adds up to the previous estimate […]