A Recap of Lean Agile DC 2018
CC Pace spent an informative day at the Center for Innovation Technology (CIT) event in Herndon, VA: Lean Agile DC. Jason Velentino (Director, Digital Reliability Engineering at Capital One) kicked off the conference with a great presentation on DevOps and his journey through incorporating cloud and a DevOps culture at such a large organization. It is rewarding for CC Pace to have been a part of the Agile adoption at Capital One, providing Agile Coaching and Training over the past five years and to see the evolution of Agile, which Capital One has made part of their everyday culture.
Another great presentation and discussion on Agile Engineering was lead by Jose Mingorance, and Carlos Rojas of Fannie Mae. They have pulled together a lot of ideas from Agile leaders to provide Fannie Mae with an exciting assessment and plan to drive business value throughout their organization through advancing Agile engineering practices. It was interesting to see their plans and the excitement surrounding this initiative.
Finally, Dean Chanter, also from Capital One, lead a great discussion on Joshua Kerievsky’s Modern Agile principles. Dean spoke about his journey towards ‘modern Agile’ at Capital One and how those principles are at the cornerstone of their advancement in their Agile transformation as an organization. As Capital One continues their trajectory into being Agile leaders in the Financial Services market, this will be an interesting case study to keep an eye on! We look forward to next year and seeing how everyone has progressed.
A long while ago, the Boston Consulting Group (BCG) pushed its limited and ill informed conception of Lean by focussing on waste elimination. It defined what most of us believe Lean to be to this day.
Six Sigma, with relatively good mathematical science – but not perfect according to Donald Wheeler – jumped on the bandwagon of certifications with its famous – and no less dogmatic & command and control – belt structure. Although Six Sigma always quotes chapters and verses from the statistical work of the likes of Donald Wheeler, we never heard the likes of Wheeler endorse ‘Sick Stigma’ (a term borrowed from Dave Snowden) ! (Having read all of Wheeler books, I never saw a reference to Six Sigma anywhere)
A recent study from QualPro, a consulting firm that advocates an alternative quality process, points out that 53 of 58 large companies that use Six Sigma have trailed the S&P 500 ever since they implemented it. As if on cue, once-mighty proponents of the program have begun to scale back their involvement, if not abandon it outright. Two of the most recent dropouts: 3M and Home Depot. In fact, Robert Nardelli, the former CEO of Home Depot, was forced out in part because his Six Sigma program was blamed for plummeting customer satisfaction and employee morale. At 3M, management is rolling back many Six Sigma initiatives: The program, it decided, was not compatible with the spirit of innovation that had once made 3M great. Invention is an inherently risky, wasteful and chaotic process—exactly the sort of stuff Six Sigma seeks to eliminate
Coming back to software development, those 7 wastes were the focus of the earlier book by Mary and Tom Poppendieck, where both merely transposed the 7 wastes as it were to software development. Later books proved to be better aligned with the essence of value creation, which is the foundation of Lean.
The essence of Lean, as depicted by David Anderson’s lean decision filter, is where we should stand : a) Value trumps flow, b) Flow trumps waste elimination, c) Waste elimination trumps economies of scale.
Waste elimination is a distant third focus. But neither BCG nor Six Sigma truly understood the spirit of Lean.
Lean Kanban University’s teachings focus on Value first where the flow of work is visually illustrated with the dominant knowledge activities driving product development. Waste is of course addressed in a system’s thinking approach inspired from the scientific work of Goldratt and Demings.
You can hop in anytime and learn more by clicking
Daniel Doiron is an Accredited Kanban Trainer (AKT) who works closely with CC Pace to deliver Kanban training and coaching to our clients.
“Once I started looking around behind the port frames, I figured I could just….”
And so began a summer of endless sailboat projects and no sailing. One project lead to the start of another without resolving the first. What does this possibly have to do with software development and Agile techniques?
My old man and I own and are restoring an older sailboat. He is also in the IT profession, and is steeped in classic waterfall development methodology. After another frustrating day of talking past each other, he asked how I felt things could be handled differently in our boat projects.
“Stop starting and start finishing!”
It is the key mindset for Agile. Take a small task that provides value, focus on it, and get it done. It eliminates distraction and gives the user something usable quickly.
Applying this mindset outside of software may not be intuitive, but can pay dividends quickly. On the boat, we cleared space on the bulkhead, grabbed a stack of post-its and planned through the next project, rewiring the boat. The discussion started with the goal of the project. “We’re just to tear everything out and rewire everything.” Talk about ignoring non-breaking changes! I suggested that we focus on always having a working product – a sail-able boat – and break the project into smaller tasks that can be worked from start to finish in short, manageable pieces of time.
Approaching the project from that angle, we quickly developed a list of sub tasks, prioritized them, and put them up on our make-shift Kanban board. This was planning was so intuitive and rewarding on its own that we did the same for other projects we want to tackle before April.
So stop starting, start finishing, and start providing value quicker for your stakeholders.
Outside of my work at the MSRB for CC Pace, I enjoy working with community organizations in Fairfax County. After eight years of running the Jefferson Manor Civic Association, I was named Chairman of the Lee District Assoc. of Civic Orgs (LDACO). This is an organization focused on improving communications between residents in the Lee District section of Fairfax, and the elected officials and staff of the county. I have been involved with the board of directors for several years, and was bursting at the seams with ideas on how to build on the foundation I had inherited.
The nearly unlimited options quickly brought about a familiar end result – paralysis. Ideas ranged from simple house-keeping to epic public festivals. It was, to be honest, complete chaos.
Thankfully, at the time I was working on my understanding of Agile techniques and how they applied to my work situation. A key source for this was ‘The Nature of Software Development” by Ron Jeffries. As the pages flew by, the point of always prioritizing value became clear. How could this perspective be focused on running an advocacy group for civic associations? The clouds parted and the way forward became clear.
Prioritize by what would provide immediate value to the organization and its members. Again referring to Jeffries, I used the “Five Card Method” to determine what our first ‘epics’ to tackle would be. The idea is pick three to five big ticket items that will provide immediate value, and focus on breaking those down into manageable pieces.
How do we determine what our members find valuable? Ask them. A review of LDACO’s contact list showed that it was incomplete and in some cases, outdated. We had no social media outreach, either. Improved, direct communication became epic #1.
Talking with leaders in other communities, as well as long standing members of LDACO, I learned that folks needed a longer lead time to plan on attending our meetings. Epic #2 was to provide a calendar of events with at least 90 days out.
Lastly, LDACO learned that our members wanted a district and county-wide focus for meetings and speakers. While having a very narrow topic may provide value for a single community, it did not translate to the diverse group as a whole. Epic #3 was to aim for big, broad topics with speakers who were involved in the decisions that impacted the largest number of communities.
These became the main focus of LDACO’s work for the past year. These were broken down into smaller, achievable pieces, then worked on and completed. In the past year, we have grown our communication list, begun to grow on social media, and increased our attendance and membership through meetings with important stakeholders. All because we kept the focus on what provided value for our customers.
Have you heard that not all Agile Transformations are successful? Have you wondered what makes some transformations more successful than others? Are you wondering if your organization can be successful?
Here is a little analogy to think about. I recently lost 40 pounds on an eating transformation plan, or more simply a diet. I don’t like to call it a diet, because if I ever go back to my old way of eating I’ll likely gain my weight back. Also if I don’t follow the basic guidelines of the diet, I may not lose weight at all. So what does this have to do with being successful at Agile?
When organizations pick and choose what principles to follow in Agile, it’s like low carb dieters choosing to still eat potatoes, or white bread on their diet. While they may see some improvements, overall they are not setting themselves up for success on this plan. The diet gets blamed rather than how the dieter chose to implement the diet.
When preparing for a transformation, the first step is to get the foundational pieces right. Learn about the plan. Prepare your house by cleaning out your cupboards and fridge, and shop for the good stuff to replace the bad stuff. Learn what the rules of your plan are, and set a date to begin. Note, a new eating plan works better if everyone in the house is on the same plan! Then measure the results, and make corrections as needed.
In an Agile transformation, the steps are much the same. Identify what method you want to follow within the Agile framework. Get everyone onboard by helping them learn about the methodology. Prepare your “house” by looking at the organizational structure and identifying what will work within the transformation and what won’t. Make a decision to replace the practices that don’t fit in the transformation with practices that will support a successful transformation. Inspect and Adapt to keep improving and making course corrections along the way.
So what if your organization doesn’t want to follow the plan to the letter? It’s OKAY… BUT the organization needs to know the impact of alterations in the plan. If I can’t give up my potatoes what does that mean? Will I see the same success rate? How can I compensate for keeping my potatoes?
Some Agile principles are more easily adapted than others. I can counteract teams not being co-located for “face-to-face” interactions, by providing great tools for them. I can bring those team members together for planning sessions, or other occasions to help build the team rapport, and offset the lack of co-location. Other principles aren’t so easily adapted. A poor company culture where trust and empowerment are lacking, may prove to be too much to overcome, leaving the organization with unmotivated and un-empowered teams.
If your transformation has hit a plateau, or doesn’t seem to be working. It may be time to take a look at how you are following the new plan, and where your potato-eating cheats are causing you bloat, and derailing your success. It may not be the method, but rather how you are following it.
I’m just returning to work after Spring Break in Cancun. I’ve met some lovely people while enjoying the sunshine. As I chatted with those beside me at the beach and alongside the pool, two common questions are asked: What is your name? and What do you do for a living? The answer to the first question is easy, but the answer to the second question is much longer. Why? Because I can’t just stop with “I’m a trainer”. I enjoy talking about Agile and Scrum, and explaining the basic framework. I enjoy sharing with others how they can apply what I teach to just about anything. I enjoy sharing Agile stories because Agile works, and I like talking about how companies can adopt an Agile mindset.
When I start talking to someone about Agile, I begin by explaining first how past processes have fallen short. The trials and tribulations of a 1 or 2 year project plan, managing risk, reaching or missing milestones, and change requests to re-baseline the plan for any number of reasons come to mind. All with a real concern of delivering something that misses the mark in “delighting the customer”. Waterfall projects often have cost overruns, extended delivery dates, and a plethora of change requests that aren’t discovered until near the end of the project during User Acceptance Testing (UAT). For these reasons, Waterfall just doesn’t feel like the best choice to deliver software anymore.
I then move on to talk about why I, and so many others, choose Agile processes to build software today. So here is a little of what I talk about:
- Continuous engagement with the customer and other stakeholders is key
- Seeing progress through continuous delivery enables better feedback
- Reduced risk and waste, which can save money and heartache
- Adapting to change quickly, which allows for the customer to respond to market changes
- Better quality deliveries by testing early and often
- Happier employees as a result of practicing the 12 Agile Principles
It isn’t magic, and it isn’t necessarily an easy transition to make. To become a truly Agile organization takes a true shift in how we and everyone else in our organization thinks about how work is performed both internally, and externally with our customers.
Yes, I am a bit of an evangelist. Sometimes I want to shout from rooftops “people get it together, follow Agile principles”, “walk the talk”, “quit being stuck in the past”. Our world is evolving every day. To keep pace with our competitors, we need to evolve too. Agile is an umbrella term for a number of methodologies including Kanban and Scrum. Today we find that Agile isn’t just for software anymore. The principles and methods can be followed just about anywhere to greatly improve our ability to deliver just about anything. That’s why I’m not just a trainer, but a believer.
When our yacht club saw membership dropping and was looking for a change, I called our Chairmen of the Board and suggested… a Kanban board.
Lucky for me, our Chairmen works in software for a well know online travel site. He knew just what I was talking about. After a short discussion, we decided to introduce the ideas of Scrum to the board. At our next Board of Directors (BoD) meeting I turned up, white board and 3 x 5 cards in hand.
Together we introduced the BoD to the idea of using a Scrum board to track our work. We started by brainstorming ideas in two key categories supporting the club’s 2015 goal of Membership retention and growth. Our two categories are membership activities and building improvements. After creating quite a backlog for the club, we discussed priority, and arrived at a commitment to working on a subset of the backlog for the upcoming sprint. Our sprint cycle was easy to determine as there are two meetings a month at the club, providing approximately 2 weeks in between each meeting. Board members signed up for stories listed in the backlog to get us off and running. At our general membership meeting, the visual board with our sprint and “product” backlog were introduced to the club.
Being “Agile” is a way of thinking. Core ideas like transparency, prioritizing, and collaboration can be incorporated into our everyday lives. I often suggest using a visual board for household chores when I’m doing training. No more nagging your partner, or kids. Just keep a board with 3×5 cards or post-its to identify upcoming work. Identify priority, acceptance criteria, and limit your work in progress by identifying a sprint length (one – two weeks work well). This helps to keep from feeling overwhelmed. Everyone is happier knowing what is expected. I’ve tried this at home with good success which is what led me to suggesting this for our club.
In taking these same principles and applying them to our club, we’re able to benefit from being Agile. The club members are our customers. They get visibility and input into the work being done. Members can make suggestions for new work, and volunteer to help. The club’s budget helps identify what can be afforded, and expected ROI helps us prioritize. Our initial work is underway, and I look forward to seeing our long-term projects lead us to sustaining and even growing our membership.
A colleague recently reached out for suggestions to help a new client whose teams are having trouble adapting to using story points.
Here are 10 tips to keep in mind when helping teams in their transition:
Change the Language – Are We Estimating Effort or Estimating Size
Story points are intended to reflect relative size. And while they are loosely correlated to effort (e.g., the bigger something is, the more effort it takes to do it), they are not meant to represent a precise measure of effort.
If your teams are grappling with estimating-in-story-points, try changing your language to sizing-in-story-points. It’s a subtle difference for those of us familiar with the concepts, but can ease the transition for those new to it.
Create New Language – Stay Away from Numbers
Historically, we think of size in terms of how-long it will take to do it. Break that strong association by using a non-numeric, relative scale such as t-shirts, dogs, boats, planes, fruits, vegetables, candy, or planets.
Clarify Language – Are We Talking Effort or Duration
Let’s take a simple example…..I have a friend who can drive across country in 3 days by herself. It takes me a week. Assuming we’re taking the same route, and driving the same speeds, why is there a difference? It turns out that my friend can drive 12-13 hours a day with minimal stops. Whereas I start falling asleep after 2-3 hours and have to stop frequently. So it takes me longer (duration) to do the same amount of work (effort).
Duration is the time it takes to complete something from start to finish and is stated in “duration-units” such as hours, days, weeks, or months. Work (effort) is the amount of work required to complete something and is stated in “work-units” such as man-hours or man-days. Because these both have a “time” component, we often mingle them together inappropriately, causing problems if there’s not a clear, shared understanding.
For instance, when I estimate a task to be 40 hours, what I mean is “it will take me 40 man-hours to do this, if I have the information and decisions I need in a timely manner, if tools are available when I need them, and if I’m not working on anything else”. What others often hear is “it will take someone a week to do this”. I’m talking about effort; others are hearing duration.
The teams my colleague observed used the following definition when estimating their stories:
1 SP = 3-4 days
2 SP = 1 week
3 SP = 2 weeks
5 SP = 4 weeks
8 SP = 6 weeks
They are tracking actual hours worked on each story and are expecting that a 2-point story equates to a consistent number of hours. But their definition is expressed in duration-units rather than work-units, and the actual effort to complete a 2-point story can vary widely depending on whether one person can finish it in a week or it takes 4 people to complete it.
Don’t define story points in duration-units and expect it to correlate to effort.
Skip Estimation, Go Directly to Work
If your teams are thrashing because of estimation, then don’t estimate. Use commitment based-planning and have them track their story throughput rather than points or hours. As they become more comfortable with this, stories will begin to creep smaller and smaller naturally. Check out more about the #NoEstimates movement.
Compare to a Baseline
Have the team select a story that is representative of the type of work they do, assign a size to it, then compare all other stories relative to the baseline.
The more the team does what’s uncomfortable for them, the more practice they get, and the better they will get at it. Opt for shorter iteration lengths, as this will offer more opportunities to practice.
If teams are thrashing, there may be too many changes happening at once for them to absorb. We’re looking for the creativity and speed that comes from being on the edge of chaos, not in the middle of it.
Focus efforts on improving the ability to create vertical slices of value.
Once teams can craft valuable slices, focus on reducing the variability in story sizes rather than thrash about estimating. Strive for small stories using story-splitting techniques. Smaller slices are easier to size, easier to finish, make mistakes visible sooner, and allow for quicker feedback. Smaller stories also improve the flow of work.
As stories become small, uncertainty and dependencies decrease, and effort and duration can be good approximations of each other. A rule-of-thumb is a story should be small enough to be completed in less than 1/3 the length of your iteration, e.g., no longer than 3-4 days in a 2 week iteration. Mature teams will often have stories that take around one day, and all their stories are of similar size.
Remember – it’s the Conversation that’s Important
The magic about relative estimation is not in getting to an answer, but in the conversation that leads to shared understanding.
And…don’t Over-Stress the System
No matter what anyone thinks, pressuring a team to accept 800 hours of “planned” work when they only have 500 hours of capacity is not reasonable, and it will never work. Forget the “if you challenge them, they will rise to the occasion” call to arms. After a certain point, that’s just a bunch of malarkey.
As my grandma used to say, “You can’t get blood from a turnip”.
As I mentioned in the introductory post in this series, an issue I frequently see with underperforming Agile teams is that work always spills over from one iteration into the next. Nothing ever seems to finish, and the project feels like a waterfall project that’s adopted a few Agile ceremonies. Without completed tasks at iteration planning meetings (IPMs), there’s nothing to demo, and the feedback loop that’s absolutely fundamental to any Agile methodology is interrupted. Rather than actual product feedback, IPMs become status meetings.
In this post, let’s look at how a Product Owner can help ensure that tasks can be completed within an iteration. As a developer myself, I’m focusing on the things that make life easier for the development team. Of course, there’s a lot more to being a good Product Owner, and I encourage you to consider taking a Scrum Product Owner training class (CC Pace offers an excellent one).
First and foremost, be willing to compromise and prioritize. An anti-pattern I observe on some underperforming teams is a Product Owner who’s asked to prioritize stories and replies, “Everything is important. I need everything.” I advise such teams that when you ask for all or nothing, you will never get all; you will always get nothing. So don’t ask for “all or nothing”, which is what a Product Owner is saying when they say everything has a high priority.
As a Product Owner, understand two serious implications of saying that every task has a high priority.
- You are saying that everything has an equal priority. In other words, to the developer team, saying that everything has a high priority is indistinguishable from saying that everything has medium or indeed low priority. The point of priority isn’t to motivate or scare the developers, it’s to allow them to choose between tasks when time is pressing. You’re basically leaving the choice up to the developer team, which is probably not what you had in mind.
- You’re really delegating your job to the developer team, and that isn’t fair. You’re the Product Owner for a reason: the ultimate success of the product depends on you, and you need to make some hard choices to ensure success. You know which bits of the system have the most business value. The developers signed on to deliver functionality, not to make decisions about business value. That’s your responsibility, and it’s one of the most important responsibilities on the entire team.
The consequence of “everything has a high priority” is that the developers have no way to break epic stories down into smaller stories that fit within an iteration. Everything ends up as an epic, and the developer team tends to focus on one epic after another, attempting to deliver complete epics before moving on to the next. It’s almost certain that no epic can be completed in one 2-week iteration, and so work keeps on spilling over to the next iteration and the next and the next.
Second, work with the developer team to find out how much of each story can be delivered in an iteration. Keep in mind that “delivered” means that you should be able to observe and participate in a demo of the story at the end of the iteration. Not a “prototype”, but working software that you can observe. Encourage the developers to suggest reduced functionality that would allow the story to fit in an iteration. For example, how about dealing only with “happy path” scenarios – no errors, no exceptions? Deal with those edge cases in a later iteration. At all costs, move towards a scenario where fully functional (that is, actually working) software is favored over fully featured software. Show the team that you’re willing to work with the evolutionary and incremental approach that Agile demands.
Third, be wary of stories that are all about technical infrastructure rather than business value. Sure, the development team very often need to attend to purely technical issues, but ask how each such story adds business value. You are entitled to a response that convinces you of the business need to spend time on the infrastructure stories.
At the end of a successful IPM, you as the Product Owner should have:
- Seen some working software – remember, fully functional but perhaps not fully featured
- Offered the developer team your feedback on what you saw
- Worked with the developer team to have another set of stories, each of which is deliverable within one iteration
- Prioritized those stories into High, Medium, and Low buckets, with the mutual understanding that nobody will work on a medium story if there are high stories remaining, and nobody will work on low stories if there are medium stories remaining
- A clear understanding of why any technical infrastructure stories are required, and what business problem will be addressed by such stories
Finally, make yourself available for quick decisions during the iteration. No plan survives its first encounter with reality. There will always be questions and problems the developers need to talk to you about. Be available to talk to them, face to face, or with an interactive medium like instant messaging or video chat. Be prepared to make decisions…
Developer: “Sorry, I know we said we could get this story done this iteration, but blahblah happened and…”
You: “OK, how much can you get done?”
Developer: “We would have to leave out the blahblah.”
You: “Fine, go ahead.” (Or, “No, I need that, what else can we defer?”)
Next post, I’ll talk about what developers should concentrate on to make sure some functionality is delivered in each iteration.
In previous posts, I talked about what the “Get It Done” (GID) and “Just Do It” (JDI) patterns look like in organizations. Today I’ll talk about another cultural pattern.
“MAKE IT SO”
If you’re a fan of “Star Trek: The Next Generation”, then you’re familiar with this phrase. I can see it now….Captain Jean-Luc Picard standing on the bridge of the U.S.S. Enterprise, facing a situation requiring action. He asks for options, listens to recommendations, and conveys a decision to move forward by telling the crew to Make-It-So. His decision communicates “what” needs to happen, but he trusts the crew to figure out “how”. This is the essence of a Make-It-So (MIS) culture, a pervasive attitude of leadership throughout an organization, resulting in an environment that supports growth, encourages exploration, demands excellence, and emphasizes accountability.
In an MIS culture, everyone has a place in the fabric of the organization….they are valued and valuable, and they know it. Everyone has an important part to play….and they are expected to play it. People are skilled and competent….and because they are, they’re confident. People are empowered, they are “granted permission” to contribute ideas, to make decisions, to take risks…to “make it so”.
Ten characteristics I’ve experienced in an MIS culture include:
“When nothing is certain, everything is possible.” – Margaret Drabble
We are informed by, but not tied to, what was. We are grounded in the here and now, yet remain open to what could be. We don’t drag ourselves down with visions of doom, but maintain a sense of hope and optimism.
“Concentrate all your thoughts upon the work at hand. The sun’s rays do not burn until brought to a focus.” – Alexander Graham Bell.
When vision and purpose are visible and shared, it provides us context. We know the direction and why, so we can act and make decisions accordingly.
“No man is an island, entire of itself; every man is a piece of the continent, a part of the main.” – John Donne
We know it “takes a village” and we can’t do it alone. Success depends on the combined strengths and contributions of everyone.
“The key is to get to know people and trust them to be who they are. Instead, we trust people to be who we want them to be, and when they’re not, we cry.” – David Duchovny
We trust in each other’s positive intent, and believe everyone does the right thing at the right time with the information they have. We act, make decisions, and move on. While we reflect on what we learn from experience, we don’t undermine confidence by second guessing ourselves or others.
“It’s not what we profess, but what we practice that gives us integrity.” – Sir Francis Bacon
We seek to know ourselves, to be ourselves, to be proud of ourselves, our organization, our place in it, and our contributions. Our actions are congruent with who we are, our beliefs, our passions, and our strengths. We own our decisions and choices, and their consequences.
“Talent without discipline is like an octopus on roller skates. There’s plenty of movement, but you never know if it’s going to be forward, backwards, or sideways.” – H. Jackson Brown
We strive for excellence, and excellence requires discipline in little things on a daily basis.
“There is no such thing as a “self-made” man. We are made up of thousands of others. Everyone who has ever done a kind deed for us, or spoken one word of encouragement to us, has entered into the make-up of our character and of our thoughts, as well as our success.” – George Burton Adams
We grow through support and encouragement, which helps us spread our wings, improve, gain confidence, and reach our potential.
“We need to give each other the space to grow, to be ourselves, to exercise our diversity. We need to give each other space so that we may both give and receive such beautiful things as ideas, openness, dignity, joy, healing, and inclusion.” – Max de Pree
We know that too much sameness stagnates an organization, so we explore and leverage differences to open the door to possibilities.
“Courage does not always roar, sometimes it is the quiet voice at the end of the day saying “I will try again tomorrow.”” – Mary Ann Radmacher
The rewards are greatest when we take chances, risk exposure, and step outside our comfort zone. Leaders nurture and reward courage.
“The secret of life, though, is to fall seven times and to get up eight times” – Paolo Coelho
It’s not just a matter of having the will to get back up and keep on going. We must also have the “health” to do that. As an organization and as individuals, we take care of ourselves so we can continue to bounce back.
An organization which cultivates an environment like this, is one where people are important. And when people are important, they collaborate, they innovate, they adapt quickly to change, they “dare greatly”…..and amazing things happen.
Gee, that sounds an awful lot like an Agile environment!
What do you think?
Agencies around the government are beginning to see more and more of their employees teleworking and going to modified work weeks. There are a number of employees that work enough so that they can modify their schedules to be off every other Friday or Monday, or even every Friday or Monday. Due to a number of factors, many employees are also teleworking, or working from home. Sound like you or someone you know?
What does this have to do with Agile?
I hear very often that one of the most talked about, and even controversial, things about an Agile transformation is the idea that teams must all be in the same room in order to satisfy the 6th principle of the Agile Manifesto “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.”
If we take this principle into account, then we find that the telework and modified schedules turn this upside down and cause some confusion and concern on whether or not an agency can actually transition. I have had a number of federal employees, especially leadership; ask if they can really transition to an Agile culture. The actuality is “yes” – an agency in this situation, can most certainly transition to an Agile environment!
The biggest question for any agency is not “can we?”, but “how do we?”. The agency needs to start with the understanding that the 6th principle says that face-to-face is “the most efficient and effective…” way to communicate; it does NOT say that it is the only way to communicate. It is so very important to encourage face-to-face communication for those that are in the office on a daily basis, but not so important that they relinquish the teleworking or modified schedules.
The key is to have the agency give the teams as much encouragement and support as they can to help create an atmosphere that fosters communication and collaboration in many different ways. The agency will need to enable team members to communicate through means that may not have been ‘the usual’ in the agency. Many government agencies have never had to put a lot of effort into ‘unusual’ modes of communication and collaboration because either the employees have been in the office all the time and/or the employees have worked fairly independently. The more independently employees work, the less they need ways to communicate and collaborate outside of the ‘usual’ means of phone and email.
Agencies that need to step out of the ‘normal modes’ of communication are most likely very skittish of doing so for a multitude of reasons. Some reasons I have been told that agencies may be skeptical is the level of security that needs to be maintained in the agency; most agencies will admit their security levels are much higher than those of private industry. Because of the level of security that needs to be supported, many obvious communication mechanisms are overlooked or pushed aside without fully investigating the overall options.
However, in today’s technological age, there are many options that are available. Any agency that is looking to transition to a more collaborative environment, one in which Agile can flourish, needs to look beyond names and find what works. They should start by understanding the needs of the teams and work with the teams to find solutions, such as Office365, webcams, bridgelines, etc.
The one thing that agencies should never assume is that they cannot transition to an Agile environment simply due to these modified schedules or teleworking situations. It all comes down to support and encouragement of teams made of people that are not all sitting in the same location…something that many agencies have not had to deal with before now!
Have you been in this situation? Do you know some that are? What do you, or they, think can be done to be more collaborative?
Being always busy does not always mean being productive
As often happens at the end of a calendar year, many people reflect on the past and start thinking about what would make sense to do different in the future.
Recently, I was having such a contemplative conversation with a client. He asked me if I am seeing any trends with management practices that, while put in place with good intentions, have unexpected consequences or side effects. He wanted to understand if his organization’s challenges in meeting delivery date commitments and accelerating time to market are rooted more in something they do versus something they don’t do.
Utilization Vs Throughput
While there are many trends I could talk about, there is a common pattern I have seen not only in the past year, but for the past twenty years. This pattern is prevalent in silo organizations and is usually a result of good managers doing what they are expected to do: keep systems running and control or minimize costs, while maintaining organizational commitments. If managers do these things, they are “managing well”.
One way to minimize cost is to minimize waste. What do we consider one of the biggest wastes in our environments? Idle resources. We don’t want idle resources because it feels like we’re wasting money, like we’re paying them “for doing nothing”. So, managers often aim for departmental efficiencies by focusing on maximizing utilization of people in their department. In knowledge work fields like software engineering and information technology, this practice is frequently used to minimize costs within a department.
While controlling personnel costs is managed at the department level (e.g. Product Management, Project Management Office, Development, Test, Operations, Support, etc), maintaining organizational commitments can be achieved only through synchronized efforts across departments.
Although not readily apparent, this creates a conflict because the organization’s throughput is deeply affected by the flow of work through the whole system and has nothing to do with local, departmental efficiencies.
Stop Managing Locally, Start Managing Globally
Maximizing resource utilization at the local level does not necessarily support an enterprise or systemic (i.e., global) optimization of getting products or services to market as quickly as possible. Quite often there will be departments with minimal slack time because the people are fully utilized, yet they are creating long delays for other departments. While everyone is very busy (and that makes us feel good), projects seem to take forever to be completed, or are completed so late that market opportunities are missed.
As long as we manage a complex production system such as an IT organization by breaking it down into department subsystems, and we manage these subsystems individually, we’ll continue to find it difficult to achieve significant jumps in throughput or profit within a relatively short time (months). The fact that each subsystem is optimized does not mean that the flow through the system is optimum.
Managing departmental costs means making management decisions according to local efficiencies, whereas managing commitments and reducing time to market requires management decisions according to global efficiencies. In other words, to manage, improve, and predict the output of an organization, we must be able to understand and optimize the flow of work through the whole organization and NOT the local efficiency within each department.
A Fundamental Shift
The shift in thinking required to manage globally vs locally is significant for many organizations, and starts with the leadership team.
However, the inability to make this change throughout an organization is a common cause of failure when trying to increase throughput, improve adaptability, and achieve enterprise agility.
Our Agile practice at CC Pace has been partnering with Art Chantker, President of Potomac Forum, LTD. since 2011. Potomac Forum has trained thousands of government and industry professionals throughout the country in a wide variety of information technology, acquisition, financial, and management subjects of importance to our government. It never ceases to amaze me how many people Art knows in the federal government. I’ve read scores of reviews on his workshops, and there are consistent praises for his chosen content, speakers and venues.
Over the years, Art has invited CC Pace back again and again to present on a wide variety of topics around Agile software development and Agile project management along with officials from the Department of Homeland Security, USDA, the VA, Department of Education, NGA, GSA and other Federal agencies.
On January 28th we will be conducting our first Agile workshop at the Willard Hotel for the 2015 Potomac Forum series. The focus will be on Agile and Lean Best Practices, including Scrum, Kanban and scaling Agile for larger projects and programs. Our speakers will talk about the latest Agile and Lean approaches on the horizon and how to effectively contract for Agile services within the Federal government. The government speakers and panelists already confirmed for the 28th include representatives from NGA, GAO and FEDSIM. There is a tentative agenda already posted on the Potomac Forum website, pending some agenda changes once other invited officials are confirmed. If your agency is starting down the path of agility you should attend this workshop. And if you haven’t met Art, you should!
Does your organization have a lot on their plate?
Are resources spread too thin?
Have you heard the phrase “stop starting, and start finishing”, but aren’t sure how it applies to your organization?
If you answered yes to any of these questions, here is an analogy to help you describe why prioritizing and concentrating on fewer projects first is important. It’s okay to not start everything at once.
In Detroit entire blocks of houses sit empty.
Imagine we have formed a consortium to buy a cul-d-sac of houses. We have a fixed budget. The houses all require work before they can be rented or sold. Our vision is to do the work, and start receiving an ROI on our investment by selling, or renting the houses. Our budget includes money for the initial purchase, and repairs.
We divide and conquer. We look at each house and identify everything the houses will need to make them wonderful homes. Each of is assigned one or more houses to work on. We utilize our skills, and hire contractors to backfill our team to get the work done. We have more houses than project managers/leads, so we must spread ourselves out across many houses. It is a slow process, but all houses should be done in 12 – 13 months. Then our inspectors (QA’s & PO’s) will need to sign-off on all the houses, we will need to remediate any issues, and then finally we can start to do something with everything we finished.
While we are working on the houses, our specialist like plumbers and electricians are spread thinly across the project too. It is hard to schedule their time, and we have down time while waiting for them. Even worse than the down time, is the fact that while they are running from house to house trying to get things done, they aren’t as thorough as they should be. We find ourselves calling them back, cleaning up after them, or just don’t know that something was missed until the property is inspected. They suffer from task switching and trying to make everyone happy at the same time.
Everyone is stressed, progress is hard to see. Leadership pushes for more, and the teams become dissatisfied with their job.
We rank the houses by Return on Investment (ROI) or Weighted Shortest Job First (WSJF – considering job size, sunk costs, and cost of delay), and all of us begin work on the house(s) with the biggest ROI/WSJF. When the first house is finished we can immediately sell or rent it, moving on to each subsequent house completing them with dedicated resources until all houses are complete. Worst case, the last house is not complete for 12 or 13 months, however we have been receiving money from the first house for 10 months, and each subsequent house as completed. By the time we get to the last house, we may decide just to bulldoze it and build a park.
We welcome change. More importantly, we can choose to change. We haven’t wasted any work identifying what will be done ahead of time. We identify what we need for each house “Just-in-time”. If there is a new “green” lighting system available, we can choose to change the plans and use it. If we decide to add heated flooring in a particular area of the next house, we can. Furthermore, we can decide if it makes sense to include these items in other houses based on the impact to just one house.
Our rework on each house is minimal. Our teams get faster at doing their work the longer they work together as a team. Everyone sees constant progress towards a shared end goal.
We have our supporting infrastructure in place. We know who is responsible for the work, and can trust everyone to do their best. The team gains positive momentum, and direct feedback. Everyone sees progress. We follow Lean and Agile Principles to ensure our teams are happy and fulfilled with their job.
One of the hardest things for companies transforming to Agile to accept is the idea that team members are to be dedicated to the teams to which they are members. When it comes down to it, it is really about the cultural shift.
In order to better understand what the cultural shift is, you must first ask yourself: “do I know what a team really is?” A team is defined as “a small number of people with complementary skills, who are committed to a common purpose, performance goals, and an approach for which they hold themselves accountable.” Teams that are geared toward the same goals are much more productive and are said to be able to accomplish more together than individually— “T.E.A.M. = Together Everyone Achieves More!”
Traditionally, when we discuss teams, we talk about them in the context of project teams. However, there are a few things about ‘project teams’ that cause us to pause as we refer to the definition of what a team really means.
One of the things about ‘project teams’ that cause some dread is the fact that project team members are not fully dedicated to the efforts of the one project team. In most cases, each member ends up being a member of multiple project teams. As members become members of multiple teams, their focus is interrupted and therefore undermines their commitment to each of the ‘teams’ they are a member of. It becomes hard to hold yourself accountable when you feel an obligation to commit to multiple teams, which usually will have different goals!
Another thing about ‘project teams’ that poses some stress is that they are only together for a short period of time then the members disperse and join other teams. When this happens, they now have to build their commitment and goals, as a team, all over again. If teams must continually come together then are broken apart, sooner or later the commitment to the team means nothing. Each time the team dynamic changes, the productivity of the team goes down and very seldom has time to recover before there are more changes.
How does this change with Agile, you ask…
As organizations move toward a more Agile-driven one, how they ‘build’ teams becomes very important. One of the main goals of Agile teams is that they are geared toward a specific backlog, which is centered around a particular product. Once the team is set with the members, they have the ability to rally around the backlog and focus on that.
When building teams around a specific backlog, or product, it is easy to have them focus on the single team that they are members of. Using this idea, the members that are on the Agile team are all dedicated to the same goals and outcome. When this happens, the members have a higher level of commitment because they are dedicated to the one team and can focus on the goals of that team and none others.
Agile teams that are geared toward a specific backlog, or product, have no reason to be dispersed at the end, because there is no end. Because a backlog, or product, is for all purposes, never-ending, the team keeps working on the backlog and the organization, in some way, keeps the backlog full with things that the product needs to have or do.
As the culture shifts from one geared toward the traditional definition of team to the Agile team concept, their focus and commitment shifts. It is the organization’s job to support the change in the team structure and help to keep the team focused on the idea that “T.E.A.M. = Together Everyone Achieves More!” holds true!
Tune in next time, when we talk about what it means to be a cross-functional, dedicated team…