Archive for the ‘Agile Culture’ Category

Balanced Metrics for Agile Enterprises – Net Promoter Score @ Rally

Wednesday, September 15th, 2010

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Original Post by Ryan Martens

Believe it or not, we talk about metrics here all the time. I bet it is the same around your near real-time, software-driven enterprise too. For Agile teams, the pursuit of good metrics and forms of feedback to steer their work is an obsession. I swear we have as many “quants” in this company as engineers, service or sales professionals.

At Rally, we currently track four categories of metrics in a kind of balanced score card of SMART numbers:

  • Employee satisfaction (see Colorado Best Company and Outside Magazine); We also use an on-demand 360-degree peer review system
  • Value Throughput (% of value demand versus failure demand, work in process, cycle time, services backlog and lead time, along with any awards and/or positive reviews)
  • Financial (Lifetime value of customer, cost of sales, breakeven point, bookings growth, renewals %, cash)
  • Current Customer Satisfaction (Control charts of cases and escalated cases normalized by user base)

NPS as part of your Agile Metrics

We are about to start measuring a new number – NPS. Ever since Tom Poppendieck exposed me to the Fred Reichheld’s book on Net Promoter Score back in 2006, I have been interested to see how a powerful tool like this could be applied to Rally.

The theory behind Net Promoter Score is, as the book’s title says, “The Ultimate Question”  – measuring customer satisfaction. On Wikipedia, you can see the criticism of this measure versus other questions, but I really like the rigor and material available behind this approach. You can find success stories, along with blogs, additional resources and information about what makes up a good NPS on the NetPromoter.com web site. Of course, Net Promoter is just one of a balanced set of metrics to help understand performance, improvement and stakeholder value. We see NPS as an increase in discipline around customer satisfaction measures. For an Agile enterprise, those end-of-pipe measures become a great predictor of future financial performance and growth.

Iteration One of NPS at Rally

We decided it was time to measure NPS at Rally due to four factors:

  • our recent growth in staff, due to financing in late 2009
  • success in moving other customer metrics this year
  • the search for an over-arching metric around customer satisfaction
  • increased sophistication and capabilities in our IT environment and belief that the feedback can help prioritize strategic work for 2011

Our team started this effort as a skunk works out of IT. Once we completed our first iteration and understood how we would need to scale NPS, our IT team prototyped a solution in and between our instance of Salesforce and Eloqua. We then expanded the team to include support, customer advocacy and marketing. This team’s first goal was to get smarter by reaching out to other friendly SaaS vendors we work with who had implemented NPS. We are extremely grateful for the time that Nadia De Villa of Eloqua and Susan Gingrich of Readytalk spent with us to share their experiences. (This Readytalk blog post led us to Susan.)

The first phase of our NPS survey will go out this week. If you are one of the randomly selected customers who receive it, please take the 30 seconds needed to respond.

Our super-short survey will take maybe 30 seconds to complete.


We are eager to hear your feedback and ready to adjust things as necessary. If you can’t wait for our survey, please feel free to comment on this post or send me an email: ryan.a.martens@rallydev.com. We really want your feedback as we are trying to be a GREAT company.

Since NPS only measures customer satisfaction and we have to balance a portfolio of stakeholders, I am sure this will not become the one or “ultimate” number for the company. But, I am confident that this will become a part of the weekly corporate dashboard. If this is an interesting topic for folks, let me know and I will post follow-ups in the future. We would also love to hear about the experience of your team or company with NPS.


Ryan Martens is a tomato canner, school board member at Friend School Boulder, and CTO at Rally Software Development.



Ryan Martens original post

Rally in Raleigh; Success in becoming a Whole Cupcake?

Tuesday, September 7th, 2010

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Original Post by Ryan Martens

Did you know that some people pronounce Rally and Raleigh the same?  It is also a tongue twister to say them together.  These are two of the more esoteric things I have learned in the eighteen months following our acquisition of 6th Sense Analytics.

fivefingersRaliegh

Five Fingers for a great Q2 and great North Caroline BBQ

This is in the forefront of my mind following a recent trip to Rally’s Raleigh-Durham, North Carolina office. After Agile 2010 in Orlando, Jean Tabaka and I visited our largest remote office in their new digs.  We were there to help share in their Q2 Celebration event.   It was a real pleasure to see that office filling out and becoming whole.  (more on the cupcake thing below)

Becoming whole is so critical for a remote office and for an Agile team.

When I was working at BEA, I was part of an amazing machine that really knew how to acquire companies.  BEA learned from Cisco about how to do this right and how to balance autonomy and culture to create a healthy soul for an office away from the corporate headquarters.  Typically, BEA moved one or two folks to the remote facility to become active managers and help provide local leadership. These embedded people helped make the transition smoother by transferring norms, values and informal networks of the existing organization to the newly acquired team.  In fact, BEA would not move forward with an acquisition deal unless it had management bench strength who were willing to move and play that role.

We compensated without management bench strength.

In Rally’s case, we did not have that management bench strength to move folks from Boulder to Raleigh. As a result, we lived through what some folks on the team called “open wheel racing.”  We had a lot of rubbing and bumping.  We struggled as Boulder team and Raleigh team tried to figure out the balance between autonomy and culture. And we were tackling this cultural bumping while working collaboratively on the same product and sometimes in the same code-base.

