Wednesday, April 15, 2009

Your manager makes you agile [John Levy]

Can you make someone else be agile?

It seems impossible on first glance because “agility” isn’t something you can impose on someone else. And on second glance, all the training for Agile is focused on self-managing teams.

But when I think back on managers I’ve had and I ask myself what the best ones did that helped me to succeed, there are five characteristics that stand out. The best managers influenced me and other people by exhibiting these characteristics.

1. Sensitivity – The manager listens well and has a real sense of what each person is trying to do. She watches for clues to underlying conflicts and motivations and asks questions to help me clarify what I need to move forward.

2. Insight – The manager can synthesize a big picture from lots of separate inputs. He compares what I’m saying to the comments of others and offers stories from experience to help me see what my alternatives are.

3. Understanding – The manager asks questions until she has enough information to grasp what’s missing or what could be added to improve things. She has seen lots of projects and teams and knows what it takes to succeed.

4. Clarity of goals – The manager has no doubt about what makes a successful result. He reminds me what’s to be done and what I shouldn’t do on the way.

5. Rock solid values – The manager knows and believes in the values of the company or organization and repeatedly states what they are. She also behaves in a way that is ethical and consistent with these values.

Think about how having a manager with these characteristics helps an Agile team perform to their best ability. Even though the team is empowered to manage its own day-to-day activities, having a manager around with these five characteristics can amplify effectiveness.

____________________________
John Levy consults on managing Agile development and is a frequent expert witness in computer & software patent cases. He has 30 years’ experience as a consultant and manager at Quantum, Apple, Tandem and DEC. His book on managing development, Get Out of the Way, is due out in 2009. More info at http://johnlevyconsulting.com

More...

Sunday, April 12, 2009

The Software Engineer as Artist [Courtney Behm]

There is a perception in the general public about engineers…solid, grounded in facts, serious, cautious. They work logically, methodically, are disciplined by their profession into taking one step at a time. I used to have that perception myself, until I started working in high tech. At first, as a marketing professional, I was looking at the engineers I worked with from the outside in, and the assumptions held reasonably well. There’s no question that they were far more practical and pragmatic than I and my fellow marketeers. But when I moved from Marketing into Program Management, and began dealing with the development process at close range, my assumptions began to change.

Hardware engineers fit my expectations more closely. They were, after all, constrained by the physical limitations of plastic and metal and wire. They were creative, for sure, but their creativity had physical boundaries that couldn’t be ignored, and the physics of matter added a stabilizing keel. I could set up a schedule with hardware engineers, and be pretty confident of our ability to meet it. But software engineers were a different box of chocolates altogether. We would make schedules, and then change schedules, and then unexpected things would happen, and it seemed that I spent most of my time one or two steps behind the volatility of their development process. I would say that my most frequent response in team meetings was “Arrrgh!”

Time passed, I spent a number of years as a consultant, and then returned to the corporate world as a Program Manager in an all-software company. OK, I said, how hard can this be? I’ve been in hardware/software companies, I know the drill, piece of cake. Not! A software company is as different an environment from a hardware/software company as I could have ever imagined. I found familiar the unexpected changes, and the volatility, and the difficulty of planning. But now it seemed more magical than frustrating, as if the absence of hardware restrictions had allowed the creativity of the mind to come into its own. And as I learned more and more about software as an entity unto itself, I realized something fundamentally important about software developers. Most of them are artists.

So what is the perception of artists? They are emotional, volatile, don’t like to be hemmed in by conventional wisdom or practices, are idiosyncratic in their behavior and dress, crave the opportunity to do something different. Conventional wisdom would tell you that artistic temperaments in high tech would only be found in Marcom or graphic design or web creation. But in fact, it is the hunger of the creative artist to break the barriers of the conventional that has fueled the emergence of software as the prime mover in the technology world. This has a number of implications for engineering leaders.

