Viewing entries tagged
agile organizations

Revisiting Agile Teams

Comment

Revisiting Agile Teams

Revisiting Agile TeamsThis post is inspired by this article by Derek Huether - https://medium.com/@derekhuether/stable-teams-should-be-non-negotiable-59af0972f77

His is the sort of the position I used to have. However, I’ve been rethinking my position over the last few years. Not that I’m moving away from honoring the team. I’ll always do that. 

But I’ve started to think that a little adversity isn’t necessarily bad for a team.

I want to use this post as an update to my writings about agile teams. The following post best captures my thoughts – http://rgalen.com/agile-training-news/2018/3/5/stop-norming-performing

Back to Derek’s point

Derek makes 3 key points in the article:

  1. Teams that stay together are more productive.             (more stories)

  2. Teams that stay together are more predictable.             (higher throughput)

  3. Teams that say together are more responsive.               (less time in process)

And he supports those conclusions with data from Larry Maccherone while he was with Rally/CA and reviewing data collected through their tooling. Another key point Derek makes is against the frequent reorganizations that run rampant in many companies. That they undermine all three aspects.

I’m not going to challenge the data or Derek’s key point. Let’s assume that everything is right. That we want to focus on team productivity. However, I think there are things to consider equally (and perhaps even more importantly) than productivity.

Comment

Building Agile Teams – A Primer for Organizational Leaders

Comment

Building Agile Teams – A Primer for Organizational Leaders

I frequently get asked about the dynamics of building agile organizations from an organization structure point of view.

The most important point is that you don’t create a high-performance agile organization by the defined structure. Managers don’t do it; neither do VP’s or Directors.

Surely we set the stage. But the teams are the ones that create the organization. We don’t have to optimize the structure for every technical hurdle or risk. Or create a structure that perfectly balances skill-sets and experience across all functional roles.

Whew! I’m glad, because I never figured out how to do that perfectly anyway.

Comment