We knew we had to address the lack of local leaders from corporate and so we started with 3 specific practices:

  1. We stuck with eight-week agile release cycles. This frequent synchronization really helped keep the wheels on both cars.  To help jump start real collaboration for the releases, the Raleigh team flew out to Boulder for most of the release planning meetings in 2009.
  2. Within the releases, we chose to develop a vast majority of the Raleigh code as a separate service running in separate application containers. This supported the Raleigh team having almost complete ownership of the functional value they delivered.
  3. We added HD Video conferencing to support frequent meetings and open worm-holes to broaden communication channels beyond emails, IM, and phone calls.

Our next steps brought in additional agile team members.

Since the acquisition of 6th Sense in late 2008, we had a only a partial agile team in Raleigh.  To complete the team, we added a development team lead and a product owner in Boulder.   In 2009, the Raleigh team released Rally’s customized reporting service and time-tracking capabilities.  Todd Olson’s ability to lead the Raleigh team in collaborating with the existing team in Boulder was yet another critical piece in our path to integration.  Todd was the original founder of Six Sense and the spiritual leader from founding and past experience in ALM space with Together J and Borland.

IMG_3654

Todd and his daughter enjoying one from the Cup Cake Shoppe in Raleigh

This summer, the office moved into a larger space to accommodate our hiring efforts in Raleigh.  So far this year, we have hired or moved six new people into Raleigh and we are not done.  Shameless plug – “In fact, we have 21 open positions at the company in Boulder, Raleigh, London and in the field.“  Part of the Raleigh growth was due to the AgileZen acquisition in April.   In January, we were feeling good enough about our lessons learned with the 6th Sense acquisition to make that move.  This time, instead of moving Rally people to where AgileZen lived, the AgileZen team moved to our Raleigh office.  We found out about their intention to move during the negotiation process and it was a huge green light in the transaction. (Think like BEA above – makes balancing autonomy and culture much easier when the management bench can not support the acquisition.)

Based on some of the joy, happiness well-being and cupcakes! (These were no ordinary cup cakes, they were from the Cup Cake Shoppe – made famous by President Obama during the Healthcare debate. We found out the owner is a great lady as she even chauffeured our own Susan Ruh to the new office!) Jean and I witnessed all this during our Q2 celebration visit, Rally Raleigh has certainly taken strides to build a cohesive agile team in a period of growth and integration.

But, there is still more to do

We recognize that there are always items in our organizational backlog.  As the Raleigh team continues to build the whole, we owe a bunch to the folks who were closest to the open-wheel racing process.  They kept their cool, did things to build empathy for the other team and kept focused on delivering value.  For Rally as a whole, we still have a lot to learn about running remote offices in a culture that is much more collaborative than what any of us witnessed in the last decade at BEA, Borland, Mercury, Quark, Rational, or Serena.

Please comment your ideas or experiences with remote offices and highly agile teams.

Ryan Martens is a tomato canner, school board member at Friend School Boulder, and CTO at Rally Software Development.

Jean Tabaka is a wine enthusiast, author and Agile Fellow at Rally Software Development.

Ryan Martens original post

No Impact Man – A cool Gift

Friday, September 3rd, 2010

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Original Post by Ryan Martens

On Wednesday, I received a copy of Colin Beavan’s book called No Impact Man.   I owe a big thank you to Michael Mah of QSM Associates for the gift.  Michael and I have talked together at numerous Agile and Rally events over the past four years.  His work has been instrumental at proving the benefits of Agile by benchmarking Agile projects against their database of 7500 projects.  He has clearly seen me talk about my personal quest to get my family’s carbon and environmental footprint down, as well as our work at Rally on our corporate footprint.

My take away: As you share your personal or professional vision with others, it becomes easier for them to help you attain it. It is a wonderful reinforcing loop.  Thanks again Michael.

(Click on Book to see at Amazon)

 

This is a book about Colin and his family, who live in New York City, and how they lived for a year with a zero environmental footprint, not just a zero carbon footprint.  I have broken the cover on the Introduction and the first chapter.  It looks like a great and funny read.  Based on my Amazon search, there is even a movie/DVD on the book.

Here are some Chapter titles, to give you a bit of the feel:

  • What you think when you find your Life in the Trash
  • If Only Pizza Didn’t come on Paper Plates
  • Conspicuous Nonconsumption

I look forward to finishing the book on my next plane trip, which is coming in two weeks to the Oracle Open World/Java One/Oracle Developer’s Conference.  I am speaking there on the “Linchpins for Scaling Software Agility.” This talk is on Wednesday morning in the San Francisco Hilton, right before Ted Farrell.  Please join us both as we explore the needs and tools for team hyper-productivity.


Ryan Martens is a homegrown tomato lover, founding board member of the Entrepreneurs Foundation of Colorado, and CTO at Rally Software Development.

Ryan Martens original post

Our Agile Organization Materials at Agile2010

Friday, August 13th, 2010

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Original Post by Ryan Martens

This week both Jean and I delivered talks on the Agile organization at Agile 2010 in Orlando. Whether you were able to attend one, both or neither, this post shares the handouts and materials that we used in the talks.

If you attended, please provide comments on what you liked, were puzzled by and might change in the future.

Jean’s work was a three-hour tutorial on learning models for managing the Agile organization.   She ran three exercises and provided a bibliography of books/resources that we have used here at Rally:

Jean in action at Agile 2010

Jean in action at Agile 2010

