Showing posts with label Agile. Show all posts
Showing posts with label Agile. Show all posts

Thursday, April 8, 2010

Getting Really Good at Agile [Ron Lichty]

From the speaker at the next Engineering Leadership SIG event, April 15, 2010:

The first half of Mike Cohn's book, "Succeeding with Agile: Software Development Using Scrum", isn't so much about how to be successful with agile as how to be successful replacing non-agile with agile, selling agile, and transitioning to agile.Mike Cohn is neither a wild-eyed dogmatist professing the one true way nor an ivory-tower philosopher; he's a pragmatist. He devotes entire chapters to helping scrum evangelists decide whether to start with a pilot or go all-in across the organization, whether to pilot publicly or in stealth, what factors might prevent success, how to swing things your way, how to approach a transition in steps, picking the right first project and first team, and how soon to adopt agile technical practices like simple design, pair programming, TDD, continuous builds, refactoring, and automated testing. He notes from the first chapter that agile implementations are hard and don't always "take" - and explains why. He recommends solutions to the many conundrums and traps that agile teams face.

About midway through the book, as you're reading insights into teamwork, you realize that this book is not just about transitioning to agile but about getting really good at agile - and that you're going to need to read it not just once but come back to it for new insights again and again. The fact is it's stuffed with tips, guides, data, approaches, failures, successes, and helpful hints of every kind.

Part of what makes this book important for me is repeatedly reading observations consistent with my own experience, but drawing on so many more experiences with agile that it results in emergent patterns, as well as in truths that are too often left unsaid. Then there are the surprises that come from reading an author who is remarkably well-read across genres. He does us all the favor of reviewing and summarizing scads of studies and surveys that demonstrate why agile is worth the effort, with data on productivity gains, lower costs, improved employee engagement and job satisfaction, faster time to market, higher quality and, importantly, stakeholder satisfaction gains.

What's the role of a manager of a self-organizing team? One of them, agile gurus seem to agree, is exercising subtle control (as opposed to command-and-control) and Mike provides an entire framework for debugging team problems and influencing their success. This will be one of those chapters I know I'll revisit repeatedly.

In another example, Mike remarkably provides what in essence is a crash course in change, and that chapter alone, while loaded with specifics about making a change to agile, could be used by any technical leader making a technology-and-culture change of any kind. Know why shopping carts were introduced and how shoppers were convinced to use them? Mike does, and effectively uses the example to teach change leadership. How does a leader deal with the skeptics and the saboteurs, the diehards and the followers certain to show up on your teams? How do you sway the uncertain to get on board?

Cohn is practical right down to the challenges from facilities and h.r., the likelihood agile transitions will face waterfall-driven expectations, and strategies for coexisting with other approaches, regulatory standards and processes. Importantly, he provides helpful anecdotes and examples from companies large and small. He's familiar enough with other process changes your company may have attempted to be able to compare and contrast and differentiate the substance and style of scrum from everything that came before.

While Cohn is sometimes unsatisfying - drilling down not quite far enough in sharing what's worked - in its 400-plus pages, it's remarkable how few of these unsatisfying examples there are.

Finally, I should point out that though it may not be immediately obvious, there's one more group of readers for whom this book has enormous value: Agile wannabes who know their current process isn't working. They frequently have heard of agile but have no idea what it looks like or how to sell it. If you're one of those, you also need to read this book. Mike Cohn over and over offers advice and examples and data that will give you aha after aha as you build a picture of what a truly effective process can look like - and how yours could become functional like his.

If you're interested, there's a longer version of this review at:

http://ronlichty.blogspot.com/2010/04/book-review-succeeding-with-agile.html
_________________________________________
Ron Lichty is a "VPE of Fix-It," providing interim and on-demand VP Engineering services to optimize software organizations and efforts. He specializes in solving problems like painfully slow product development, past-due estimates with no delivery in sight, snafus from geographically dispersed teams, scalability stymied by sluggish data integration, productivity bridled by uncertainty, an "order-taking mentality" from teams that should be proactive, and teams unable to break out of research and move on to development and delivery. He also untangles organizational knots, creates roadmaps everyone can follow, builds communications with other parts of the organization, coaches and trains organizations in agile and scrum, and gets teams productive and focused on delivery, quality and customers. Small tweaks, dramatic impacts. He'll be presenting the SDForum's April 15 Engineering Leadership SIG topic on how agile changes the development manager role group in Palo Alto: "If Agile Teams Are Self-Directing, What Do Managers Do?" His book on managing software developers and software development teams, "Managing the Unmanageable: Rules, Tools, and Wisdom for Managing Software People and Projects", is forthcoming.

