Home > Articles > Programming

  • Print
  • + Share This
This chapter is from the book

Repair Triage and Change Control Workflows

Let’s review the overall workflow of each phase. This will set a context or map for the topics we will cover. From the perspective of this workflow, we will be looking throughout this text at patterns, examples, and lessons. In the section after this, I offer a detailed commentary on this book’s contents.

Phase 1: Initial Defect Analysis (Low-Level Triage)

Upon initial detection, each defect goes through two steps for gathering initial information and details. The originator of the defect report fills in the complete details from his or her test or usage perspective. He or she then assigns the defect to the development lead or to a specific point resource for handling the initial triage.

The development resource reviews the defect report for reproducibility, completeness, duplication of previous reports, and overall validity. If the description information isn’t complete, it is returned to the originator for more complete information. Chapters 7 and 11 cover the basics of this early defect analysis and management.

Phase 2: High-Level Triage and Change Control Decision-Making

Once we have solid information on the defect, the cross-functional teams need to hold a decision meeting to consider the defect against the current set of defects being worked, the current release criteria, the current release plans, and the impact analysis.

Usually, basic triage and decision-making take the form of a meeting. There is a more formal version of this type of meeting, commonly referred to as a Change Control Board or CCB. The CCB meeting usually has a predefined set of attendees, which gives it a decision-making structure and a scope of change approval that encompasses defects and all substantive changes to the product (requirements, software, hardware, environment, marketing, documentation, manufacturing, and so on). CCB meetings are typically formal in structure, heavy in process weight, and sometimes slow in yielding decisions.

There are much lighter-weight equivalents of CCB meetings, where team members get together to decide what defects get repaired and what enhancements are allowed for a particular project. Such meetings are usually cross-functional but much less formal. Usually, the project manager or one of the team managers leads the decision-making effort and documents the change decisions. In doing so, he or she also focuses only on product defects and enhancements in the endgame, while the formal CCB structures can overlay the entire product life cycle.

No matter what environment or “weight” of methodology you work under, though, every endgame has a project-change decision-making team and mechanism (see Chapter 2 for more details). The team should consider the following points:

  • impact on the release criteria and project focus (Chapter 3)
  • all factors influencing the defect priority
  • all options for resolving the defect
  • workflow, packaging, and schedule timing

Once the change has been approved, the development lead will make some preliminary schedule estimates and will decide who should repair the defect. The lead will also manage work assignments through a work queue, as illustrated in Chapter 10.

Phase 3: Communication

Communicating decisions is an important part of endgame activity, especially since there are so many decisions being made in real-time, every day. This phase is strongly linked to the change control process, so it is an ongoing and constant activity. After any change control decision meeting, the following communication actions need to be taken:

  • update the defect data with all relevant changes from the change control meeting
  • alert the team to read the defect database for status changes. Keep all data in the database! Try not to rely on marked-up printouts, spreadsheets, or any other decentralized tracking methods.
  • post the current status, schedule, progress to date, defect trends, and so on in the war room (see Chapters 13 and 14)
  • publish the change control meeting minutes (see Chapter 2)
  • update the Endgame Release Framework and other plans (see Chapter 4)
  • issue condensed reports to upper management and outer management

Phase 4: Package Analysis

Beyond the individual defect level, your triage and change control team needs to consider the packaging of individual repairs into a release that can be tested, as I discuss in Chapter 10. Usually, this frequency target or cycle time is identified in the Endgame Release Framework (as discussed in Chapter 4) and is a part of the overall release planning for the endgame. However, it is usually only a guideline, requiring frequent adjustments as progress and discoveries are made.

Another factor that comes into play in package determination is the overall productivity of the team. How much can the development team repair and how much can the test team test to make significant progress in stabilizing the release in support of the release criteria? There is a series of balancing acts that need to be achieved in the team’s workflow (see Chapters 10 and 11 for more details).

Phase 5: Repair Scheduling

The next phase, after high-level packaging, is detailed, defect-by-defect assignment, estimation, and repair. This is the real “meat and potatoes” of the endgame activities. Your planning must precede the physical scheduling, which is performed first at the organizational or team level, then at a release framework and package level. Since you will be making repairs at one rate and finding defects at another, this is a very dynamic and iterative process. All of the following steps must be taken:

  • decide on team dynamics—focused individuals or teams, multitasking teams, and level of parallel development
  • develop a release framework or view and plan “packages” (see Chapters 4 and 10)
  • make repair estimates, employing a consistent estimation technique (see Chapter 12)
  • use work queues for defect-repair loading (see Chapter 10)
  • apply consistent strategies for reducing the rate of change (see Chapter 5)

Phase 6: Construction (Repairs)

Simply put, in this phase, the software development team is frenetically making repairs. As an experienced endgame manager, I share many recommendations for repair selection and estimation because I think these are important parts of a properly orchestrated endgame (see Chapters 10, 11, and 12). The insights that may be derived from understanding the scope and complexity of individual repairs is extremely important to endgame decision-making.

Phase 7: Release and Verification

Final assembly and verification serve as closure or “loop back” for the triage and change-control defect-handling phases. The release and verification phase consists of the following activities:

  • builds: frequent check-ins, frequent builds, smoke testing (see Chapter 6)
  • release of the software for testing
  • testing and repair verification
  • + Share This
  • 🔖 Save To Your Account

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