First…how do you manage the creative process to a schedule? Think about Michaelangelo on his scaffolding in the Sistine Chapel. I doubt he could have produced a project plan, and if so, it certainly wouldn’t have been done in Microsoft Project. “OK, Mike, we need you to have God ready by April 23rd, and then Adam by June 16th because the spark of creation has to happen on July 1st.” I think not. But when art becomes business, and there are customers to satisfy and external deliverables to produce, this is exactly what traditional waterfall planning methodologies ask of our software organizations. We tell them there are only so many days to be creative, and then only so many days to code and test. It is this fundamental mismatch that has given rise to disciplines such as Agile and Scrum, in an attempt to put a form around the development process that more closely mirrors how it actually works.

Second, how do you manage the artist developer? There are probably as many different ways to answer that question as there are individual developers. Yes, this is essentially true of all of us, there is no human being cookie cutter, and so we all respond differently. But it is exacerbated in the artistic world of the software engineer by the very nature of the work itself, and by the vision of the unknown miracles that software makes possible. Managers often find themselves caught between the need to meet schedules and the inability to rush the discovery process that gets them there. Sometimes the most valuable contributors are the most resistant to observing the necessities of measurable process and delivery dates. They are essential to the organization, and no one wants to make them unhappy, but at the same time a prima donna can wreak havoc on a product launch.

Clearly, software engineering leadership has its challenges and rewards. In subsequent posts, I’ll look more deeply into how we can make the artistic nature of software development work for us and for our organizations.

____________________
Courtney Behm holds a B.A. and an M.A. in Performing Arts and Communication, and an M.B.A. from the Harvard Graduate School of Business. In her corporate career, she has worked for wildly successful companies, and those struggling to stay afloat in the ocean of change. Through her consulting company, Viewpoint Solutions (www.ViewpointSolutions.com), she has helped a diverse client base, including Sun Microsystems, Adobe Systems, Wyeth Pharmaceuticals and the San Jose/Silicon Valley Chamber of Commerce, find creative solutions to classic business problems. An accomplished speaker, Courtney uses a combination of language, humor, insight and front-line experience to offer a fresh perspective on life in the fast lane. In 2006, she returned to the corporate world, and is currently Senior Project Manager at i365, A Seagate Company. She is writing a book on how to lead effectively in a time of constant change, and collaborating on a book on Personal Career Management.

More...

Wednesday, April 8, 2009

New Tool: Sausage Survivors [Matt Schlegel]

Not all problems need a systematic approach like the 8 phase methodology outlined in the previous submission. People are solving problems all the time. Some problems can be addressed in a few moments. Others take longer. Generally, the more people involved in the problem solving process – the more stakeholders there are – the more benefit would be gained by a systematic approach. Here are some examples.

Take the start up founded by a couple clever folks that have worked together for years at their previous big company. When they start developing a new product together, things just click. They know exactly what needs to happen. Then, a few folks join from another large company, some of them managers. Now it gets interesting. The development processes were similar enough so that everyone has a general idea of what needs to happen, but the words they use to describe the process, and the details of who is responsible for what are different enough so that confusion arises, gaps appear, and balls are dropped. Now, add a few junior developers to the mix. These fresh folks are looking to the leaders to understand the development process. Depending on who they listen to, they will get a very different picture of roles and responsibilities on the team. And, the balls continue to drop.

Next, take the two companies that just merged and are integrating development teams. Both development teams have their own terrific product development process. Now, they have to work together to deliver products. Which process should they use? How do they resolve the differences? And, how do they do this in a timely way that allows them to continue to meet the demands of the market?

Most people don’t take a systematic approach, and problems can be solved without one. I have heard people characterize their problem solving process as similar to “making sausage” – it is messy, and you do not want to know what goes in, but in the end it makes a delicious product. As with most endeavors, the smart application of the right tools will allow tool-wielding sausage makers to thrive and prosper.

_____________________________________________
Matt Schlegel has a German last name which belies the fact that his heritage is mostly Irish, English and Scottish. He does have a fondness for sausage which may be traced back to those Germanic roots. He also enjoys the meats of other cultures. He lived 3 years in Japan, where he indulged in sashimi, Matsuzaka-gyu, basashi, and other delicacies.