More...

Wednesday, October 21, 2009

Managing Risk in IT organizations [John Levy]

Most losses / failures in IT Development are initiated or compounded by management shortcomings; very few losses / failures are due to technical inadequacy.


1. IT Operations and Development must be managed differently. Development is Engineering and must be managed as such. Outsourcing of Development does not convert it into Operations – it is still Engineering.

2. Measurements for IT Operations and Engineering (Development) are different: Development should be measured based on expected ROI plus certain strategic factors; Operations should be measured based on predictability of spending and certain Quality of Service measures, along with regular and consistent assessment of relevance of those measures to the business. [This is analogous to market risk in financial portfolios]

3. Most losses / failures in IT Development are initiated or compounded by management shortcomings; very few losses / failures are due to technical inadequacy. In addition, the probability of future failures remains undiminished so long as the management shortcomings are not addressed.

4. The cost of failure in IT Development always exceeds the allocated budget for the activity, because failure has consequences beyond the immediate failed project, both for people and for other projects. For example, one major factor of risk that increases when a development project fails is the loss of key people. It is rare to find IT management mitigating this risk immediately on learning of a development failure.

5. Failures and losses in IT Operations usually involve either directly managed operations centers or outsourced providers’ operations. Outsourced operations are inherently riskier because the providers’ operations are less visible, and therefore less known, to Operations managers. [Cf. Failure in Microsoft-provided services for Sidekick smart phones, Oct., 2009] [This is analogous to credit or counterparty risk in financial transactions]

6. IT management should be able to communicate to top management the nature of the tradeoffs in IT Operations and Development, so that strategic implications of decisions in IT are well understood at the top level. This means that financial factors must not be the exclusive determinants of IT decisions. The CIO should not report through the CFO.

7. Multi-year planning is essential for both IT Operations and Development. A roadmap for rationalization and integration of resources and services is necessary, even if it must be revised multiple times per year as new equipment and services are needed. Contingency planning and scenario analysis related to possible shortcomings of vendors and outsourced services must be part of the plans.


Above thoughts on IT management are based on my recent experiences at a client company and were triggered by a paper, “Risk Management Failures” by Prof. Rene Stultz, Fisher College of Business, Ohio State University, published by Cornerstone Research http://www.cornerstone.com/

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 high-tech management, Get Out of the Way, is due out in 2009. More info is at http://johnlevyconsulting.com


More...

Monday, June 15, 2009

IT Dilemmas [John Levy]

As an organization grows, it has to increase the scale of IT activities, including software development. As a result, it faces these dilemmas:

1. Software development is engineering, but IT is an expense.

If your only management metric is level of expense, rather than return on investment, then you won’t be able to differentiate between winners and losers in software development. Some organizations have the CIO reporting to the CFO, because they are completely oriented to control of expenses, and IT is a large expense. But this misses the fact that investment in software, whether for internal use or for sale as a product, should be managed the way that R&D (Engineering) is managed – as an investment in development that must ultimately produce a return.

Engineering is not purely execution. R&D/Engineering involves a degree of creativity along with a professional sense of discipline about implementation. That’s why recruiting and retaining people who can balance innovation with execution is as important in Engineering as in, say, Marketing.

2. Outsourcing and offshoring work when the activities of software development can be broken into component parts and split across multiple organizations without loss of innovation or relevance of the product.

In forward-looking organizations, IT-implemented tools provide a strategic advantage to the business. To achieve this, IT strategy and architecture must be very close to the top decision makers. In this context, the question of outsourcing becomes, “can we succeed by having people we have not hired directly execute some part of our implementation?” To the extent that the impact of software or IT on the organization’s strategic goals is not considered, the decision to outsource can lead to failure in many ways.

3. If no one in top management understands how IT works, then all the IT decisions will be made based on financial reports. As organizations get big, they become more and more finance oriented. When someone at the VP level or higher has enough technical background to understand IT implementation, then IT strategy has a much better chance of being realistic. Of course, the CIO should have a basic knowledge of technology as well, because vendors will attempt to sell things which may not be appropriate to the organization. The main problem, however, goes back to item 1 above: managing Engineering is different from simply controlling expenses.