In addition to Jean’s talk, I presented an experience report on our use of Plan-Do-Check-Act (PDCA) at Rally.  This report tells a story of our evolution of strategy execution from Gazelles/Scrum to Lean/Agile.

We hope these resources provide you with ideas for scaling your own Agile efforts beyond their current levels.  Again, please comment on the blog with what you got from the materials or the talks.  We want to hear from you on this topic.

Ryan Martens is a tomato grower, founding board member of the Entrepreneurs Foundation of Colorado, and CTO at Rally Software Development.

Jean Tabaka is a wine enthusiast, author and Agile Fellow at Rally Software Development.

Ryan Martens original post

Bob Payne and the Art of Agile Philanthropy

Monday, August 2nd, 2010

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Original Post by Jean Tabaka

bob_headI have a reason for liking Bob Payne. Bob has empathy and a true love for giving back. That resonates with some of what we are trying to do here in Boulder. Rally, as a B Corporation, has expressly created a charter about giving back to the community: 1% equity giveback, 1% employee volunteer hours (over 2500/year in the last two years) and a number of other local not for profit initiatives. For Bob and us, adopting Agile has  been an important component in how will pull our empathy and our software skills together. With Agile, we seek to deliver feasible, effective, desirable solutions in our complex world. And reaching beyond our corporate walls to deliver that desirability catapults us to being truly empathic in our solutions.

When you meet Bob, you immediately get what “giving back” and empathy is about in his Agile work and beyond. Bob is always looking for new ways to bring Agile to our community and the greater community: our complex world. Out of his own interest in giving back to the Agile community, Bob set up his Agiletoolkit podcasts site. A gift for all of us. At the recent ADP West conference, Bob was there with his sound setup.  Bob took interest in Rally’s Agile Zen acquisition when interviewing Ryan Martens. And I  had the great fun of talking about Seth Godin’s book “Linchpin” that both Bob and I had read.

In this post, I’m so honored to have the opportunity to turn the tables on Bob and be the interviewer.

“Bob, what got you started recording your Agiletoolkit podcasts?”

I began recording the Agiletoolkit podcasts in 2005 after hearing several interesting podcasts and wondering if anyone would be interested in a podcast about Agile. I had always been a gadget person so fiddling with recording equipment and microphones was a natural for me. In fact, I now also have an iPhone App for the podcasts.

I love having the conversations and the podcast gave me an excuse/push to have conversations with people that I might not connect with in the halls at a conference.  A good example of that was when someone said to me, “You have to talk to this guy Arlo.” Without that introduction via the podcast I am sure I would not know Arlo Belshee as well as I do now.

While I am by nature gregarious, I do not search out “networking opportunities”. The podcasts have forced me into a new comfort zone that includes a lot more people from the community than I would have connected with through normal channels.  While I hope people appreciate and benefit from the podcasts, I do them for myself.  That affects the style of the podcasts. Since I am not trying to be polished or create an edited product, the podcasts have a more natural/comfortable feel.  I just wish I said “UM” less and a was little more polished on my delivery. But…I am who I am and it is what it is.

“How did you get into Agile philanthropy?”

man a mano babyAgile philanthropy started as a way of trying to meld my passion for doing good in the world with my passion for agile methods.  Using the power that is evident in the agile community to do great things is one of the goals of Agile Philanthropy.  Ideally we will get to the point that this movement is self-sustaining. But we are really just starting out on this journey.  I hope that I can grow the movement in the direction of local chapters doing work for local not for profits. Right now everyone is very busy and I am the bottleneck.  We are currently working with Mano a Mano and Haiti Partners. And, I would love to have people with a passion for a particular cause to contact me and start up their own chapter.

“What about your other philanthropic interests?”

I am very interested in local sustainable food, economic development and social justice. I volunteer in my kids’ schools quite a bit.  Most recently, I built incubators with the kids and hatched chickens and worked with the teachers to incorporate that into the curriculum. I have been working to get local food into the schools; to create school gardens; and, to relax the laws in Washington DC as they pertain to the keeping of bees and hens. Most of my other work is more directly related to the work I do in Agile Philanthropy.

“When did you start the Mano a Mano project work and what have you and your yearly teams accomplished at the Agile conferences?”

Seems like forever but we introduced Mano a Mano three years ago when the conference was in DC.  I was running the development lab in the basement and hoped that I could get some real work done in the lab that would do some good.  After that, I tried to make it more formal and improve what we have done for them each year.  They have been very appreciative and very patient with us since I am learning as I go with this process.

To date, we have moved them onto a Content Management Platform and developed their iPhone optimized donation page.  Most importantly, I am happy that I have connected Mano a Mano with David Hussman and a number of other volunteers in the Twin Cities that are helping out on a regular basis.  Wayne Simacek showed up for an event that Jeff Patton and Ed Kraay were holding to help Mano a Mano define their web strategy and ended up staying on as a volunteer member of their IT staff.

It is that kind of leverage that I hope to bring by connecting the two communities.

“What do you have in store for us at the Agile2010 conference?”

For the Agile2010 Conference, I am working again with the UX stage to do an Extreme Makeover for the Mano a Mano web presence.  We hope to be able to work on their information architecture and site design to improve the impact of the message that Mano a Mano is putting out. We are looking for volunteers to come by the LiveAid lab and help with the effort (hint, hint).

I also hope to get people interested in replicating this model for not for profits that they are passionate about.

You can do this too

To end this post, I want to thank Bob for the example he sets for all of us. I also want to emphasize Bob’s call to action to get engaged locally. You can do this through your existing local Agile group. Or, you can create a new group with an express charter to give back to the community. Recently Brad Feld here in Boulder wrote about the “Boulder New Technology Meetup” event that supported over 300 people engaged with 20 local non-profits. And here at Rally, we are marching along with Bob philanthopically working to give back: supporting  Intercambrio, donating time to local non-profits (Community Food Share and Growing Gardens) and working with the Salesforce Foundation.

Jean Tabaka original post

“Dear Agile”– A Love Letter

Monday, July 19th, 2010

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Original Post by Jean Tabaka

Dear Readers,

Writing or receiving a break-up letter can be fairly daunting or shattering, letters-1depending on which end of the letter your name appears. That letter puts a pretty hard stop to a relationship. It’s communicating detachment and finality. It can create a lot of pain whether intended or not. In contrast, a love letter is uplifting. The endorphins fly! Someone is revealing their attraction for you, and their hopes and wishes for a future with you.

Now, there is a reason I have these letters on my mind. I’ve just returned from Rally’s Agile Leadership Forum – a great gathering of people eager to lead successful Agile transitions in their organizations. The event included a lively presentation from Forrester Research’s Senior Analyst Dave West: “Agile Adoption – Research Findings on the Adoption of Agile.” (You can find some of Dave’s data in the “Forrester Wave: Agile Development Management Tools, Q2 2010″). We also enjoyed an inspirational talk from our CTO Ryan Martens, called “Moving Agile Beyond Software.” These great presentations were followed by breakout sessions and a panel discussion about Agile challenges. Now, how to end the event?

As emcee of the forum, I not only kicked off the event, but it was my job to bring closure to the gathering as well. How can we have people walk away with thoughts about Agile? Why are they interested in the first place, and where do their concerns lie?  I was inspired by a video I recently saw about “breakup letters.” The Breakup Letter is a design research tool that Smart Design uses to understand the emotional connection between people and their products, services, and experiences. One person broke up with his cell phone, another, her single-cup coffee maker.agilelove

Now, just how does this relate to the Agile Leadership Forum? I liked the concept of the breakup letter, but I decided to entirely flip the idea and close the event by asking everyone to write love letters instead. In the spirit of Cyrano de Bergerac, I asked each table of participants to work together in crafting a “Dear Agile” letter. In this letter, they were to convey their attraction to Agile. And, they were to reveal where they were concerned about as well. All letters were to be from a secret admirer :-)

Once the groups began to read their letters, I knew we were on to something. Though I don’t have the reading of the letters on video, here are a few examples of our “Dear Agile” love letters.

 

Run this exercise in your own group to find out what the Agile “lure” looks like and also what the “turn-offs” might be.

Breathlessly awaiting your comments,

Jean


p.s. If you want to read some of the transcribed texts of the love letters, read on!

__________________________


Dear Agile,

I have admired you from a distance for some time. Waterfall and I are in the process of an ugly breakup. There is so much about you I need to know. My friend says great things about you. You are so simple and straightforward– no mind games like Waterfall.

This won’t be simple. Waterfall still has clothes at my place. My Facebook status is confused.

In the relationship as we get to know one another, we will have to know each other carefully– co-locating right away? Are we sprinting too fast?

Be gentle with me.

Looking forward to a rapidly developing future.

xoxoxo,

Secret Admirer

__________________________

Dear Agile,

I love you because you offer quick cycles, better quality, and better teamwork. From the first time I saw you, I thought I could begin saving money and add business value.

But, fair Agile, you are not so simple. I’ve heard you are a micro-manager. I don’t totally understand you. Some people are confused by you. On the surface, you sound so perfect and simple, but the more I get to know you the more questions I have.

But, among all my choices, I choose you. You promote collaboration, and allow me to turn things around quickly. You’ve helped me trim weight and stay lean. Don’t disappointment me, I trust you!

With all my love,

Megedá

___________________________

Dear Agile,

I loved you from the first moment I saw you, I loved your fast, speedy releases and that you don’t come with a lot of baggage or documentation. You’re simple and down to earth. You are a great communicator. I always know where you are and my friends love you, too.

I am, however, a bit concerned that not everyone accepts our relationship. I am worried that as my job continually grows and my needs scale up, whether you can handle the increasing challenges. And I’m concerned whether I can afford you… Our relationship and your attachments are what intrigue me the most.

Looking forward to spending more time with you and getting to know you better.  – Your secret admirer.

___________________________

Dear Agile,

We love you, we think you are awesome – for the following (bulleted) reasons:

  • Agile accepts changes and encourages frequent changes
  • Agile can start implementation before full requirements are known.

We do however have a few problems with you agile –

  • Handling cultural change in the organization
  • Does not solve all our issues
  • Makes distributed teams harder to work with

- Your secret admirer -


Jean Tabaka original post

Using Problems and Difficulties in a Culture of Innovation

Monday, June 21st, 2010

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Original Post by Ryan Martens

This is #4 in a Series on the Culture of Innovation with guest blogger Lee Devin.

Problem or Difficulty?Do you notice a difference between problems and difficulties? A problem has a solution. When engineers solve it, the problem goes away. It’s a question raised for solution with fixes, tests, and checklist updates. In contrast, a difficulty has no solution. A difficulty wants you to sit with it, address it, not solve it. Artists know this world of the difficult very well.  No definitive fix, test, or checklist will suffice. Sitting with and playing with the difficult is simply part of the knowledge work of the artist.

