New enterprise agile blog at

As if it wasn’t obvious from its name, my blog is dedicated to the challenges of agility at scale, and I try to stay focused on that space because that is where so many of the challenges and so many of the potential benefits of agile adoption lie. Of course, it’s often a mix of team and enterprise practices, because if something doesn’t work for the team, it doesn’t work for the enterprise. And if there’s an impediment in the enterprise, then agile probably doesn’t work well for the team, which doesn’t work for the enterprise, and well, you get the idea, it’s always a mix.

In any case, I’ve been aware of a new blog devoted to enterprise challenges that some people I know have been working on. It’s at Here’s an intro:

“Agile Juice is a blog dedicated to the advancement of software agility. We’re experienced agile advocates in the Telecom / Cable software industry. With the help of others throughout the software industry, we have learned a ton and in the process, have been successful at leveraging agile best practices to deliver enterprise scale BSS and OOS software of high value in within reduced timeframes. It’s now our turn to give back to the community. For the bulk of our careers, our agile experiences have been centered on development shops of 30 folks or less. However, that has recently changed and over the past year, we have transformed a 100+ resource development shop into a synchronized agile release train that operates in concurrent and parallel 2 week iterations.”

I know these guys pretty well and their recent experiences have a lot to contribute to our growing pile of intellectual property and best practices of agile at scale. Their latest post (If you see the spotlight, don’t ignore it) points out one of the challenges with agile – if an individual can’t keep pace with the intensity of the quality software delivery process – then that can be a big and immediate cultural challenge for the enterprise.Here’s a quote that should tweak your interest:

“What if it’s customary to give average performers second, third and even fourth chances? In the agile world, you are dead.”

I suspect you’ll find it interesting reading, so I’ve added them to my blogroll.