4. Traditional Project Management doesn’t fit well with Agile software development.

When we do software development in an Agile framework, we have fixed time & budget and variable functionality. Almost no one who has been doing traditional Project Management intuitively understands how to manage a project this way. Short Agile iteration cycles confound traditional PM tools and measurements. We need the PM world to come up with a new division: Agile Project Management, with a focus on projects that are not characterized by large sets of requirements up front, and have rapid fixed cycles with variable functionality.

5. It is difficult to overcome an addiction to short-term metrics.

IT managers prefer short-term pain-reduction (ship it!) over longer-term goals (is it what the users want?) every time. This leads to the never-ending cycle of code debt (code that needs to be cleaned up and/or re-written). To overcome this phenomenon we need to understand the psychology of addiction and to get top management to support a change to proper metrics. For further discussion of this, I recommend reading Gerry Weinberg’s Quality Software Management, Volume 3: Congruent Action (New York: Dorset House, 1994).

All 5 of these items also apply to software development in Engineering departments. But the effects are most widespread in IT organizations. How is your IT organization doing?

__________________________________________
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 is at http://johnlevyconsulting.com/

More...

Thursday, May 28, 2009

Managing the Creative Process [Courtney Behm]

So…you have a product that is core to the success of your organization, and you’ve just realized that, though the titles of your team say Software ENGINEER or DEVELOPER, it should really be ARTIST. Add to that the challenge of software itself, a product that is often indistinguishable from magic, and you have a dilemma. How do you maintain the level of creativity you need to be cutting edge and still deliver on time?

Let’s talk about the planning process. Consider, for a moment, Microsoft Project. I know, I know…a fearsome thought. So many people have an antibody reaction to using Project; I’ve worked at companies who have refused to use it, relying instead on Excel spreadsheets and lots and lots of manual updates to manage complex development programs. Microsoft Project isn’t perfect, no question about it, but it’s not really that bad. Its biggest problem is that it isn’t flexible enough to track the work of artist developers. It’s an artifact of the waterfall methodology, symbolized by the horizontal Gantt charts with their slick interdependencies that adapt every time a date is changed. It assumes that the project is one monolithic whole with interconnected moving parts. You start with A and move to B and then to C, and before long, you intersect with D. Waterfall methodologies focus on maintaining these relationships to keep the project on track. For some applications, it works wonderfully – IT infrastructure projects, vendor evaluation, customer betas and product launches, to name but a few -- but waterfall, and therefore Project, isn’t the best tool to support the more fluid vision of the software developer.

In reaction to the restrictions posed by waterfall, we now have “Agile” programming, with its various manifestations…the one I’m most familiar with is Scrum. Agile is pretty much exactly what its name indicates. It’s a way of approaching software development that allows us to bob and weave, to take advantage of discovery, to place enough rigor around the process to know what is going on, but to keep options open. Agile says that the best results arise from small, iterative development chunks. You come together as a group, you meet every day, and you chart your progress with tools that can be easily adjusted as you discover more and more about what your product really needs. And within a short time, you have a usable, working piece of functionality. It changes the game.

But Agile programming seldom takes place in a vacuum. Inevitably, there are customers and deliverables, and we need to sell product to make money. So elements of waterfall creep in under the cover of darkness. How can we support the creativity of our software developers and still march to the corporate drumbeat of deadlines, release schedules and launches?

Eventually, common sense trumps methodology, and a hybrid scheme emerges…not as crisp and apparently predictable as waterfall, and not quite as free and creative as Agile. This is a compromise with which no one is completely happy, but which honors both the need for flexibility and the need for predictability. However, it isn’t easy. Knowing when to let the creative energy flow and when to rein it in is a dance that doesn’t come naturally to most of us. We are called to come out of our comfort zone and live in two worlds at once. And this management challenge has a tendency to change emphasis depending on the breadth of our responsibility to the organization. The closer we are to the development process itself, the more comfortable we will be with an Agile approach. The closer we are to the Boardroom, the more we will want things to be certain.

But to be successful in this volatile, ever-changing world of software, we have to listen to the development process as if it could talk, and let it tell us what it needs. When we consider it as a living organism, the combined DNA of marketing and engineering creativity, the offspring of a company that depends on it for survival, we can see more easily where the touch points are, where we can apply structure, when it’s time to let the ideas flow, when to say, “That feature won’t make the release” and when to say, “This feature is worth waiting for.” It may mean letting go of some old assumptions about how things work, but the final result will be the best of both worlds.