For both the engineer and the artist, a difficulty is often what tangles up the solution to a problem. We see problems and difficulties all around us in the world of innovation. What’s needed to address a difficulty may not be clear at first, if ever. You may, in fact, never achieve that lovely industrial clarity. And yet, our ability to gaze unflinchingly into the face of difficulty will lead us to solve problems with greater innovation and deeper artistic mastery.

Difficulties require “AND” thinking

Difficulties are fuzzy. Improving how we address difficulties requires us to hold a large container with the word “AND” versus the word “OR.” This concept was first introduced to me in Peter Senge’s Fifth Discipline Fieldbook. I also delved into the topic in his course on Leading and Learning for Sustainability. To work with difficulties, we hold and play with a spectrum of possibilities, multiple solutions sets: this AND this AND this AND this. For the actors in a theater ensemble, AND means absorbing a variety of possibilities with the materials surrounding the play. Many innovative outcomes await based on the ensemble’s ability to hold the ambiguity of the art and embrace that sense of release.

For engineers, this might look like the following: you are solving multiple simultaneous equations for problems you see in the larger system. To be able to hold on to this container, you and the team have to feel safe “failing” with lots of little experiments. You must keep the “art of the possible” in mind. This is not an easy task for an individual, much less a group. Difficulties that accompany problems require the courage and patience to sit in a large container of ambiguity.

Consider the wicked problem example

In their book Wicked Problems, Righteous Solutions Peter DeGrace and Leslie Hulet Stahl help us delve further into problems and difficulties. Wicked problems arise out of several conditions. First, the problem domain is complex and fraught with difficulty. Then, the solution domain is similarly complex and difficult.  Finally the two overlap. That is a wicked problem. Wicked problems hold nests of difficulties. Let’s compare the wicked problem of an engineer and one of an actor.

The engineer’s work begins by reading a user story and exploring the problem sheet from the architecture council. In this assignment, the engineer must be prepared to address known and unknown difficulties on the path to a solution. The engineer recognizes that there is no one solution. How difficulties are addressed may be the key to just how innovative the resulting solution is.

This assignment is the equivalent of a script given to actors. The script is not a limit, but rather material on which to perform and interpret to create something new. There is no one solution. And so, the actors hold ambiguity as they move to the ultimate offering to their audience.  How the final play comes together may depend on the ensemble’s ability to play with and address the large realm of possibilities.

The art of the possible and innovation

Like actors, engineers and other knowledge workers need to do our homework, invite innovation and alternative solutions. We need to address difficulties not by point solutions, but by applying “AND” thinking, creating large containers of possibility. We must embrace the art of the possible. In the case of the actor, this comes in the form of rehearsal, ensemble and release that ultimately leads to the actual performance. In the case of the engineer, this work comes in the form of design spikes, set-based engineering, and tests. In both cases, experiments create space around difficulties. The art of the possible broadens the team’s or troupe’s innovative outcomes.

For such a culture of innovation, “AND” thinking is a vital function. At Rally, we apply “AND” thinking in how we address difficulties in a variety of ways. We may take a particular problem with its difficulties and spread it across a paired team of engineers. The teams work safely in an “art of the possible” mode for addressing difficulties in a way that leads to a better solution. We eventually move through the “AND” to a final solution, having addressed the difficulties in a variety of contexts. How you invite “AND” thinking and the art of the possible into your organization may include your Chief Engineer, a Product Owner, Director of System Engineering or a peer engineer all working in a new larger container.

Say “No,” to “No way!” and “Yes,” to “Imagine if…”

Within given circumstances, which are different for each team member, and a safe container for the conversation, the group can play out the implications of a solution, and discover its virtues and flaws. As with an ensemble of actors working through the possibilities of a scene, the only rule is: Never say, “No!” Swallowing that “No” can be hard! You must fight your first response to a suggestion or proposition, which is often “No, there is no way that it will work.”

Instead, the thing you must do is think, “Wait a minute. Let’s assume it will work. Let’s find out what happens when it does.” And, you’ll find out what happens when it does by behaving (thinking, talking, deciding) as if it is in place and working. If your first response is “Oh, wow, what a great idea!” the release might be, “How do I fit myself into this? What can I do personally to make it work?” The tool here is imagination.

We must find comfort in ambiguity and uncertainty. The question is: how can you create the container that allows your team to live with this difficulty and keep from jumping to try and solve it? If we create a culture friendly enough to notice accident and serendipity, we set ourselves up for the asymmetric payoffs associated with successful innovations. Our “AND” thinking and art of the possible ferret out the wicked problems and harvest collective team creativity.

Ryan Martens original post

Agile and Lean Product Development – Yesteryear, Today and into the Future

Wednesday, May 12th, 2010

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Original Post by Ryan Martens

Yesterday, the Agile Journal posted their May edition of the online publication with the above focus.  To support their release, they asked us to share our opinion on the topic.  Here is our response:agilejournal

Ryan Martens: Age of Reconsideration, Reform and Regeneration

