The Latest

Johanna Rothman recently wrote, commenting on Joshua Kerievsky's proposed definition of done. Both posts are worth a read, if for no other reason than to better understand why we have such a difficult time defining what "done" is, and why defining "done" is one of the major challenges for teams  trying to adopt agile practices.

Agile and ALM are two terms that you don’t often see side by side. To most developers, agile means team interaction, customer collaboration, dynamism, and responsiveness to change. In contrast, ALM seems to imply the opposite of agile, with echoes of rigid procedures, inflexibility, and top-down process control. But are the agile and ALM approaches as contradictory as they first appear to be?

Agile software development is designed to thrive within even the most dynamic business and technical environments. All agile methodologies include integrated practices and processes that manage evolving requirements to efficiently develop a continuous stream of new software capabilities. However, what Agile does not address are changes related to enterprise support that falls outside the scope of the project work. Enterprise Change Management (ECM) provides a framework that addresses many of these missing factors.

Mastering the “art” of adopting agile and lean software product development and delivery requires you to understand the science (technology) and the art (behavioral nuances) associated with this undertaking. This article focuses on how to make the cultural changes necessary for adoption and overcome general resistance to change in all of us.

Jim sat in his manager’s office about to have his 6-month review. His boss seemed to have that look on his face. A look he’d seen before.

“Jim, I’d like to say your work is outstanding, but while we’ve been pleased with your project outcomes, your approach to your work needs improvement.”

Jim squirmed in his seat and tried to prepare himself for what would probably mean another layoff.

A social experiment in the ‘80s found “Vandalism can occur anywhere once communal barriers are lowered by actions that seem to signal that 'no one cares.'" The same can be said for our software projects.

Agile teams need to analyze product requirements in enough detail to build, test, and deliver the right requirements in short time frames. For the many teams that struggle to define "just enough, just in time” requirements, here's help.