Home > Articles > Software Development & Management > Agile

Agile Processes - Emergence of Essential Systems

Agile processes, also known as lightweight processes, are a new paradigm for systems development. This article discusses the role of emergence in agile processes, with Scrum used as the model agile process.
Like this article? We recommend

Like this article? We recommend

Agile Processes: Emergence of Essential Systems

This article discusses the role of emergence in agile processes. Scrum is used as the model agile process. Agile processes, also known as lightweight processes, are used to develop software rapidly, iteratively, and incrementally with sufficient, but no more than sufficient, overhead. The agile processes are based on the empirical model of process control theory, as contrasted to more traditional systems development methodologies, which are based in the defined model of process control theory. More information regarding agile processes is found at www.agilealliance.org.

Systems emerge when built using agile processes. Through iterative, incremental delivery of functionality, business value emerges with every iteration. The architecture and design also emerge iteratively during Scrum and XP projects, a somewhat controversial but nevertheless experientially successful practice. Through emergence, agile processes deliver a product to a customer that maximizes business value. This article describes this occurrence.

For the purposes of this discussion, I will identify two types of systems. The first is the envisioned system, a system as initially foreseen and described by customers to deliver needed business value. The second is the essential system, a system with that minimum set of functionality, architecture, and design that delivers the envisioned system's business value. Business value is defined as the capability that provides business advantage for a certain cost, delivered by a specified date, with adequate quality.

The envisioned system is a starting point for a development project. However, it is not a sufficient or correct description of the system that will deliver the business value. One cause of insufficiency is that the business environment changes during the project. A system that would provide business value at the start of the project often is insufficient by the end of the project. Another reason is communications. When the development team translates the envisioned system into a working set of software, inaccuracies, misunderstandings and lack of knowledge cause inaccuracies.

Still another reason the envisioned system is insufficient is that customers change their minds. Scrum's Uncertainty Principle is the following: "Customers don't know what they want until they see it, and they always reserve the right to change their mind." When the customer sees the envisioned system actually working, they often have different ideas about how this functionality could have best delivered the business value.

A desirable objective is to execute a systems development project that

  1. focuses and delivers the essential system only because anything more is extra cost and maintenance

  2. takes into account that the content of the essential system may change during the course of the project because of changes in business conditions

  3. allows the customer to frequently view working functionality, recommend changes, and have changes incorporated into the system as it is built

  4. delivers business value at the price and cost defined as appropriate by the customer.

Traditional approaches to planning and developing systems cause a business and systems model of the envisioned system to be initially built. Costs and delivery dates are predicted from these models. These models are progressively decomposed into further models that eventually result in an operational set of software. Customer requests for changes from these initial models are handled through extensive change control mechanisms. Most of these change control mechanisms require the user to contractually agree that the cost and date may be changed to adopt the changes. The complexity of change orders discourages customers, resulting in projects without many change orders that don't deliver the desired business value. Alternatively, projects become so enveloped with change orders that the system never gets delivered.

The traditional approach represents a contractually acceptable way for developers to do business with customers. A cost and date can be predicted and contracted. Contractual predictability has driven the entire systems development process into the level of detail and bureaucratic overhead that is currently encountered. It is difficult to build a system that delivers the envisioned business value when this contractual approach is used.

A new, more satisfactory approach to systems development has been described by the agile processes (www.agilealliance.org), and, more specifically, by the Scrum agile process (www.controlchaos.com). This process, which is known as "collaborative," is detailed in the book, Agile Software Development with Scrum by Schwaber and Beedle (Prentice Hall, 2001). Customers and developers collaborate over the life of the project to deliver an essential system with the business value foreseen in the system vision.

The dissatisfaction with the traditional approach was one vector that caused agile processes to arise. The second vector was the significant improvement in software development environments over the last 15 years. The extensive availability of libraries, components, and supporting operational environments negates the need to extensively decompose models into code. The code becomes the only valuable model of the essential system.

All agile processes focus on business value. Customers and developers collaborate during the development project to make changes needed to deliver that value. Agile projects are not constrained to an initial contracted model that must be delivered, whether it provides business value or not.

Each agile process implements collaboration differently. Scrum implements collaboration and focuses on business value in an essential system using two complementary, simultaneous cycles. One cycle sustains a dynamic list of prioritized requirements that, when converted into a working system, will create the highest business value. The other cycle consists of development iterations that build system increments to deliver the highest priority business value. These cycles are constructed so that the most appropriate essential system iteratively emerges during iterations.

These cycles are implemented through the following steps:

  1. A Scrum project starts with the customer's vision of the system. The vision may be vague at first, stated in market terms rather than system terms. The vision will become clearer as the project moves forward. A metaphor of the system is also defined to help guide development and to provide a tangible communication model between customers and developers. An initial vision and metaphor can be usually created in several days if they aren't already part of the customer's business plan.

  2. The customer and development team define requirements that will deliver the highest value business value from the vision. A prioritized list called a Product Backlog is created that consists of these requirements.

  3. The development team works for a short, fixed iteration of 30 days (called Sprints) to create an executable increment that contains the top-priority business value. The team selects as many requirements as they can build during the Sprint. They only build the architecture and design needed to deliver this functionality.

  4. The customer continues defining requirements that will deliver high business value. They are added to the prioritized Product Backlog. The Product Backlog dynamically changes during the project as the business conditions change and through customer response to the product increments created by the development teams.

  5. At the end of every Sprint, the customer reviews the working system increment with the development teams to see whether it delivers the expected business value; if not, what changes need to be made. These changes are added to the Product Backlog and prioritized with the rest of the requirements.

  6. When the customer wants to realize the business value achieved to date, he or she will request that product increments built to date be released. One or more Sprints will be used to polish and implement the system into a releasable product.

The customer steers the cost, date, and business value continuously. By increasing the cost, the customer can cause the delivery of business value sooner. By changing priorities in the Product Backlog, the customer can change the order in which business value is created. By deferring the date, the customer can slow costs. If the customer is dissatisfied with the competence of the developers to understand the business domain and deliver systems that create business value, the customer can terminate the project at any point. The capability to terminate reduces customer risk. Any work completed prior to termination has produced working functionality that may be able to be used by the customer.

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.


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.


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.


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.


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


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


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.


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.


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