The last decade marshaled in a new empirical way of working with increasingly complex, interconnected and highly-critical software-based systems – Agile.  We are entering a period of reconsideration, reform, and regeneration in software, systems engineering and project management.  Agile is working, Lean Software and System is working, and the combination is starting to prove very powerful with regard to throughput and workers.  The benefits of autonomous work, engagement and mastery are driving systemic improvements in our way of working and growing to meet complex challenges of our world.


These results illuminate a future vision that has the potential to expand our current notions of Lean and Agile from software teams and into real organizational agility.  As a result, there is a chance to unite and unify many communities under the guiding ideas of flow, pull, and value.  All of these communities are being drawn in and starting to play well.  These are beautiful days with all the implications to CMM/SEI, Agile, Scrum, Lean/LEI, and PMI/PMBok communities yet to be determined.


In the first half of this decade, look for collaborating across boundaries, seeing larger systems and groups working hard to create their future realities.  Following that period, look for messy consolidation as the winners of this new platform emerge for a new golden age of networked, software product and system development. Together we’ll be focused on the problem domain of global scale difficulties in governance, cyber-warfare, energy, water, communication, commerce, medicine, climate, transportation and nano-technology.


Ryan Martens is an amateur triathlete,  founding board member of the Entrepreneurs Foundation of Colorado, and CTO at Rally Software Development.

Jean Tabaka: Let the System Talk

Thinking about our path with Lean, I’m compelled to draw upon research I’ve been doing in Systems Thinking and, more recently, what I’ve been learning in Systems Engineering.


In Systems Thinking, we recognize a world of system archetypes based on the dance of balancing loops, reinforcing loops and the outside agents that may cause them to transition. Lean, as a system of thinking, has certainly responded to systems that rely too much on take-make-waste. A set of negative reinforcing loops: the more you waste the less you have to take and make. Outside agents, the scarcity versus abundance of materials, has led us to Lean. Lean principles and practices create a positive system wherein the more we reduce waste the more value we get which in turn reinforces more waste reduction. It is a reinforcing loop propelled by continuous improvement.


Recently, I attended the Lean Software and Systems Consortium’s 2010 conference in Atlanta. What a revelation. From James Sutton’s talk on Lean Systems Engineering, I added new vocabulary that I think will become critical to Lean’s future.


Will Lean be our best source of practices and principles in the future? That depends on what will be guiding our systems:

  • Scarcity
  • Abundance
  • Desperation
  • Conformity

Once we have clarity about what guides our system, we can understand more about the system in which we are operating:

  • Simple
  • Complicated
  • Complex
  • Chaotic

Lean has steadfastly addressed pressures of scarcity and hence a system of complexity. That brings me to Dave Snowden’s work captured in Cynefin, a Welsh word he has used to describe a framework of problems, situations and behaviors in these four systems. For our world of complex systems, Lean provides the perfect high-level thinking for what we must embrace: emergent practices informed by, as Snowden puts it, “sense-making”


As we move into the next 10 years of Lean, I fervently believe that our sense-making must inform us about what supports emergence that responds to complexity. The practices will follow. For now, let us concentrate on the systems in which we operate, what outside agents or pressures are guiding our systems, and how we can best continue to formulate and hold dear the practices that will naturally emerge.

Jean Tabaka is a wine enthusiast, author and Agile Fellow at Rally Software Development.

Subscribe today to get free updates by email or RSS.

Ryan Martens original post

What do Toyota, Tabaka, GM, and NUMMI have in Common?

Friday, April 16th, 2010

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Original Post by Jean Tabaka

My name is Jean Tabaka.

I live in an Agile and Lean world where we take a “stop the line” mentality for granted.  I am encouraged to give my observations and recommendations about continuous improvement. I’ve been learning to create my own reality, to continue learning and to find my strengths in cross-functional work. I passionately read about, talk about, and practice Agile and Lean principles. These principles continually inform how I can create benefit for my company and how I derive benefit from my company.

I’m the lucky Tabaka.

Army JimMy father, Jim Tabaka, was a life-time white collar worker for GM, starting fresh out of University of Illinois with his mechanical engineering degree.  He worked 12 hour days, on his feet the entire time, walking the plant floor, making sure cars kept coming off the line at all costs. He retired at age 55 with a great pension and unbelievable health benefits.

Tim TabakaMy brother Tim Tabaka is a retired GM blue collar autoworker. Well, retired is the euphemism for, “Would you please leave early so that we can bring in a younger, less experienced, cheaper workforce?”  During his time at GM he worked any shift he was told to work. He even moved to a different, older plant. Why? He needed the job and they wanted to replace the older workforce with a cheaper, younger workforce.

My nephew, Andrew Tabaka is a current GM autoworker. He came in under-skilled and now works a night shift for a GM subsidiary building brake assemblies. Andrew is one of the people Tim trained on his way out. Andrew is 24 and this is his first job. I suspect he intends it to be his life-time job. Well.Andrew Tabaka

I’ve never worked for GM but learned to drive a stick-shift on a Chevy Corvette (yes!) And, while growing up, my dad used to take me to visit the plant where he worked in St. Louis. The acres of parking lot outside the plant were for all the cars that had rolled off the line but could not be shipped to a dealer. Too many defects.

Get the picture? We have been and are a GM family.

And I’m telling you this for a reason.