____________________
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...

Saturday, May 16, 2009

Will complexity overwhelm us? [ John Levy ]

Should we worry about software being too complex?

I’ve been teaching a course to elders about how computers work – both hardware and software. The challenge in such a course is to make the content both true and accessible while keeping the presentation interesting.

Hardware is in some ways easy to teach. Once a student grasps that all computers involve the interaction of a processor with memory (both for instructions and for data), there is only the matter of input/output left to deal with. Well, OK, there’s bootstrapping and operating systems and a lot of other stuff in there, but knowing about the processor and memory is the only crucial step to understanding how it runs.

But what about software? First I explain that nobody writes in machine code; very few write in assembly language; and even procedural languages like C and Pascal are being abandoned for object-oriented languages. So I have to get across, first, that people who create software are thinking abstractly in terms of algorithms and procedures. Then the next level of abstraction is objects and messages. And finally, the tools of the trade include editors, compilers, linkers, loaders and program (and object) libraries being used in Integrated Development Environments (IDEs).

And I haven’t even touched on testing and QA yet. How is a layperson going to come to appreciate the difficulty of producing a properly-functioning program? Yet everyone knows war stories of how failing software caused lots of damage. Is our knowledge of testing methods inadequate, or are we just being poorly managed?

Gerald Weinberg, in his recent book, Perfect Software and other illusions about testing (Dorset House, 2008), does a brilliant job of explaining to non-experts why testing doesn’t – and can’t – produce the eponymous perfect software. I highly recommend reading Chapter 14 of his book, which starts off with a study of failed and successful projects at IBM. All of the projects had “bad luck” strike during the projects. His conclusion is that success was a function of good management, not avoidance of bad luck.

Fifty years of Moore’s Law has given us computing power in our pockets that is greater than the room-filling machines of the 1960s. And we have whole networks of tiny microcontrollers inhabiting our homes and our cars. How are we going to deal with the prevalence of bugs in these devices?

No one says the code has to be perfect. But it has to be structured in a way that keeps it from failing catastrophically. And it has to be adequately tested even as it gets larger and more complex. Are we up to the challenge?

I firmly believe that Agile software development frameworks give us the best path to developing decent software. But they are not enough. We have to manage ourselves and our organizations in ways that permit healthy development behavior. This is what Agile Management is about: giving up certain counter-productive behaviors and establishing new management patterns that encourage constant improvement in the face of increasing complexity.

_________________________
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 is at http://johnlevyconsulting.com


More...

Monday, April 27, 2009

Software Evolution [John Levy]

There are some principles of software development that were described by M. Lehman by observing large-scale development teams (such as IBM’s OS/360 development in the 1960s). When you put several of these principles together, it is not very encouraging for those of us who are concerned about software quality.

1. Early bug rate predicts late bug rate
You would think that if you fix a lot of bugs early in the project, you could expect to have a lot fewer bugs later. In fact, observation shows that projects that have (and fix) an above-average number of bugs early tend to have above-average bug rates later.

2. Software grows over time

As users demand more features and functions in their software, the size and complexity of a released software package tend to grow.

3. Bugs are introduced when bugs are fixed

No matter how careful we are, sometimes we introduce bugs while we are fixing others. As long as the ratio of bugs-introduced to bugs-fixed is low, working on bug-fixing is a productive enterprise.

When you combine these observations, things get stickier. For example, the ratio of bugs introduced to bugs fixed tends to get larger as the software package gets larger. As a result, bug-fixing gets less and less efficient as time goes on because of the growth of the software.

Also, we can imagine that putting a major push on early bug-fixing in project could drive up the introduced-to-fixed ratio, thereby keeping the first rule valid – we’ll find even more bugs later.

What’s an Agile manager to do?

First of all, pay attention to bug-find rate and system size and complexity. My guess is that having the software developers fix their own bugs before QA sees the software doesn’t fall into the domain of the first rule. In any case, it’s a good thing to have a designer/implementer see exactly what went wrong – it’s a good opportunity to correct one’s thinking. Of course, Agile principles suggest that pair-programming does exactly this at the earliest possible moment in the coding process.

Second, always strive to reduce complexity, whether by simplifying the model, partitioning the system, or adapting to existing services rather than inventing new ones.

Finally, make sure that your teams are relentlessly refactoring the code. The teams always learn better and better ways to streamline and simplify the functions they’ve already implemented, so don’t hold back on letting them express that knowledge.

