In 2001, the Agile Manifesto was created with 17 signatories from around the world. Following on the heels of the first XP conference in Sardinia in 2000, the Manifesto fired its shot of agility across the Waterfall bow. A year later, at XP/Agile Universe 2002, I found myself standing at a folding table with Janet Danforth of Facilitator4Hire. We were selling facilitation services to the members of the Agile community gathered at a Courtyard by Marriott in Lincolnshire, Illinois. Approximately 80-100 people had come together in that steamy summer venue to continue Agile discussions and to define ongoing growth of methodologies, practices and frameworks.
Where we were
At the same time I was at my folding table in Lincolnshire in 2002, Ryan Martens was at a whiteboard in Boulder, Colorado. Ryan was brainstorming ideas about how he could use Agile practices to create a Software as a Service platform in the Agile domain. His goal? To provide zero-waste, low-carbon emissions applications and services for this growing, vibrant community.
In 2003, the Agile community gathered in Salt Lake City for the Agile Development Conference. This was my first time presenting at an Agile conference. Janet Danforth and I conducted a workshop: Collaboration 4 Agile Projects. And, unbeknownst to me, Ryan was also in Salt Lake City for his first Agile conference. As Ryan was busy engaging vendors about how they were supporting the adoption of Agile, I was busy networking with Agile thought leaders and helping to found “The Freaking Flock” (you’ll have to ask me about that in person!) Our paths were set and Agile was on the move.
Fast Forward to 2011
Now, in 2011, we are 10 years on from the Manifesto signing, 9 years on from the first sighting of me at the folding table, and 8 years on from Ryan’s first foray into the conference.
The Agile 2011 conference is an exciting one for both Agile and Rally. We are pleased once again to be a Title Sponsor of the conference. This year, August 8-12, Rally has 11 speaking sessions on the wonderfully vast and diverse program.
We’ve also participated behind the scenes in advance of the conference as producers, co-producers and reviewers for various conference stages. And, once again, we’ll have a booth where you can come to meet our Agile coaches, talk with our technical gurus, and see the latest that is happening with Rally’s Agile ALM platform and services. Plus, you won’t want to miss our special commemorative activity at the booth this year. Stay tuned to the blog and follow our Twitter hashtag #roadtoagility for more details on how you can participate with us!
Going back to my history of Agile and Rally and the conferences
Ryan and I never met at the 2003 conference. But in 2004, as the conference moved into the northern Rockies in Calgary, Alberta, 4 of us stood together at a folding table in a small hallway. Rally’s representation at that Agile conference was Ryan as President of the company, Richard Leavitt as our VP of Marketing and Sales, Brad Norris as our sole sales person, and me as the sole Agile Coach. At that point, none of us were speakers. However, Rally has had one or more speakers at each conference since: Denver in 2005, Minneapolis in 2006, Washington DC in 2007, Toronto in 2008, Chicago in 2009, and the 2010 event in Orlando. Additionally, Ryan served on the Agile Alliance board during the years of the Washington D.C. and Toronto conferences.
From the folding table to now
Some things have changed in Rally’s Agile journey. We’ve grown from a 20-person company in 2004 to over 250 people and counting. Ryan is now the head of the office of the CTO. Richard is now the Executive Vice President of Worldwide Marketing. Brad is our Vice President of Field Operations. And I am an Agile Fellow in the Office of the CTO.
From a Manifesto, a whiteboard, folding tables, and a single speaker to title sponsorship with multiple speakers, producers, reviewers, and booth presence in a true exhibit hall at a conference with over 1,600 attendees, we’ve indeed come a long way!
Jean Tabaka is a frequent flyer on no particular airline, an author and Agile Fellow at Rally Software Development. You can follow Jean on Twitter at @jeantabaka
I’ve been pretty passionate about collaboration and knowledge flow throughout the decades of my technical life. This passion led me to author Collaboration Explained. Now I value playing with and applying a variety of visioning, planning, and learning models in Agile organizations. My reading has focused on models for individuals and organizations in how they create flow of value in 21st century businesses. For me, there could be no better place than the Agile context in which to apply these models of rich knowledge sharing. Complex Agile organizations need to consider diverse models that can effectively guide how they plan and deliver.
Agile planning helps us scale and mature across the organization
With this in mind, I’m excited to announce a new series about N levels of Agile planning. I’ll be co-authoring the series with my Rally colleagues Ben Carey, Zach Nies and other Rally folks. Ben, Zach and I want to share some of our informal conversations around Enterprise Agile planning, knowledge creation and knowledge sharing. That means we’ll be blogging about various models we think can be useful for capturing and tracking Agile business value up and down the organization. Our suspicion is that useful scaling and maturing models coupled with overall team practices bring great value at a variety of levels within an Enterprise Agile organization.
In this series, we’ll share direct experience in applying our models both within Rally and with Rally customers. That means we’ll share some insights about collections of practices at the various levels of Agile planning. We’ll also provide guidance around the Rally services and tooling we believe support planning in continuously innovative, value-driven organizations. Also, be sure to check out Ryan Martens’s series about Scaling Agile to the Strategic Level. Ryan and others will be providing on-going guidance about Rally’s “Project Stratus” tool for road mapping and other strategic practices specifically for Enterprise Agile beyond Release planning.
Ben, Zach and I don’t believe we are the sole experts on this topic!
We’re exposing our frank conversations in hopes of gaining your reactions, insights and feedback. You probably already know about some of Rally’s existing guidance on Agile planning. We just want to dig a little deeper, play a little more with these perspectives and some new approaches that could help you innovate your own Enterprise Agile adoption. While we do this, we’ll be reporting on how we are experimenting with these models here at Rally in our own practices using our own tools and our own services as well as new practices.
Look for our first blog in the next few days describing the overall model of “Why, How, and What” in positioning the value of Enterprise Agile planning. How many levels of planning will emerge in our exploration, and what will they look like? We aren’t yet prepared to declare in a definitive fashion. Instead, we’ll peek into that together with your input.
Join us as we go into N levels of Agile planning and beyond. We’re looking forward to great dialogue with you through the comments you bring.
Jean Tabakais a crash skier, author and Agile Fellow at Rally Software Development. You can follow Jean on Twitter at @jeantabaka
Writing or receiving a break-up letter can be fairly daunting or shattering, depending 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.
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 –
I just wanted to take this opportunity to thank each and every one of you who follow the Agile Blog.
Jean and I have had a great time writing these posts over the last year, and we are humbled by the way you’ve responded. After a few years of casual, intermittent posting in our Agile Commons community, we jumped off the deep end into blogging this year by hatching out this site and our Engineering Blog.
We are truly grateful for how you have helped us learn and grow: for every comment, every tweet, everything that you have shared with us.
And we are hopeful that the learning has been a two way street. That is, whatever topics or ideas we posted in the blog that particularly resonated with you, we are honored that you invited us into your 2009 professional journey. In fact, we’d like to see your comments on what you found particularly useful or engaging in this past year. And we welcome your suggestions for topics in 2010.
We look forward to continuing this great conversation in 2010.
I’ve been thinking about leaning a lot lately, and not of the pressed-wood bookshelf nuisance variety. I talk about Lean with my colleague and President of Rally, Ryan Martens. So when I talk about a leaning bookshelf, I’m referring to my interest in Lean in all its forms. I am talking about the books I’ve been reading that pertain to Lean. And, more specifically, how can I turn my “Leaning bookshelf” into a continuous “learning bookshelf”? How can I think about my evolution of thought and practice with regard to Agile as influenced by Lean? What could be a good, rewarding goal?
And so, through discussions with Ryan and some of my own quiet thought, I came up with a goal of improving my notion of learning. Yes, for me, that seems to be what I am discovering more and more about Lean:
How to learn
How to teach others to learn
How to encourage organizational learning
How to avoid/eliminate re-learning
And so in this post, I thought I would share what I am reading, have read, or am about to read, and ask you for your comments and recommendations with regard to my leaning—>learning path. Some of the books may not look directly associated with Lean. I just know that they have been part of my lean learning journey.
Looking at my leaning bookshelf and thinking of my focus on learning, I realize I haven’t included any Senge books or others about organizational learning. That will have to wait for another post.
What books are important to you on your leaning/learning path?
Right now, we are all working through our 2009 budget process with the unknowns of the economic recession staring us in the face. This budgeting cycle holds more unknowns than we’ve seen in awhile, so it’s making everyone cautious about finding the right moves that will cut costs in the short term without damaging our businesses.
Unfortunately, layoffs may be part of the solution to achieving short-term savings, especially for firms hit hard by the recession. In short, layoffs suck. These highly personal actions are sad, and I am sure you and your staff may need some time to grieve the losses. But prior to cuts, there is a bigger issue to consider while managing belt tightening -– your long-term vision and direction. Put simply, it is imperative to refresh your 2009 vision before the cutbacks, or you risk destroying the morale of the whole team, losing key personnel, and dropping market share.
As you look to make cost-saving cuts, the first question is, how are you going behave?
Take the easy way out and cut in a way that fixes the short-term at the risk of harming your long-term prospects. “Across the board” cuts fit this behavior.
Rise to the occasion and cut in ways that meet short-term needs and advance your long-term goals.
On Nov. 9, Rahm Emanuel, the new chief of staff for President-elect Barack Obama said, “Rule one: Never allow a crisis to go to waste… They are opportunities to do big things.” Clearly Mr. Emanuel is reacting by rising to the occasion – scenario number 2.
The trick to taking advantage of this crisis is to resist the pressure to simply cut without a long-term plan that everyone understands. When you do not have long-term goals, short-term fixes always lead to unintended consequences that are typically worse than the original problem. Said another way: While we sometimes get some of the intended consequences, we always get all of the unintended consequences.
A key goal of every IT department is to reduce the time and effort needed to deliver value to the business. To accomplish this, the best long-term trend we have in IT beyond Moore’s law and the power of the Internet is the improvement of IT agility. Increasing IT agility is important because it provides a value innovation and delivery method that harnesses these fundamental advances in infrastructure.
Tom Poppendieck, a leader in the Lean IT movement, recently said, “You can’t cut costs by focusing on cutting costs. You’ve got to focus on the changes that will lower your costs over the long run.”
If you are exploring the adoption of agile software development practices and you’re prepared to rise to the occasion, this recession and the resulting belt-tightening gives you an opportunity. You have the opportunity to rally your company around a vision that will not just cut costs, but improve morale and help you grow your business in the next economic spring.
IT agility
For the 70% of you who have not adopted enterprise agility, let’s do a quick overview. Agile practices enable teams to build less, but return the same value by focusing on early delivery of the features that have the highest business value and not wasting money on the features that don’t.
IT agility is driven by three major innovations: agile development, Software as a Service (SaaS), and Web 2.0 social networks. However, without agility in development and software releases, the innovations of service-oriented architecture (SOA) and Web 2.0 are elusive.
There are three costs savings for enterprise IT agility proven through benchmarking analysis:
Lean flow provides more productive development organizations.
Better prioritization delivers the most valuable software first.
Faster time to market and incremental delivery returns income sooner.
To realize those benefits, you and your team must develop, communicate and implement an effective agile enterprise adoption driven by a highly visible roadmap. Since the late 90s, agile adoptions have followed a ground-up and incremental funding approach as early adopters proved the benefits and scalability of agile in the enterprise. Starting in 2005, leadership-led or top-down approaches have begun to dominate the scene. These larger and more systemic approaches are required for organizations that need to act fast to derive short-term gains.
For managers and directors doing their budget planning now, the next three sections outline the proof points for agile, a roadmap to enterprise agility, and the implications on this roadmap from having to make savings cuts ahead of investment.
Proven impact of enterprise IT agility
Many large and distributed development organizations have proven the positive financial impact of agile over the past five years. These findings were quantified in the Agile Impact Report. In that study, QSM Associates benchmarked Agile teams against a database of 7,500 projects and delivered the following results. On average agile teams working with Rally were 25% more productive, had 50% faster time to market, and delivered one-fourth the number of defects. (Those teams not working got 50% of those results.)
Given those improvements, it is becoming a business imperative to adopt agility, especially on your mission-critical applications. In the face of cuts and with a long-term outlook toward enterprise agility, you can now see your way to a 25% savings in 2009.
Enterprise agile adoption roadmap
Like any mission-critical systems or initiative, you need a vision and roadmap to steer your adoption and rally the troops. During the past four years, an approach fashioned from Lean manufacturing concepts and adopted in an incremental approach has proven very effective. The following illustration depicts that method.
There are three keys to effectively managing this process:
Work incrementally, in an agile fashion, through the steps and gain proficiency before widespread scaling.
Develop a vision/roadmap and change backlog with key executives before you attempt to move up to step 3 and beyond.
Share the vision and roadmap with the entire organization and manage the rollout in a collaborative fashion with complete transparency.
Many of these rollouts have started with a grassroots effort to get to Step 1 and Step 2. With the help of external coaching and parallel tool rollouts, many companies have taken more aggressive, “flash-cut” moves with top-down leadership and investment to jump to step 3 in the roadmap within months.
Flash-cut approaches
Given the pressure and opportunity of this crisis, as well as the increasing number of public proof points showing how large organizations can quickly transition to agile, you might be thinking about your ability to do accelerate your adoption and capture savings in 2009 from your efforts. From my experience, there are three things to heed while considering this:
Adopting agile needs complete management buy-in and a true sense of urgency. Many enterprises that have done this have used phrases like “burn the life rafts.” A recent Gartner report, “Case Study: Inovis Uses Agile Methods to Accelerate Product Development,” says, “The ‘big bang’ adoption approach is high risk, but it works in companies or business units with high levels of risk acceptance, and it can manage the ensuing organizational change.” What is it going to take for your management team to get buy-in to adopt Agile on a major portion of your organization? I assume the current recession will amplify any existing business needs.
You are going to need a strategic partner to help you manage this organization change effort. I do not know a company that followed the flash-cut approach without an outside coaching or consulting firm. As a result, you will have to budget for this investment and the time to choose and schedule them. These partners will help you build the organization capacity for agile while also supporting the professional development of your middle managers as the organization becomes flatter and leaner.
This is a whole system change from a world of plan-driven to value-driven ideas. As a result, you will see immediate changes in your process, organization, and technology. This transition will set up a culture of continuous improvement and even drive changes in your overall development and business strategies. To make this transition go well, you are going to need to implement a collaborative project management solution to provide visibility across your development teams. Enterprise IT agility does not scale or distribute around the world without it.
Don’t waste a crisis
We don’t know how long or how deep this recession will be. Belt-tightening and staffing cuts almost seem inevitable. You can either reduce costs by just cutting your budget, or you can use this opportunity to make systemic changes in your business. I strongly urge you to make your cuts in parallel with investment in the long-term to avoid fixes that fail.
Provided you have a longer-term vision of your organization around agile software development, some outside coaching to help accelerate your adoption and solution for distributed management, you can take advantage of this crisis to make big changes very quickly. Enterprise IT agility is proven to do that — more so than investments in technology point solutions that only have a point in time savings. Most important, this approach will help ensure the savings from today’s cuts do not create worse problems in the long run.
RallyDev.com
Now, in 2011, we are 10 years on from the Manifesto signing, 9 years on from the first sighting of me at the folding table, and 8 years on from Ryan’s first foray into the conference.
Ryan and I never met at the 2003 conference. But in 2004, as the conference moved into the northern Rockies in Calgary, Alberta, 4 of us stood together at a folding table in a small hallway. Rally’s representation at that Agile conference was Ryan as President of the company, Richard Leavitt as our VP of Marketing and Sales, Brad Norris as our sole sales person, and me as the sole Agile Coach. At that point, none of us were speakers. However, Rally has had one or more speakers at each conference since: Denver in 2005, Minneapolis in 2006, Washington DC in 2007, Toronto in 2008, Chicago in 2009, and the 2010 event in Orlando. Additionally, Ryan served on the Agile Alliance board during the years of the Washington D.C. and Toronto conferences.
depending 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.
I just wanted to take this opportunity to thank each and every one of you who follow the Agile Blog.
And so, through discussions with Ryan and some of my own quiet thought, I came up with a goal of improving my notion of learning. Yes, for me, that seems to be what I am discovering more and more about Lean:
