Need training, coaching, or help leading an agile transformation?
email: mike@cottmeyer.com or call: 404.312.1471

Sunday, September 6, 2009

Building an Agile Book with Agile

If you were going to write a book using agile methodologies, what might that look like? You might be inclined to create a backlog of topics... maybe play a little planning poker to get some idea of how big your book is in story points. You'd start writing the book in sections... chapter by chapter... burning down your backlog as you delivered. Since you understood the size of your backlog, and you know your average writing velocity, you'd start to get a pretty good idea about when the final draft could be delivered to the publisher.


If you were running ahead of schedule, you'd be able to predict an earlier delivery date or maybe include some content that you weren't originally planning to be part of the book. If you were running behind schedule... you'd be able to make solid decisions about what to leave out. Maybe you go back to your publisher with real data about how much additional time you'd need to get the book completed. You could use all this agile goodness to really run a solid 'book writing' project.

Do you think that you'd stop there? What else could you leverage from agile methods to write your book? How would you build in quality? How would you know you were writing the right book? Over the past few months I have been thinking hard about this idea of keeping the book potentially shippable. How would we build the book in such a way that it always tells our story. If the publisher pulled the plug in a few months, how could we self-publish a shorter version of the whole book rather than be sitting on a few disjointed individual chapters.

So here is the plan. Dennis and I are working really hard on the major themes... you saw that last week in my four posts on capabilities, double-loop learning, the 7 Habits, and conversations. These themes are going to be hung on our five phase framework of team based agile, horizontal, first order, second order, and third order scaling. The final bit of work we are doing right now is around the specific organizational capabilities (and by extension, the practices) we see as essential for adopting and scaling agile at each of the five different levels.

This is the basic set of up front design work that we want to do on the book. I think of it as the high-level systems architecture. We are defining the framework, the major themes, and the significant features that are going to blend together to tell the story. Like I keep saying... all these ideas are subject to change but this helps us decide what is in-scope for the book... and what is out. There are zillions of ways to tell this story... we are picking one to start with.

Over the next week or so... you are going to see me blogging a bit around the extended book structure as my way to start telling the story end to end. We'll talk about the order of the topics and the learning outcomes for each section. By the end of this phase, you should end up with a pretty good idea of where Dennis and I are headed. That process will help us decide specifically the user stories we want to put in the backlog with a pretty high degree of confidence we are telling the right story. Then we start really writing the book.

Subscribe to Leading Agile

Interesting Post... 8/30/2009 through 9/5/2009

Wow! Have we been back from Agile 2009 for over a week now? Time sure does fly. You may have noticed that I didn't do an "Interesting Post" summary last week. It's not that there weren't any interesting posts... it's just that my Internet access was so bad in Chicago, I gave up reading blogs and Twittering. So in short... there was nothing to summarize. I came back to Atlanta with over 900 unread posts in my Google Reader. I tried to scan them for highlights... but in the end gave up and decided to 'Mark All Read' and start over!

So now we are back in the game. Here is my list of what was worth reading from over 1000+ posts across over 400 blogs. Oh, and by the way... if your blog never shows up on my Interesting Post list... you might want to check my blog roll and see if you are on it. Every once in a while someone I should be following is noticeably absent. Let me know and I'll subscribe to your feed.

Interesting Posts from 8/20/2009 through 9/5/2009

Agile 2009 and PMI http://bit.ly/fuPNS

The agile BA: lead, follow, and get out of the way http://bit.ly/9xjMN

A chat with Gordon Pask Award Winners @ Agile09 http://bit.ly/Z4X63

Agile 2009 Roundup http://bit.ly/4qhF7c

A question of fundamentals http://bit.ly/XRfdF

Words drive thoughts, thoughts drive actions http://bit.ly/IniiL

The Dangers of Hidden Talent – New CIO Series http://bit.ly/15jOpK

FeatureBranch http://bit.ly/ETdhg

ScrumButs are the downfall of agile http://bit.ly/KXomi

Agile 2009 – The General Highlights http://bit.ly/EE2ri

Agile 2009 Chicago http://bit.ly/2ziUO7

Why Tester Won’t Like Agile http://bit.ly/Na7DW

Passion and Talent http://bit.ly/e8zKN

How To Behave Like a Professional Project Manager http://bit.ly/ZeQ0A

We don't need no stinkin' process http://bit.ly/38Nd8Q

Feeding the Agile Beast http://bit.ly/14FT9r

7 habits and Agile http://bit.ly/uweck

Agile Estimating: The Secret To Delivering On Time http://bit.ly/12yYNZ

It Used to Take Three Highly-Trained Professionals to Make a Presentation http://bit.ly/2GVRXR

Staying A Specializing Generalist http://bit.ly/2N58L2

support Corey Haines http://bit.ly/HJFCn

Simplify, or the problem with Six Sigma http://bit.ly/mOSe2

Swamp Thing http://bit.ly/iScBx

Agile 2009: a retrospective http://bit.ly/9hsb6

Lean is more than a set of tools http://bit.ly/kFvof

Reflections on #Agile2009 http://bit.ly/mvj5D

Agile2009 Trip Report http://bit.ly/1iMyoz

Quote Series Part 7 - Philosophy http://bit.ly/8sTMI

Agile 2009 report: Thursday afternoon http://bit.ly/SHtAW

10 Steps for Setting up an Agile Start-up http://bit.ly/lZPrY

The Power of Simplicity http://bit.ly/2TCkC

Reflections on Agile 2009 http://bit.ly/2XjY0

Agile 2009... Thank You All http://bit.ly/pPZfI

Is software development an art or a science? http://bit.ly/dsIPx

Agile Coach Tour thoughts http://bit.ly/mehpG

Using Earned Value in a Changing Environment http://bit.ly/F4wZD

Testing vs. Checking http://bit.ly/Fn3oQ

Looking back at Agile 2009 http://bit.ly/yMTap

6 Thinking Hats Retrospective Plan http://bit.ly/E76T9

Reality check for Agile projects- working sofware over comprehensive docu.. http://bit.ly/1QhweF

Subscribe to Leading Agile

Saturday, September 5, 2009

The Big Agile Persona

A little about our intended audience...

When Dennis and I started thinking about our book, we told the publisher that we'd really like to write for CxO crowd. We want to be able to influence the people that can really effect change in a meaningful way. We want to give them the tools... the language... and thinking patterns to successfully start transforming their organizations toward a more agile way of building software.

The reality... many CxOs are not going to pick up our book... and after really thinking about it... that's not where a book like this is going to have the most impact. We need to write for the mid-level manager who has direct influence over their organization and is able to evangelize these ideas to their peers and their leadership team. We want to enable folks to act locally... but think globally. The book needs to be tactical enough to help the guys doing it and visionary enough to influence the key decision makers outside the team and up the organization.

Armed with that new bit of insight... we decided to take a page out of Jeff Patton's handbook and create a persona for the manager we think might want to read our book. We also created a profile for the target company our persona might work for. We wanted to have a really clear idea of the problems our manager was trying to solve and the resistance they might have to overcome in the process.

So like everything I've talked about the past week or so about framing this book... this is ALL subject to change. We just wanted to have a starting place for the conversation.

Frank Michaels, Development Manager

Frank is 34 years old and married with two young children. He has a bachelors degree in Computer Science from the local state university and is currently making just under 100K per year. Frank joined his company a little over four years ago as a senior developer. He is considered by his manager to be someone with excellent technical skills... an open mind... and has consistently demonstrated his ability to get things done.

After only a year, Frank was asked to serve as team lead and was recently promoted to be the team's manager. With this recent promotion, Frank has several teams under his control and more direct interaction with the other managers in his department. He coordinates with the other functional managers to drive work through the organization. He works closely with various project managers to assign resources and track project deliverables.

Frank is frustrated by the whole corporate thing and really questions his decision to become a manager. He spends way too much time in meetings and just isn't interested in all the corporate politics. It takes over a year to bring a new release to market and it seems to be getting slower. Project schedules are unpredictable and cost overruns are common. To make things even worse, quality has been suffering as pressure to deliver has gone up.

StandardCorp's Company Profile

StandardCorp is a public company that has been around for about 20 years. They grew organically for the first 10 or 15 years building software for the insurance industry. Several years ago the senior leadership team launched a strategy to grow through acquisition and they branched into the financial services sector. As of now StandardCorp is just under 5000 employees worldwide with most of their offices in North America. Product Development makes up about a third of their total employees.

As their product lines became more diverse, StandardCorp started looking for ways to leverage common infrastructure components and shared services as a way to reduce costs. The product teams began looking for ways to combine product offerings to create competitive differentiators in the marketplace. Several initiatives spun up to rationalize architectural model but these initiatives have been expensive and success has been sporadic. In fact, these initiatives have slowed down time to market and made products harder and more complicated to deliver.

Product Managers are frustrated because they used to have total ownership of the requirements and the technical teams they needed to deliver features to their customers. As the organization has grown, the delivery model has become more complex and it takes forever to get anything to market. In frustration, the product teams specify larger and larger initiatives in an attempt to get competitive feature sets to market. In response to this inability to deliver... the organization has decided to grow up. In the past year StandardCorp has made significant investment in CMMi, ITIL, and PMI Project Management as a means to get more predictable business outcomes.

Costs are going up... market share and revenue are going down. StandardCorp has already started offshoring some of their development activities and it looks like more offshoring and more layoffs are on the way.

Acknowledgments

Before we wrap, I'd like to give a special thanks to my wife Kimi. She was gracious enough to do some research for me while I was away at Agile 2009. I asked her to find information on about 10 different mid-level manager roles in a typical software development organization. She found information on Project Managers and VPs and lots of roles in between.

Interestingly enough... there were lots of similarities and overlap in terms of age, marital status, gender, and even salary. She gave me names of folks she found with links back to their original sources. Funny thing was, she actually gave me some links back to people I knew in the industry. Anyway... her research was really helpful... so I just wanted to give a nice pubic "THANK YOU" for helping me out. Thanks Kimi!

Subscribe to Leading Agile

Friday, September 4, 2009

Noodling on Kanban... Part Four

Okay... time to wrap this thing up. If you missed any of the first three 'Noodling on Kanban' posts... I included links at the bottom of this one... just to make it easy on you guys ;-)

There is clearly much more to this topic than I wanted to try and address in this tiny little series. We could talk about how Kanban drives culture... how it gives managers a role... how it is more inclusive. Karl Scotland and I debated over Drum-Buffer-Rope and how it applied to Goldratt's Boy Scout story over drinks at Agile 2009. We agreed we were splitting hairs. I tried to get David Anderson to admit that Kanban was just a visual way of managing and elevating constraints... he didn't agree.

There is lots more to say... but for the general agilist or newbie... this should be enough to start. For this post we'll wrap with some of my thoughts on what situations a Kanban might be particularly useful and what I see for Kanban outside the team. To me that is the much more interesting problem.

Time to Use Kanban?

My personal take is that Kanban... even Kanban with a capital 'K'... is not a development methodology. It is not a replacement for Scrum or XP or AUP or DSDM. I do think that Kanban is a powerful tool that can be used when some of our more common agile practices stop making sense. Consider these examples:

Have you ever tried to talk about planning in two week iterations with a team that is responsible for production support? The idea that you can't add anything to the sprint once it is started is going to fail... we'd probably abort every sprint. How about a mature product team that is iterating an existing product? Does it necessarily make sense to stop every two weeks for a few hours to plan... to retrospect? If requirements are generally understood... the team talks over lunch... and they just know how to get things done... probably not.

How about a team that suffers from late delivery in the sprint? A Kanban board can keep them focused on continuously delivering value... even if they don't do away with the iteration boundaries. What about a new team that isn't ready to self-organize or self-manage? A Kanban can give the manager a tool to help the team learn how to self-organize and self-manage. We can use Kanban as a replacement for stuff we don't need or as an addition when we need a little bit more control. Something to consider, huh?

Kanban in the Enterprise

Personally, I find most problems at the team level pretty uninteresting. It's not that team level practices aren't important... they are incredibly important... it's just that most of the teams I work with have environmental problems. If the organization would just create the team... leave the team together... let them stabilize... let them establish a pattern of delivery... most of the coaching stuff we do could work itself out. Coaches could focus on helping competent teams become excellent.

Similarly... at the team level... Scrum... Kanban... who really cares... let the team decide what works for them and go for it.

For me... Kanban gets really interesting at the portfolio level and across the enterprise value stream. Most organizations really struggle to get value flowing in a predicable way out of their enterprise project portfolios. What if we could have an enterprise Kanban... a portfolio Kanban... a project Kanban... and a team Kanban. As you go deeper into the organizational hierarchy... the work in process limits at the enterprise level force value from the portfolio... portfolio limits force value from the projects... and projects force value from the teams. Imagine a system with enterprise cycle time all the way down to team level cycle time.

Thinking about the enterprise as a series of capabilities... capabilities that together form a system... a system that can be managed and subordinated to the constraint... now that is exciting. Now we can focus our enterprise agile adoption dollars at the constrained teams and resource groups to get maximum value from our investment dollars. That is where I'd like to see us to start talking about Kanban.

Hope you enjoyed this series of posts. Make sure to comment if you think I've got this all wrong... I am open to your feedback. Oh... and here are the links for your reference:

Noodling on Kanban... Part 1
Noodling on Kanban... Part 2
Noodling on Kanban... Part 3

Subscribe to Leading Agile

Thursday, September 3, 2009

Noodling on Kanban... Part Three

Earlier today we noodled on the secret sauce... maybe even THE most important value add... of implementing a Kanban system. Kanban gives us a very visual way of identifying and elevating the constraints in our system. The ONLY way to really get a team to go faster is to increase capacity at the constrained steps in the development process. Building inventory in other parts of the system leads to waste and re-work.

If you get nothing else out of this little series... that is your take-away.

For today... we are going to talk about going iterationless. So far we haven't really talked about the iteration but most Kanban teams have figured out how to live without them. We'll talk a bit about how to measure progress without being able to measure velocity at iteration boundaries. Without iterations... without velocity... we need another measure of team throughput.... and that is where cycle time comes in.

Going Iterationless

While agile is fundamentally designed to accommodate change, the idea of an iteration implies some degree of certainty about what it is you plan to build, even if that certainty is only two to four weeks into the future. In some environments customers can't wait until the iteration boundary to introduce changes. In some environments requirements cannot be neatly fit into a consistently sized window of time.

This understanding has led some teams to abandon the iteration all together and now consider planning at iteration boundaries to be a wasteful activity. These teams have opted toward working directly from the prioritized product backlog and only bringing new work to the team when the work in process limits allow a new feature to begin. Agile introduced the idea of small batch sizes by limiting the amount of work that could be pulled into the iteration. Kanban teams take this approach to the extreme and reduce the batch size at any one time to that of a single user story.

Teams that implement this approach have ad-hoc planning meetings when the team is ready for new work. They conduct periodic operational reviews to asses team performance, communicate with management, and evaluate the overall health of the system. Teams choose appropriate boundaries for traditional retrospectives but they are not necessarily tied to the operational review or any predetermined time-box.

Velocity versus Cycle Time

Agile teams become predictable by stabilizing the size of the product backlog and establishing a consistent velocity over time. We can assess the delivery date of a fixed scope product backlog by dividing its total size by the velocity of the team. Likewise, we can use velocity to make trade-off decisions when trying to manage to a fixed delivery date release. Without the iteration, there is no longer a fixed period of time from which the team can measure team velocity.

Kanban teams replace velocity with the notion of cycle time. Cycle time measures the total elapsed time from when the feature was started until it is marked complete and accepted by the customer. Cycle time can be useful for predicting delivery and making both short-term and long-term customer committments. Becuase features are independent and not allocated to a fixed scope sprint, the team can always work on the highest priorities of the business.

Many Kanban teams will track the cycle times of similarly sized stories, making a distinction between the cycle time of a one-point story versus the cycle time of the other possible story point values. If the team becomes proficient at breaking down user stories into similarly sized increments of work, estimation is no longer even necessary, and cycle time becomes the only metric necessary to measure the delivery capability of the team.

What's Next

The next and final post in this series will talk a little about why you might want to choose Kanban and a bit about Corey Ladas' work on Scrumban... an interesting hybrid of Scrum and Kanban for teams in transition. We'll also hit a little on some work I am doing with a couple clients to introducing Kanban boards for project/portfolio management.


Subscribe to Leading Agile

Agile Chronicles has Moved!

Hey... most of you guys know that I write both here and at Agile Chronicles. But... did you know that I'm not the only one who writes for Agile Chronicles? We've got quite a few folks that post every now and again... and every one of them is worth reading. Here's the deal... VersionOne upgraded our blog and we have a new look... a new URL... and a new RSS feed.


I strongly encourage you guys to head over to blog.versionone.com and pick up our new feed. If you are only reading me here... you are missing out on some great content.

Subscribe to Leading Agile

Noodling on Kanban... Part Two

Okay... time for part two in my Noodling on Kanban mini-series.

Yesterday we talked about the Kanban board and how it was similar, but not the same, as the Scrum task board. We also talked about work in process limits and how they can be used to explicitly control the flow of value delivered by the team. This post we are going to explore the idea of constraints and how Kanban handles the division of labor on the team. So without further adieu... constraints and labor.

Constraints

So this is how it works... we’ve got the board and we’ve got the work in process limits. As work moves through the team it is possible that certain steps in the development process might become bottlenecks and constrain the flow of value through the system. For example, the team might be dependent on a person who is not part of the team to deliver a particular feature. If that person is not available to assist them team, the work in process limits will prevent more work from being started until that constraint is removed and value is able to flow from the team once again.

Constraints are those steps in the process that are limiting the team’s ability to get completed backlog items through the system. The Kanban board forces us to stop taking on more work until we get the problem with our constraint fixed. By focusing all our attention on the constraint... we work together until the impediment is removed. Work in process limits encourage everyone to work as a team and prevent any one individual from getting too far ahead of everyone else.

Fundamental to the idea of managing constraints is the notion that any partially completed features are considered inventory and could potentially lead to waste. Our goal with a Kanban system is to limit the team’s ability to create inventory and increase the likelihood team members are doing work that will result in value in the shortest amount of time possible. Kanban systems elevate constraints and force the team to address them before they can bring additional work into the queue.

For a great visual representation of this whole process, go visit Henrik Kniberg's blog post... One Day in Kanban Land.

Reasonable Division of Labor

Some teams that encounter a Kanban board for the first time note that the columns seem to reflect a waterfall style process mapping. The reality is that requirements have to be analyzed and designed before they can be built and tested. The problem with waterfall is that teams work in large batches, doing all of one phase before beginning the next. In traditional methods, there is typically a high degree of specialization amongst team members and an excessive number of handoffs between teams as work moves through the system.

The Kanban board acknowledges the phases a backlog item must go through in the development cycle, but like mainstream agile, encourages small independent user stories that are developed in small batches. The columns on the Kanban board do not represent strict hand-offs between team members but more the feature's state during that time in its development lifecycle. While Kanban teams can accommodate a reasonable division of labor, Kanban teams are still typically made up of specializing generalists. Having specializing generalists on the team reduces skill-set dependencies and levels the flow of work across the team.

Kanban, like Scrum, leaves it to the team to decide how work moves through the system and doesn’t explicitly assign work to an individual with a specific skill-set. The Kanban board does acknowledge the reality of intermediate development states, and through the use of work in process limits, explicitly controls the amount of work in each state. This allows work to be managed, helps identify constraints, and provides visibility so the team can determine which impediments should be dealt with next.

The next post in this series will address going iteration-less and replacing velocity with cycle time. We'll close after this next one with some thinking about when you might consider using Kanban and maybe even introduce some advanced contexts I find particularly interesting.

Subscribe to Leading Agile

Wednesday, September 2, 2009

Noodling on Kanban... Part One

For the next few posts I want to explore some of my thoughts on Kanban. Like many in the community, I started thinking more about this during the Lean/Kanban Conference down in Miami. On the heels of that conference I did an exploratory post on some of the similarities and differences between Scrum and Kanban. The post addressed how Scrum and Kanban (in principle) were not all that different and how Kanban makes some things explicit that Scrum leaves up to the team.

There are a lot of things I consider myself pretty knowledgeable about... but on the whole... I am not certain Kanban is really one of them. David Anderson wasn't sure he agreed with my conclusions about Kanban… but didn’t totally slam the post… so I took that as a small victory ;-) For the real experts... you do need to go hear what David Anderson, Corey Ladas, Karl Scotland, David Laribee, and Henrik Kniberg have to say about all this. These guys are in the thick of the Kanban movement and most of what I know comes through them.

That said... I fancy myself pretty good at figuring stuff out and understanding what is most important. I am also pretty good at communicating complex ideas in a way that others can understand. So with that little bit of confidence (bravado) I am going to take another stab at explaining what I think is essential about Kanban… what tooling and principles I think are most important… and explore a bit how we can use these ideas to help our organizations become more effective.

Kind of like my first post on Kanban… I believe it is helpful to start from a shared foundation and bridge into the new ideas. My opinion is that there are five or six things... right out of the gate... that we need to know about Kanban to be knowledgeable of where it fits and how we can use it to our advantage in the enterprise:

The Kanban Board

The Kanban Board is a tool that helps the team visualize the flow of value through the development process. If you have used a Scrum task board you should be pretty familiar with the general concept behind the Kanban Board. There are sequenced columns that represent the states a work item can have at any one time. As work progresses through the development lifecycle, the card is moved from one state to the other, until it has been accepted by the customer.

The primary difference between task board and the Kanban board is that the Kanban board tracks the flow of user stories through their development cycle and is not concerned with tasks. This is significant because now the team is focused on the value creating item, the user story, rather than the activities required to deliver that value. Only when the entire user story makes its way through the Kanban board have we delivered value to the customer.

A simple Kanban Board might have a column for the backlog, work in process, and the work completed. A more complex Kanban board might break out the work in process column to include dedicated areas for each of the steps in a typical development lifecycle: analysis, design, develop, code, and test. Some Kanban boards will include columns for buffers between the various states depending on the needs and process maturity of the team.

Work In Process Limits

Kanban is more than just a way of visually tracking progress at the user story level. The Kanban board is intended to help the team minimize waste, focus on the most important work, and keep the value flowing through the team. The Kanban team accomplishes this by setting work in process limits for each column of the Kanban board. Work in process limits effectively restrict the amount of work that can be in any one state at any one time.

One common failure mode in Scrum is late delivery within the sprint. Late delivery means that all the backlog items were in process during the sprint but were only fully done and accepted in the day or two prior to sprint closeout. Late delivery introduces risk, tends to destabilize velocity, and results in delayed value delivery to the customer. Scrum addresses this by encouraging team members to work together on only a few backlog items to completion before starting new work.

Kanban takes this implicit guidance and makes it explicit by setting a limit on the number of work items that can be active at any one time. By limiting the amount of work that is in process, the team is forced to focus on getting backlog items fully done before new work can start. These limits can be determined by the team, or by their management, in ways that optimize the flow of value and reduce the number of intermediate work products.

So... What's Next?

The next post in this series will address constraints and a reasonable division of labor. After that we'll discuss doing away with iterations and replacing velocity with cycle time. We'll close with some discussion around why a team might want to consider using Kanban (over basic Scrum) and a little on where I see Kanban being used outside the team in more of an enterprise portfolio context.

Until next time...


Subscribe to Leading Agile

The Conversation Conversation

For the final cross-cutting theme in "Rethinking the Agile Enterprise"... Dennis and I are going to talk about talking.

In other words we are going to explore how organizations talk to each other when delivering work. We plan to integrate the idea that adopting agile in the enterprise involves a series of conversations around how we are going to deliver value back to the business. Within small teams many of these conversations just happen. At scale... there are conversations that we have to make explicit... conversations that we have to plan to have so we can effectively execute.

This post is going to address 10 conversation types that organizations have to address at each of the 5 levels of our adoption and scaling process:

Purpose...
conversations about why we are doing the work we are doing. Think about things like visioning... setting the mission... and setting goals. At the team level... this is abstracted behind the Product Owner as a prioritized product backlog.

Understanding...
conversations about learning what we are going to do. Think about those conversations we have with the Product Owner before we agree to pull a backlog item into the sprint. These conversations are about getting the entire team all on the same page.

Creative Solutions..
. conversations about how we might build a particular user story. Think about those times when the team gets together to decide how they are actually going to implement a backlog item. This conversation is about problem solving.

Competing Concerns...
conversations about how to make tradeoffs. At the team level we might have to negotiate technical tradeoffs or balance what the Product Owner is asking for with the team's ability to implement. This conversation is about balancing tradeoffs.

Enrollment...
conversations about being part of the team. Does the team have the skills necessary to deliver? Are we committed to delivering the sprint objectives? Are we committed to working together and getting better over time? Here we are learning about who is on board and who is not.

Flow...
conversations about how we are going to move work through the team. Do we plan to manage this ad-hoc by swarming around backlog items or are we going to use a Kanban and set work in process limits? This conversation is about how we are going to execute the work.

Planning...
conversations about how we are going to schedule the work. When are we going to estimate the backlog? Will we track velocity or cycle time? Do we plan to do release planning or only sprint planning? These conversations are about where we need to be and when so we can manage the business' expectations.

Promising...
conversations where we say what we are going to actually do. Think about the end of the sprint planning meeting where the team commits to the Product Owner to deliver a specific outcome by the end of the iteration. These conversations are about stating our intentions.

Completion...
conversations where we state that the work is completed. In Scrum this happens throughout the sprint as the team works with the Product Owner to accept the backlog items. It also happens at the end of the sprint during the formal sprint review. These conversations are about being done-done.

Status...
conversations where we track progress. Here you can think about project burndowns, sprint burndowns, card walls, and daily stand-up meetings. These conversations help our stakeholders know where we are and the chances we are going to be where we need to be.

These conversations happen pretty naturally within a small agile team. They get dicey when you have to conduct these conversations across multiple teams... across projects or programs... across portfolios. Figuring out how to make these conversations happen at scale is part of what we have to address when learning how to adopt and scale agile in larger enterprises.

Head over to Dennis' website for a more detailed treatment of each of the 10 conversation types...

Subscribe to Leading Agile

Tuesday, September 1, 2009

The 7 Habits Conversation