If you want to read more on how software evolves over time, do a search on “Lehman software evolution” and see what’s been learned.

____________________
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...

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...

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...

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...

Sunday, March 1, 2009

What's an agile manager? [John Levy]

Sometimes I sit back and think about management -- really! Yesterday I was reflecting on the hierarchy. You know, the President at the top, the Vice-Presidents, the Directors, the managers, and so on down the line. This is what we call line management, right? And we know that each one of them is responsible for something. The best analogy in Scrum is the "single wringable neck" that summarizes the Product Owner role.

But the Product Owner in Scrum is a member of a team -- the Scrum team that is self-organizing, self-improving, and collectively responsible for producing results. What if we organized the whole company that way. We could have a Departmental Scrum consisting of the Scrum Masters and Product Owners from each of the ongoing "projects" or functional groups, just like a Scrum of Scrums. And there could be -- but wouldn't have to be -- a Senior Scrum Master and a Senior Product Owner who participated in further Scrums of Scrums with broader scope.

Back in 1996, I was a member of an 8-person team charged with planning company strategy looking 10 years ahead. There was another 8-person team doing the same thing independently. (For a description of the process, see Prahalad & Hamel, Competing for the Future). We spent 9 weeks away from our normal jobs studying the world and composing a strategy. It was the best team-oriented process I have ever participated in. The reason I note it here is that when the team was asked to select a single spokesperson / leader, the team refused. We responded that we had confidence in each and every team member to represent the team (and to check back with the team if there were any questions).

What if a Department were run by a team that had that kind of confidence in each other? Imagine a group of former "managers" who are now team facilitators and/or team product owners who spend enough time together to know what's going on, and are able to deal with all of the Department business by designating a pro-tempore leader to represent the team and its interests. Even at the next level "up," even the "leader" could be a rotating role.

It goes against all the hierarchical thinking that we've been raised with, taught, and trained to accept as normal. But a business enterprise is not a military organization. And many of today's enterprises need to be Agile so that what they produce (whether product or service) is adapted to the current business environment. If we organized management as rings of teams with coaches and product owners, that would give us maximum flexibility, open up lots of lines of communication, and cross-train people in many roles.

First, of course, we have to give up some long-hallowed practices, such as the hierarchical organization chart. We'd also have to change the concept of managing from being a sense of control to one of responsibility -- and responsibility in this case means responsible for the way in which the team operates as well as what we as a team produce. This strengthens the idea of the manager as coach, and might even encourage a person in the leader/manager role to act as if the team knew more and was capable of more than the individual leader. What an idea!

____________________
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...

Thursday, February 19, 2009

Agile Management -- Principles and Systems [John Levy]

As we broaden the applicability of Agile principles from software to how we manage, I'm trying to encapsulate principles that apply in the wider context, and to develop "systems" or ways of conceiving of management that help us to visualize what we're doing. So the title above, Agile Management -- Principles and Systems (or AMPS as we will no doubt call it later), is the heading under which I'll put these encapsulations and visualizations.

Immediately I can think of some pitfalls to this process. First, "principles" and "systems" are very heady -- conceptual -- things. Yet one of the first principles we're trying to broaden is to emphasize individuals and interactions. So any principle that loses sight of the individual and impels us to act unilaterally (rather than interact) is moving in the wrong direction.

Let's take a concrete example. You have a set of projects you've asked a manager who reports to you to get done, but the results are not what you want. Not enough is happening, and sometimes the wrong thing is happening. What's the agile principle that applies here? First, direct interaction with the manager is necessary. Not only interaction, but respectful listening after you've asked the questions. There may be more impediments in the path of these projects than you imagined. Or the projects may be more complex than you believed. Then the manager may need coaching in certain areas, but hasn't asked for it. Or the manager may have ideas for getting the projects done that are simply not working. The only way to determine what's actually going on is to ask and to listen. Then, using your judgement and experience, you either coach, direct, or suggest to the manager ways in which things could work better. If you haven't done that, then you're not interacting with the individual in a useful way.

Too often, upper level managers, due to the press of time or overload from having too many direct reports, will severely shorten or skip over the step of listening to the responses of the individual. Or will jump to the conclusion that the individual is inadequate when a small amount of coaching would be very effective. In the old days we would call this incompetent management -- because the result is the waste of time and energy for both the individual and the manager far beyond the energy required to correct the situation. Today, we'll call it a failure to apply Agile Management principles. After all, it's the responsibility of the top manager to lead by example, and to make efficient use of everyone in the organization. That can't be done by applying pre-conceived ideas about people and their roles without listening to the individuals actually doing the work.

Maybe you'll find this old hat -- something we all knew from long ago. But we need to remember that management is primarily a matter of people interacting. What follows, if the interactions are effective, is productivity. And we all know that productivity underpins every aspect of being agile. Consider that statement a principle.

___________________________________
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...

Wednesday, February 4, 2009

We wouldn't know a good system if we saw one [John Levy]

One of the keys to effective Agile development is having a customer as part of the development team. Yes, I really meant to say customer, not product marketing guru, executive officer, or VP of Engineering, because we don't know how to tell when a system is good for the customer.

There are a lot of reasons for this. The most prominent reason is that we're technologists, and we love engineering. That means we love to take things apart, understand how they work, and then design intricate and elegant solutions to engineering problems. It's even worse when it comes to engineering systems that will be used on (or consist of) a personal computer, because we're expert users of PCs. Therefore, we have no clue about how a non-expert user will regard the interactions offered by the system we designed.

As a result, enlightened companies have discovered that new breed called an interaction designer. And they trust the design of the interactions to these people. And what do they know? Well, they have a grasp of human psychology, human mechanics (haptics), graphic design, language and symbol semantics, and learning. An odd, but effective combination.

When all of our customers were engineers, we didn't need interaction designers. But watch out when the system is for a non-technical consumer. For an example of what happens when the engineers design the interactions, take a look at the GPS system in the Lexus. This system, in an otherwise beautifully designed car, has 13 ways to set a destination; and what's the button you press after selecting a destination, to take you there? It's GUIDE! In my vocabulary, "guide" is a noun before it's a verb.

OK, so we should not be designing our own product interactions. And that's a good reason to have a customer on the development team, so she can tell us when something looks right and feels right as we go along (every iteration). And what's our reaction supposed to be when we find out the customer wants something changed? Happy -- happy that we found out in 2 weeks that we were on the wrong track; happy that we can suggest some other possibilities directly to the customer and listen to the customer's reaction; happy that our development work, if it is allowed to continue to completion, will work the way a real user wants it to work.

And that's pretty happy.

___________________________________
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...

Friday, January 23, 2009

When impediments dominate [John Levy]

Agile managers are supposed to be "servant leaders" and to spend a good deal of their time removing impediments to effective work by the team. What happens when the impediments you're trying to remove are so big that (a) the team is working at half efficiency at best, and (b) removing the impediments requires intervention up the management ladder at least 2 or 3 levels?For example, an enterprise I know about has barriers to efficient work that have to do with software environments and bureaucratic procedures for deployment of releases. A manager at the VP level has reported that when a funding request to fix the environments comes up, it gets knocked out by the financial folks "because it won't increase revenue." Meanwhile, releases take an extra week or two because approvals have to travel up a 3-link chain, the last two of whom are not in fact concerned with (or knowledgeable about) the particulars of the intended release.

It's easy to get frustrated with such impediments. As one of the technical staff said recently, it's a case of "I love the work and hate the company." Not that the place of employment is unpleasant -- on the contrary, it's a very supportive and friendly physical place to work, at least on the surface. But the ossified bureaucracy indicates that something about the enterprise is extremely un-Agile.

Within this context, however, there are positive indicators: a significant number of bright, capable and "agile" people who recognize what should be done; strategic initiatives coming from the top that seem well-focused; and a willingness to bring in new ideas -- and consultants. This sets up an interesting tension between the "let's get the transformation done and move on" people and the "we have to follow the rules and processes that have worked for us for so long" people. Even this statement is not entirely fair: the "rules and processes" people are doing what needs to be done to satisfy the financial processes that make the place run, even as they know that something has to change. So the challenge is to establish ways to evolve the processes into something more agile.

Can an agile software consultant do that? Probably not. But the consultant can do a number of useful things. One is to encourage teams to operate in an agile way, while finding practical ways to feed the needed numbers into the financial gear-works. Another is to provide unbiased information from grass-roots teams to key change agents (managers who are moving the enterprise in the Agile direction). And finally, a consultant can advise the decision-makers when old processes are just too creaky to keep as the enterprise moves into the 21st century competitive world.

