Home > Articles > Software Development & Management > Agile

The Agile Revolution

This chapter is from the book

Agile Project Management

The central question for project managers, project team members, and executives is, "How does project management add value to a project?" Unfortunately, many development engineers consider project management to be a roadblock—a hindrance, not a help. Project managers are viewed as administrators who put together detailed task schedules, create colorful resource profiles, bug team members about micro-task completions, and write reams of status reports for upper management, not as direct contributors to delivering value to customers. Teams often view project management as overhead. As Michael Kennedy (2003), author of Product Development for the Lean Enterprise (about Toyota) says, "Our product development philosophy is based more upon administration excellence than technical excellence, and it's getting worse."

"Buy pizza and stay out of the way" expresses too many product engineering teams' view of "good" project management. Rather than overhead, project management should be seen as offering inspirational leadership focused on delivering customer value. We have missed this point because many project management practices and project managers are focused on compliance activities, not delivering value. They are project administrators, not project managers. Customers pay for value; everything else is overhead—necessary overhead in some respects, but overhead nonetheless. Team activities or deliverables that help comply with government regulations are necessary, but they rarely add customer value. Documentation that conforms to legal requirements may be necessary, but it may not add value—at least not directly. Status reports assist managers in meeting their fiduciary responsibilities, but they don't add value. Endless milestone approvals may delude management into thinking they are in control, but they don't add value.

But how do we measure customer value and project management's contribution to that value? Motorola's ill-fated, multibillion-dollar Iridium project was a spectacular failure in the market. Meanwhile, the movie Titanic, which was severely over budget and time—and viewed by early pundits as a $200 million flop awaiting release—was the first movie to generate over $1 billion in worldwide revenue. By common compliance-based project management practices of budget, scope, and schedule performance, Titanic was a failure. Within some circles, Iridium was considered a success because it fulfilled the original specifications.

All products face similar demands—customer needs, profit, development speed, constant change, high quality—that require high levels of competency in multiple domains of expertise. These often contradictory constraints and demands on product development—speed and quality, great functionality and low cost, uncertainty and predictability, mobility and stability—have created the need for project managers and project management practices that focus on delivering value.

APM is a set of values, principles, and practices that assist project teams in coming to grips with this challenging environment. The core values of APM address both the need to build agile, adaptable products and the need to create agile, adaptable development teams.

Agility Defined

There is no Agility for Dummies. Agility isn't a silver bullet. You don't achieve it in five easy steps. So what is it? For myself, I've characterized agility in two statements:

Agility is the ability to both create and respond to change in order to profit in a turbulent business environment.

Agility is the ability to balance flexibility and stability (Highsmith 2002).

In an uncertain and turbulent world, success belongs to companies that have the capacity to create change, and maybe even chaos, for their competitors. Creating change disrupts competitors (and the entire market ecosystem); responding to change guards against competitive thrusts. Creating change requires innovation: developing new products, creating new sales channels, reducing product development time, customizing products for increasingly smaller market segments. In addition, your company must be able to respond quickly to both anticipated and unanticipated changes created by your competitors and customers.

An example of a product development effort in which all the aspects of agility come into play is that of small, portable DNA analyzers. These instruments, which are still five or more years away from commercial deployment, could be used for analyzing suspected bioterror agents (e.g., anthrax), making a quick medical diagnosis, or performing environmental bacterial analysis. These instruments must be accurate, easy to use, and reliable under wide-ranging conditions, and their development depends on breakthroughs in nanotechnology, genome research, and microfluidics. A half-dozen companies are racing to build versions of a DNA analyzer, often with grants from agencies such as the US National Institutes of Health (Gardner 2003). Developing these leading-edge products requires blending flexibility and structure, exploring into various new technologies, and creating change for competitors by reducing delivery time. These are not projects that can be managed by traditional, prescriptive project management methodologies.