More...

Tuesday, March 31, 2009

When NOT to talk about Agile [John Levy]

Sometimes you have to lay low.

I know of a company where the IT department calls its monthly code releases “Agile” because they occur regularly. This confuses the rest of the IT department, because it has several teams doing Scrum, one of the best-known set of Agile software practices. The Scrum teams have been trained and know that key practices of Scrum include the following:

· A co-located team with team-managed processes
· The team includes QA & a business sponsor (called the Product Owner)
· Work is done in short iterations (usually 2 weeks) with demonstration of working software at the end of each iteration
· There is daily (or more frequent) integration of all code
· Automated test suites run at every integration

There are other practices, but that covers the essentials.

Now, why would the IT department want to call their monthly releases “Agile”? I can imagine several reasons. 1. Management wants to be seen as being on top of a current trend called Agile. 2. Doing monthly releases stresses the system enough that it makes sense to call the people running the releases Agile. 3. It forestalls the imposition of real Agile frameworks on the IT department, which would really change things.

A company has to decide to take the heat of change when it decides to go Agile in its software development. And by “company”, I mean the top management. Anything less than full commitment by at least one of the C-suite officers and a full chain of management command all the way down to a functioning team will not get the job done. And what is the job? Implementation of a framework for software development that will embrace change as it happens, be productive, and create a satisfying workplace for software developers.

We’re talking about serious productivity changes here. The studies I’ve seen show that poorly implemented Agile teams achieve only a doubling of results compared with a classic waterfall framework. The well-implemented ones achieve 9 times the productivity.

So if you’re in a large enterprise that has launched at least one Agile team, look around. If you find management support, good tools, and respect for the changing environment needed for Agile, then go ahead and lobby to join an Agile team.

If you don’t find those things, it may be best to lay low – and just start adopting Agile practices quietly, without calling attention to what you’re doing.

__________________________________
John Levy consults on Agile development and is an expert witness in computer & software patent cases. He has 30 years’ experience as a technology manager at Quantum, Apple, Tandem and DEC. His book on managing technology, Get Out of the Way, is due out in 2009. Check him out at http://johnlevyconsulting.com

More...

Saturday, March 28, 2009

Layoffs and Firing [Jane Divinski]

The current economic situation with the resulting corporate downsizings has unfortunately given engineering leaders and people at all levels of engineering management increased experience preparing for and implementing layoffs. It’s not enjoyable, for anyone involved…

I’ve recently had informal discussion on this topic with various engineering management colleagues as we caught up over coffee (well, chai tea latte for me – NF, XH, no H20) or a meal. One person lamented the fact that in his company several of the engineers who were laid off were definitely not top performers and some should actually have been previously fired. Another person felt very sad that everyone laid off in her engineering organization were definitely contributing and that there was no “dead wood” so to speak; the loss of talent was severe.

The current times are definitely painful and the layoffs unfortunate both for solid performers and for the weak links. For the former, it is distressing that their life is suddenly more stressful and not due to their own performance as an individual contributor, whether in a hands-on or management role. For the weak links it is problematic because being part of a layoff does not necessarily provide the wake-up call that a firing for bad performance should have/ would have/ might have inspired.

Years ago I took the time and energy to go through the steps required to fire an engineer and he subsequently thanked me (not immediately but later.) It is a hassle and awkward to put a professional employee on a performance plan with weekly monitoring; sometimes it’s easier to just put up with the less than stellar performance. In the case of this person he was a smart, talented software engineer who had gotten in a rut and he’d started (prematurely) resting on his laurels. Subtle hints, followed by frank discussions didn’t result in change so after a while I took more drastic steps. Not enjoyable, for anyone involved…

__________________________________________
Jane Divinski has enjoyed the challenges of engineering management consulting since 1994. Most of her gigs are as interim VPE but Jane's also tackled other interim roles including CTO or program manager. Her background is at www.jadski.com

More...

Wednesday, March 25, 2009

