If you're practicing agile methods but continue to reach back to the rules and structures your organization used before adopting agile, you might be asking for more trouble than you know. In this article, George Schlitz discusses the mingling of old and new rules in organizations in different phases of agile adoption and offers a four-step method to help sort out the confusion.

Project management has contributed diverse triangles as it has evolved. From the traditional project triangle to the agile inverted triangle and, recently, the agile triangle. In this article, I am proposing going one step beyond the agile triangle by taking into consideration lean thinking to add a fourth element, specifically that of design, to form the lean-agile prism.

Estimating Projects give people the fits. On one hand, you have to know when things are going to get done and how much they are going to cost. On the other hand, estimating projects looks a lot like magic from the outside.

I've been successfully estimating and teaching people how to estimate projects for a long time, and if you’ve read Part 1 in this series, you're ready for some tips and tricks of estimating.

By putting more effort into fixing time, rather than functionality, agile development projects are able to reach the levels of agility they were intended to reach. By welcoming change, as agile was designed to do, you're able to create an innovation cadence keeps everything in harmony.