Of course, you may be able to do all of these things from within the enterprise, too. Be the consultant and change agent; but be sure you have the support of your network of other change agents -- you may need it to keep your job.

_______________________________________
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...

Thursday, January 8, 2009

Can you manage conflict in an Agile way? [John Levy]

A company I know initiated an agile software development project in 2007 using Scrum. They put together a very competent crew of developers, isolated them in a corner of the building, put them under a manager who understands and is an advocate for Agile frameworks, and let them start. There was only one hitch -- their business counterparts were 750 miles away. Nonetheless, the team overcame this obstacle by daily telephone conferences, online file sharing, and frequent visits by the business folks to the developers' location. Development continues with frequent demonstrations of working software.

This year, a larger, existing group of developers and website design people in the same company decided that all their problems could be solved by going Agile. The list of obstacles, however, is quite a bit longer:

1. The development managers and some of the developers are also 750 miles away from business and website design people.
2. Some of the developers and QA people are contractors at a location a few miles from the development location.
3. Other developers are offshore -- in India.
4. None of the developers or managers have experience with Agile / Scrum teams.
5. The development work is dependent on a number of vendors' software packages.
6. The physical work area at the company's plant is not conducive to Scrum team interactions.

This may seem like a lot to overcome. In fact, it may look like a fool's journey to take on implementation of Scrum in this environment.

But we're still not through the whole story. Here are a few more issues:

7. The server software environments for development and for QA are not the same as in the operational systems.
8. The QA people are constrained by company rules from accessing the live, operational system.
9. Attempts to allocate budget for infrastructure improvements are consistently thwarted "because they won't increase business."
10. Frustration at the low throughput of finished projects has led to a lot of conflict between the business people and the development people.

So now let's consider a few questions about what to do if you're an advocate of "Agile Management" ....

Would you take on the Scrum training for this company? If so, would you expect the company to see positive results within a year?

Where would you begin to tackle the productivity problems at this company?

If the CIO asks you what should be done to make development run more smoothly and more productively, what would you say?

And finally, how would you justify (to the management) spending dollars on infrastructure improvements?

Yes, I am involved with this company, and for now I'll tell you only that I'm addressing issue number 10 first -- the conflict between the business people and the developers. I believe that establishing a basis for cooperation between people who need to work together is always the first order of business. Is this "Agile Management?" Yes, of course. The top priority is what's most important and most valuable; and getting conflicts resolved is at the top of my list of value-producers.

______________________________________________
John Levy, PhD http://johnlevyconsulting.com
Managing product development for speed and innovation

More...

Friday, January 2, 2009

What is Agile Management? [John Levy]

We're not into managers who do yoga. But there are two other ways to think of Agile Management.

1. If you're in software development, then you are surrounded by (if not submerged in) people practicing Scrum, XP, RUP or one of the other frameworks for Agile Software Development, so you can find a community of like-minded developers. How does management fit into the picture?The Agile Manifesto http://www.agilemanifesto.org says we value people and interactions over processes and tools.

So the first way of thinking about Agile Management is: we are figuring out how to apply the Agile principles to actually managing a collection of software development teams. This immediately brings up a dilemma. Agile principles emerged from a bottom-up approach which says to management, " We are developers, we can manage ourselves if you let us, the job of our manager is to defend the team and the team's working space. Go and remove impediments. Stay out of our way."
But what about the manager? How does the manager role get filled and the person in the role get fulfilled? Is she a former developer who sacrificed herself to become a full-time non-developer? Or a project manager who now has to learn how to let go of control? Or even a founding software guru who is now running the whole company?

I believe we're interested in all of these questions. And we want practical tips on dealing with real-world problems that come along with an Agile development.

2. If you've been a manager (or Director, or VP) for a while, you have probably discovered that many people regard management as an honorable profession. Americans have been good at more than firmware and pizza (à la Snow Crash) -- they've led in modern management as well.

So the second way of thinking about Agile Management is: how can we apply the principles of the Agile Manifesto to general management? Customer Collaboration and Responding to Change sound like good principles across the board. Can we develop a set of guidelines for managers that establish a more agile approach to the broad challenges of management? Is there something like Iterative Management (something like The One-Minute Manager)? A way of managing that feels as responsive and adaptive as Scrum?

I invite you to join in this discussion wherever it goes.

______________________________________________
John Levy, PhD http://johnlevyconsulting.com
Managing product development for speed and innovation

More...