Tue 18 May 2010
5 Questions About Agile with Gear Stream’s Brad Murphy
Brad Murphy, CEO of Gear Stream, gave a keynote presentation at last week’s Agile Success Tour. Brad’s vision includes helping organizations transition from project-driven governance to Lean, continuous flow, product line execution. We sat down with Brad to ask him 5 questions about Agile. 
1. What’s the most valuable thing you’ve learned by helping organizations adopt Agile practices?
The dynamics surrounding the adoption of Agile practices are changing in ways that are very different from even two or three years ago. In parallel with implementing Agile practices and establishing effective Agile teams, we’re helping organizations connect Agile philosophies and values to vital stakeholder groups. We’ve recognized that actively involving all stakeholders early in the process is key to ensuring that core Agile teams are able to achieve expected results. Gaining the support of all collaborators in the organization dramatically helps core Agile teams successfully transform and deliver outcomes. Involving the following stakeholders is vital, including:
- The core Agile team
- Tooling, Infrastructure and Release Management – the architecture side of the equation.
- Governance and PMO groups – more than half the time, this group builds the roles of the project managers, Agile teams and the Scrum Master. They consider how Agile teams work off backlogs. There’s huge potential for misalignment here.
- Product Management – since this is frequently a group that doesn’t exist, the responsibilities here aren’t well defined. Loosely, I’ll describe this as a group of individuals responsible for defining business value. This group has to be aligned with the way Agile works.
- Executive Management – all of the focus on Agile change with the groups listed above must be explicitly aligned with the strategy and values articulated by senior executives. Too often, Agile is pursued based on “generic” benefits like speed, responsiveness, quality… while these are “good,” they’re not explicit enough. We must challenge executives to express exactly how they will measure/recognize their own corporate goals and then map these back to the things we choose to emphasize in an Agile transformation.
Responsiveness would be #1. Having the ability to course-correct and change directions quickly in light of new mandates and directions. A close #2 is innovation. A distant #3 is productivity.
Gear Stream’s clients are realizing compelling organizational realignment by refocusing the entire value chain on external customers, as opposed to the often dysfunctional inward focus of many organizations. By aligning the entire value chain on external customers, our clients are able to more predictably influence customer satisfaction and marketshare objectives.
I’ll give the advice I’m most passionate about. Agile teams need to challenge the rest of the organization to rethink and reconsider how work happens up and down-stream to them in order to fully exploit what they’re capable of achieving. It’s really about how Agile teams can actively promote, influence and change an organization beyond just what they do as a team. They really can – and do – influence and engage the rest of the organization. The failure pattern of Agile is almost always the same: we’ve built an Agile team, but failed to build the adjacent stakeholder teams in the process – then, the Agile team gets frustrated and the organization loses momentum and enthusiasm for Agile. Agile teams must have the ability to influence stakeholder teams, and ultimately, the baseline infrastructure of the entire organization.
5. How do you define Agile success? (Can you do it in 113 characters?)
Building, delivering & sustaining outcomes that customers r continually thrilled by, driving profit & value 4 all


[...] This post was mentioned on Twitter by Agile Blog, MKinside. MKinside said: Looking at: 5 Questions About Agile with Gear Stream’s Brad Murphy http://bit.ly/bS76la [...]
Great to hear Gear Stream is helping clients to orient themselves towards the value delivered to the external customer – the true value stream.
I’ve come across many in the community who fail to “see the whole”; instead, directing efforts towards improving internal responsiveness. Often, this approach is justified with the “we’re (or they’re) not a product/software company” excuse. Unfortunately, these organizations/individuals are limiting the potential and heading down the wrong path.
In my view, this unfortunate practice is perhaps the greatest sub-optimization plaguing the Agile community. In order to fully realize the benefits, organizations seeking to achieve agility should put the concept of an internal customer to rest and instead focus on building collaborative PARTNERSHIPS with all stakeholders/contributors in an effort to deliver real value to real customers.
Brad, your comment about “putting the concept of an internal customer to rest” really resonates with me…
As we work with larger clients seeking to “go Agile”, it’s interesting and sobering to go across the stakeholder community (including the core development teams) and ask simple questions like:
“how are the priorities of your team directly impacting and enhancing the value you’re working to produce for external customers”
“do you know who your customers, customer is?… If so, do you know how they define value?”
“how is your team actively partnering with other stakeholder groups to help them achieve better outcomes for customers”
It’s not surprising that that the answers are often defocused, rambling or simply “I don’t know”.
Despite the “local focus” emphasis of many Agile initiatives, I’m encouraged by the tension good Agile teams often create inside larger companies… it is this tension that affords us the opportunity to engage the enterprise in a broader conversation about the need to reshape the organization and re-imagine what is possible.
Brad,
This is great! I really enjoyed learning more about your experiences and Agile expertise while presenting at the recent Agile Executive Forum in New York City. I value your perspective that Agile has the ability to help the rest of the organization evaluate how it works. That fits nicely in my systems thinking world, “Seeing the Whole”. I so agree with you that Agile creates that “unintended consequence” (in a very positive use of this system archetype) of evaluating upstream and downstream processes that can impact or are impacted by the Agile adoption.
Thanks for a great guest blog!
Jean