Back in my late 20's a coworker suggested I read Stephen Covey's 7 Habits of Highly Effective People. Little did I know what an impact that book would have on my life. The funny thing was that my first reading didn't make all that much difference. It wasn't until I read the book again in my early 30's that it became life changing. Over the past ten years I have read the 7 Habits at least 5 times... probably more.

So often we find ourselves pushing up against walls that just won't seem to move. We are trying to change things that we are powerless to change. At the end of the day we learn that the only person you can really change is yourself... that we can really only influence those we have earned the right to influence. The 7 Habits is a book about personal effectiveness... it's about where you are now and how you get to where you'd like to be. I think that there are some powerful lessons here... and I am sure some of these ideas will become part of the fabric of our book.


Habit 1 - Be Proactive

Being proactive is about operating within your circle of influence. It's about focusing your time and energy on the things you can directly impact... rather than getting frustrated over the stuff you can't. Becoming effective where you have the most influence will result in your ability to influence more of your overall environment. Start your agile transformation where you can have the most impact and grow it from there.

Habit 2 - Begin With the End in Mind

What does your agile transformation look like when you are done? Sure... we need to get started but first we need to know what direction we are headed. We need to have some idea what the end state looks like. We need to understand our vision... our mission... our values and principles. We need to lead our organization toward that vision in a way that reinforces our desired outcomes.

Habit 3 - Put First Things First

What is the next most important thing I can work on? What are the next most important things to do that will lead me closer to where we need to be? There are many things in life that take time to make happen... things that can't just be mandated or made to happen overnight. Putting first things first means that we are going to consistently choose to work on things that will bring us closer to our goal... grow our ability to influence the organization... and get us that much closer to realizing our vision.

Habit 4 - Think Win-Win

Agile adoption and scaling is not an end unto itself. We are in a quest to deliver more value... to be more productive... to make things better for the people we work with. To be successful... everyone has to have the opportunity to be successful. We need to understand what success looks like for everyone involved and seek out solutions that optimize value for as many people as possible. We certainly want to deliver value for our customers... but also our managers, team members... and yes... even Project Managers.

Habit 5 - Seek First to Understand, Then to be Understood

It's easy for a consultant to come in and make recommendations that are totally out of alignment with your current reality. We need to spend time understanding how our teams are currently working... what things they are currently struggling with... and which opportunities for improvement are going to maximize our desired outcomes. Only then can we craft situationally specific strategies that maximize our investment in change.

Habit 6 - Synergize

Synergy is when two things come together and form something greater than the sum of their parts. In personal relationships this might mean a couple coming together to make a family or two friends working together on some massive backyard project. For businesses, this might involve people from different parts of the business. People working together to improve the overall system rather than just optimizing their individual parts. The whole system working toward a common objective is much more powerful than any one of us going it alone.

Habit 7 - Sharpen the Saw

Personal effectiveness... organizational effectiveness... depends on staying healthy and focusing on improvement and renewal. Leading change is not a one time event and your agile transformation is never really complete. We are going to learn... we are going to inspect and adapt... we are going to respond to changing conditions and guide our organizations toward greater effectiveness and continuous improvement.

Habit 8 - Find your Voice

Several years after the publication of the 7 Habits... Stephen Covey published a book called the 8th Habit. This is another book that took me several readings to fully get its impact. The 8th Habit is about leadership... it is about empowering people... aligning people... respecting people and treating them like whole thinking... feeling... human beings. It's about tapping into the untapped human potential that lies dormant in many of our organizations. I think that's a pretty agile way of thinking about things...

I doubt Stephen Covey would consider himself an agilist in our sense of the word. I don't know if he ever managed an iterative software development project. But to me... that is what is really cool about all this stuff we talk about... the values are transcendent... they apply in every problem domain. We are bringing universal truths to play in our work and making life better for everyone involved. I doubt these ideas will be directly referenced in the book... but they are a part of who I am... and I am sure they will become part of the fabric... part of the thinking framework.

Related Post:

Subscribe to Leading Agile