In 1984, GM and Toyota entered into the NUMMI (New United Motor Manufacturing Inc.) agreement to co-run an auto plant in Fremont CA. NUMMI made big news at the time. It took an existing, highly dysfunctional GM workforce and turned them into one of the most productive auto plants in the US. A documentary about this recently aired on Ira Glass’s “This American Life”. What a story, too fantastic to be made up: the complete turn-around of a failing GM plant to a thriving joint venture. The documentary recounts 30 disgruntled, unmotivated GM employees traveling to Japan to work with Toyota employees to learn “The Toyota Way”. It features commentary from Jeffrey Liker (author of “The Toyota Way”) John Shook (author of “ Managing to Learn”) as well GM line workers and GM management. The power punch of the Ira’s story? GM never replicated the success at the NUMMI plant.  Several theories about this failure are postulated at the end of the documentary. It is up to the listener to form their own conclusions.

Two weeks ago, as a coda to the documentary:

The Fremont NUMMI plant had its last Corolla roll off the line. NUMMI was shut down, this time for good. It was the first factory ever shut down by Toyota.

I care both personally and professionally about that darn NUMMI plant. The Ira Glass documentary about NUMMI’s turnaround and GM’s failure to replicate struck a deep chord for me. I called my brother Tim that evening to get the real scoop. I had heard him recount what his life was like in a GM plant and I wanted to hear it from him again.

The truth is the NUMMI success DID have an impact on GM outside the Fremont plant. Prior to the NUMMI conversion, life in the Oklahoma City plant where Tim worked was miserable. As in the story “Rivethead” by Ben Hamper about GM plant life in the 1970’s, alcohol abuse, absenteeism and nervous breakdowns were common place at Tim’s workplace. He lived the life documented about the Fremont plant prior to the Toyota venture.

Life with the Andon.

In the late 1980’s though, Tim told my about how things were changing, amazingly so. A “stop the line” mentality was adopted at their plant. Use of an “andon” was introduced. One tug on the andon was the alert to call over for some help; a second tug was “stop the line” we need more time to fix this. Tim was one of the people who roamed the plant floor prepared to assist when the andon was pulled once so that it wouldn’t have to be pulled again. Every station had its own andon “song”. (Apparently the “Baby Elephant” song became the bane of my brother’s existence.)

Life was so much better (the “Baby Elephant” notwithstanding). Workers were encouraged to stop the line and fix problems versus pushing cars through. Teams were brought together to offer suggestions for how to improve the work processes and the flow within the plant. Quality went way up and defects went down. Morale and motivation went up. Alcohol and drug abuse went down (this is anecdotal from my brother, not based on an actual study.) And for Tim personally, plant life improved dramatically. The new system played into his strength: being a cross-functional team member, challenged and rewarded for doing his work.

Back to the NUMMI story and what GM ultimately adopted.

NUMMIFair enough. I have my brother Tim as an example of an autoworker who benefited (well, except for the darn “Baby Elephant” team’s issues). But I also have a father who, as a GM executive was expected to tirelessly follow and communicate the GM line. It took its own deep toll on him. And I have a nephew who continues to work as a very replaceable night shift cog in a different plant in the GM machine. GM has declared bankruptcy for any number of reasons. And now, my mother’s benefits, my brother’s pension, and my nephew’s pay are in peril.

My name is Jean Tabaka, daughter of Jim Tabaka, sister of Tim Tabaka, and aunt of Andrew Tabaka. My father never benefited from Lean thinking. My brother had a wonderful brief taste of it. And my nephew is now somewhere in an odd stew of Lean and non-Lean practices.

I’m the lucky Tabaka. Lean has brought me a lot and taught me a lot in my Agile world. While Lean may be most closely affiliated with the Toyota Production System; and while it may be assumed that failure to adopt the TPS was GM’s ultimate demise, I believe the Lean lessons have continued to grow, spread, and morph as a result of both success and of failure in Lean adoptions.

GM, Toyota (yes Toyota), NUMMI, the Oklahoma City plant and others all have their stories of success and failure. Each had their approach to Lean adoption. Like Tim Tabaka and NUMMI, we have our lessons to learn from Lean in our software world. Lean is not the panacea. The TPS cannot tackle all issues. Agile is not the panacea. No one methodology can guarantee product success in all situations. Our continued belief in checking the value of our adoptions is critical. Our conviction to pay attention to failure modes as well as success is key. If you don’t believe me, ask my brother Tim.

Jean Tabaka original post

Plan-Do-Check-Act at the Lean SSC Conference April 21-23

Thursday, March 25th, 2010

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Warning: preg_replace() [function.preg-replace]: Compilation failed: unknown option bit(s) set at offset 0 in /var/www/wordpress/wp-includes/shortcodes.php on line 227

Original Post by Ryan Martens

On April 21 in Atlanta, the Lean Software and Systems Consortium will come together for its second US conference.  Last year’s event in Miami was “amazing” according to Jean.  So this year, Rally is exhibiting, I am speaking while Jean and Aaron are running the open space on Friday.  The price per attendee goes up by $250 on March 31st, so if you do intend to go, REGISTER now.

At our booth, Rally will be demonstrating its product support for highly-visible Kanban, WIP/Cumulative Flow reports, and cycle-time  metrics. Join Alan Atlas, Jean Tabaka, Aaron Sanders and Craig Langenfeld in our booth.

I will be presenting an experience report titled: PDCA: Beyond Simple Inspect and Adapt. On spring break this week, I’ve been thinking more about the details of my talk. Here is my abstract and outline for those of you who might consider attending:

Lean and Kanban focus on practices of continuous flow of product delivery. Plan-Do-Check-Act (PDCA) is a Lean discipline that moves beyond inspect and adapt of Agile team-level processes.  At a corporate level, PDCA provides guidance for strategy as well as problem-solving work. In 2009, I led Rally’s move to PDCA for the company’s strategy process at both the annual and quarterly levels.  My primary guide was Pascal Dennis’ “Getting the Right Things Done”. In this experience report, I share Rally’s PDCA first year of adoption: where we started, how this impacted our corporate behaviors, and where we are now. I want to share Rally’s story to compel participants to embrace PDCA and get good at it. I ask each participant to come with its organization’s #1 goal and success criteria. I will close with a planning A3 exercise from Pascal’s book .

Outline

  1. What brought me here—background on why I am passionate about sharing my organization’s overall Lean story including the addition of PDCA, A3’s and concurrent set-based development.  This talk focuses on PDCA as the critical step in increasing structure and discipline in strategy execution.
  2. Point of View – Use PDCA to move your planning horizon out and as the principle governing mechanism for organizations in continuous flow.
  3. Benefits — Mature your strategic planning and execution environment to handle the complexity of increasing speed, agility and scale and to gain alignment, pull and innovation.
  4. Where we were and what was not working
    1. The context at Rally was based on a couple of key concepts:
      1. Core Values, Core Purpose, Sandbox and BHAG from Jim Collins
      2. 3 to 5 Quarterly Rocks, success criteria and Scoreboards from Gazelles
      3. Rock team structures  – cross departmental and story based
      4. Facilitated, highly collaborative cross-departmental meeting of 30+ managers and above
    2. What we noticed
      1. Rock work as a second or third job
      2. Wisdom of the Crowds to help fix over-reaction and group think
      3. Too much on the fly, not enough backlog grooming
      4. Highly critical, non-cross departmental initiatives were de-prioritized
      5. ORID process added to keep from jumping too solutions, but the data was not visible enough
  5. What we decided to do about this:
    1. Explanation of PDCA — A brief overview of PDCA in general and then specifically what I used as guidance from the Pascal Dennis book, “Getting the Right Things Done: A Leader’s Guide to Planning and Execution”.
    2. Our initial experiments with A3 process the year prior — Working with our Ops team and product marketing teams on problem solving using real data
    3. First quarter — How we kick-started Rally’s company-wide adoption of PDCA . I describe our “Mountain Team” and their transitional role.
      1. Defining Rally’s True North
      2. Creating our second level tree with current and needed metrics
      3. Socializing these throughout the company seeking feedback in anticipation of our annual and quarterly planning
      4. Started new experiments based on quarterly planning decisions
    4. Next Quarter – Review new experiments, discussed learning and drive A3’s into the planning process
    5. Mid-course adjustment by Mountain team, in middle of the quarter – What we discovered working and not working
      1. The rocks were all dependent on each other.
      2. Had to run Rock of Rock team meetings to steer to a final solution
      3. Coordinated release planning would have
    6. Final quarter – We worked to expand the plan. We took the Mountain team’s True North and feedback to drive our PDCA for Rally’s Annual Corporate planning by:
        1. Taking company-wide feedback into our Annual planning to collaboratively drive cross-department A3 creation around each branch of the tree
        2. Mountain Team retrospective over the course of year 1 that helped create a planning rock team.  The Mountain team’s role as a transition team ended.
    7. Year 2 – Doubling down our efforts to go from amateurs to intermediates —Changing our process to institutionalize A3’s and PDCA as our strategy execution approach:
      1. Quarterly rocks moved to a world of pre-defined from developed on the fly
      2. Quarterly planning moved from ad-hoc based on yesterday’s weather to more programmed based on True North and meeting the target metrics
      3. Strategic planning worked to validate annual True North in the context of long-term planning, shared vision development, cross-boundary collaboration and larger systems
  6. What we learned and what you should do about it
    1. The cycle of adoption is a year, quarterly cycles work to improve the process, but it is hard to make leaps on a quarterly basis.
      1. Year 0 – Introduce Lean thinking (A3 in our case)
      2. Year 1 – Introduce PDCA (Novice)
      3. Year 2 – Invest or abandon (Your choice)
        1. A3 is now the language for problem solving
        2. Making sure we are solving the right problem (aka slowing down to speed up)
    2. Do not have a overall guidance team steering the continued PDCA process – it is owned by the “team”
    3. Putting pressure on the organization to get more clear about our economic models to mature from “Theory-based decision making toward the right solution,” Now “Data-driven decision making toward the right problem”
    4. Where to start – The Strategy A3 an exercise
    5. What is next? – We call it the Innovative or Lean Organization. Seeing large systems, collaborating across boundaries and creating your reality.
  7. Point of View – Use PDCA to move your planning horizon out and as the principle governing mechanism for organizations in continuous flow.
  8. Call to Action – Introduce the language of A3’s through problem solving or Strategy A3’s
  9. Benefits — Help build a company of problem solvers to focus your efforts on the critical few things.
  10. Where I hope you go with this: Great companies build great software, great experiences and work on creating win/win scenarios.
Are there other questions you’d like to see answered in Rally’s experience report on Plan-Do-Check-Act? I look forward to seeing you at Lean SSC.
Ryan Martens is telemark skier,  father,  founding board member of the Entrepreneurs Foundation of Colorado, and Founder and CTO at Rally Software Development.

Ryan Martens original post