Some people mistakenly assume that agility connotes a lack of structure, but the absence of structure, or stability, generates chaos. Conversely, too much structure generates rigidity. Complexity theory tells us that innovation—creating something new in ways that we can't fully anticipate, an emergent result—occurs most readily at the balance point between chaos and order, between flexibility and stability. Scientists believe that emergence, the creation of novelty from agent interaction, happens most readily at this "edge of chaos." The idea of enough structure, but not too much, drives agile managers to continually ask the question, "How little structure can I get away with?" Too much structure stifles creativity. Too little structure breeds inefficiency.

This need to balance at the edge of chaos to foster innovation is one reason process-centric methodologies often fail. They push organizations into over-optimization at the expense of innovation. Agile organizations don't get lost in some gray middle ground; they understand which factors require stabilization and which ones encourage exploration. For example, in a high-change product development environment, rigorous configuration management stabilizes and facilitates flexibility just as a focus on technical excellence stabilizes the development effort. The concepts and practices described in this book are designed to help project teams understand this balancing between flexibility and stability. They help answer the question of what to keep stable and what to let vary.

Agility means being responsive or flexible within a framework or context. As I've said elsewhere, "The problem with many traditional software development and project management approaches is that they have too narrowly defined the context; that is, they've planned projects to a great level of task detail, leaving very little room for agility to actually happen" (Highsmith 2002).

Balancing at the edge of chaos between flexibility and stability requires people who are good improvisers—who have the ability to deal effectively with the ambiguity, and the paradox, of pursuing two seemingly dissimilar goals at once. Organizations that support these improvisers have three key traits:

  • An adaptive culture that embraces change

  • Minimal rules that encourage self-organization, combined with the self-discipline to closely adhere to those rules

  • Intense collaboration and interaction among the project community

Each of these traits will be further described in the chapters on the guiding principles of APM.

The APM Framework

Project management processes and performance measures are different for exploration- and experimentation-based approaches than they are for production- and specification-based ones. Production-oriented project management processes and practices emphasize complete early planning and requirements specification with minimal ongoing change. Exploration-based processes emphasize nominal early planning, good enough requirements, and experimental design with significant ongoing learning and change. Each approach has its place, but the lifecycle framework for the latter has a very different flavor from the former. The APM framework consists of five phases, each with supporting practices. They are Envision, Speculate, Explore, Adapt, and Close.

These phases resemble a scientific investigative process more than a production management process. The Envision phase results in a well-articulated business or product vision—enough to keep the next phases bounded. In the Speculate phase, the team hypothesizes about the specifications of the product, knowing that as the project continues both technology and customer specifications will evolve as new knowledge is gained. The Explore phase then becomes a parallel and iterative operation in which the preliminary specifications and design are implemented. Components labeled "uncertain" are subject to more experimentation than others whose specifications or design are more certain. In the Adapt phase, the results of these experiments are subjected to technical, customer, and business case review, and adaptive actions are incorporated into the next iteration.

One of the most common questions about APM is, "What about the planning, architecture, and requirements phases?" The simple answer is that these things are activities and not phases. An agile approach can easily include as much time for these activities as in a conventional serial phase approach, but the activities are spread across multiple iterations.

A second area of concern is the risk of rework in agile development if the initial architecture work (the discussion in this section could refer to architecture, plans, or requirements) misses a critical item. But there is an equal if not greater risk in serial development that often goes unnamed—that of getting the up-front architecture wrong. In a serial process, the validation of the early architecture decisions comes late in the project lifecycle, when the actual building occurs. By that time, a tremendous amount of time and money has been spent. Changing the architecture then becomes a major, and costly, decision—if it is possible at all.

Within this general APM framework, the successful completion of each phase depends upon a series of key practices that actually guide the work effort. Some of these practices are simple and straightforward, like the product vision box and project data sheet, which I'll discuss in Chapter 5. Others such as customer focus groups and iterative planning are based directly on the core values of agile organizations, while such practices as workload self-management and participatory decision making focus on building an agile, adaptive culture. Values and guiding principles describe the why of APM, and practices describe the how.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020