New Tool: Reinventing the Wheel [Matt Schlegel]

To a person holding a hammer, everything looks like a nail. This great cliché, in a backwards kind of way, says that there are many different tools and many ways to solve problems. Here, I will describe a tool that I have used successfully to solve complex problems in cross functional organizations. Perhaps my analog electronics engineering background compels me to formulate an analogous tool to aid me in describing this tool.

The analogous tool that I propose to use is the wheel. Like the wheel, this tool is an efficient way to move teams forward. Once the team is in motion, it wants to stay in motion. Conversely, once it gets stuck, it takes effort to get it rolling again. It requires balance for smooth operation: once out of balance, the ride can get bumpy. You get the idea. The wheel will be a good way to describe both the pros and cons of this approach.
This wheel tool is a methodology consisting of 8 steps or phases. Each step is critical to smoothly getting to the next step. The steps must be done in sequence in order to keep the wheel moving forward. And, each step allows the opportunity for team members to contribute in different ways, some steps will resonate with certain team members’ strengths. Those resonances will provide opportunities for those members to play to those strengths, providing leadership during that phase. Without further ado, here are the steps:

1. Problem – Goal: List the problems, define the goals
2. Team: Build a balanced team
3. Ideas: Brainstorm ideas for solutions
4. Analysis: Analyze the ideas
5. Proposal: Prepare a promising plan
6. Advocate: Present the promising proposal
7. Implementation: Implement the plan
8. Debrief: What worked? What didn’t? Start again.

Does this look familiar? I would expect most to say it does. That simply may speak to the natural way we humans solve problems. The magic, if I may use that word, of taking this systematic approach is that the solution the team chooses to implement has buy-in from all, everyone has a vested interest, and solutions are effective and lasting. Magic indeed.

Ah, yes. And, my favorite part about the wheel analogy is that the beginning and the end are at the same point.

________________________________
Matt Schlegel is a rare native to the Bay Area having grown up in Pleasanton and having gone to high school at Mission San Jose in Fremont. He went south to study engineering at Harvey Mudd College as an undergraduate and UC San Diego as a grad student. Perhaps his favorite education has been at the poker table, where he there learned about another kind of wheel – a five card hand consisting of A-2-3-4-5.

More...

Monday, March 23, 2009

Have you ever tried to introduce an Agile methodology into a company? [Nancy Dirgo]

I've done this a few times in my career. The first time it took about a year and a half. If you want to do this company-wide, you first need to get buy-in from the top. The CEO needs to understand it and needs to understand how it can save the company time and money. You then need to get the other stake holders involved. They need understand why it is important because they are your advocates. After that, it's all about tailoring it for your company.

From there, I built a internal website. The website defined each phase and provided an explanation of the deliverables of each phase along with templates of those deliverables. The templates provided people with something to start with; plus, it gets everyone using the same format, speaking the same language, walking the same walk.

I then took it one step further! I developed a 1-hour training session. I taught this session 13 times. I traveled to all of our offices (west coast and east coast). Every person from the CEO to the Admins had to take this training. This was an excellent way to get everyone to understand the process. The first 30 minutes of the session went through an explanation of each phase and their deliverables (just like the website). In order make this meaningful from a hands-on standpoint, I wanted to come up with something that everyone could relate to. I took the deliverables from "building a house" and wrote them on sets of index cards. The group broke into small teams and their assignment was to take those deliverables and organize them into the proper phases. At the end of the session, everyone walked away with a good understanding of the process.

Now that training was complete, we still had one more task to perform in order to drive it home: a test case. We took a small project and ran it through the process. We took that same project and did the old way. What do you think we found out? We would have saved $200K on this one project by working it through our methodology.

This was a very rewarding experience which has allowed me to continue to roll out Agile, company-tailored methodologies to several companies.

____________________
Nancy Dirgo has held several technology management positions in companies from start ups to large-size companies. She now is pursuing her interests in the Medical and Healthcare industries with Medical Devices and software. She also enjoys consulting for companies in the areas of engineering leadership, program/project management and software development.

More...