Home > Articles > Software Development & Management > Agile

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

Risk and Value Driven

The DAD process framework adopts what is called a risk/value lifecycle, effectively a lightweight version of the strategy promoted by the Unified Process (UP). DAD teams strive to address common project risks, such as coming to stakeholder consensus around the vision and proving the architecture early in the lifecycle. DAD also includes explicit checks for continued project viability, whether sufficient functionality has been produced, and whether the solution is production ready. It is also value driven, a strategy that reduces delivery risk, in that DAD teams produce potentially consumable solutions on a regular basis.

It has been said “attack the risks before they attack you.” This is a philosophy consistent with the DAD approach. DAD adopts what is called a risk-value driven lifecycle, an extension of the value-driven lifecycle common to methods such as Scrum and XP. With a value-driven lifecycle you produce potentially shippable software every iteration or, more accurately from a DAD perspective, a potentially consumable solution every iteration. The features delivered represent those in the requirements backlog that are of highest value from the perspective of the stakeholders. With a risk-value driven lifecycle you also consider features related to risk as high priority items, not just high-value features. With this in mind we explicitly address risks common to IT delivery projects as soon as we possibly can. Value-driven lifecycles address three important risks—the risk of not delivering at all, the risk of delivering the wrong functionality, and political risks resulting from lack of visibility into what the team is producing. Addressing these risks is a great start, but it’s not the full risk mitigation picture.

First and foremost, DAD includes and extends standard strategies of agile development methods to reduce common IT delivery risks:

  • Potentially consumable solutions. DAD teams produce potentially consumable solutions every construction iteration, extending Scrum’s strategy of potentially shippable software to address usability concerns (the consumability aspect) and the wider issue of producing solutions and not just software. This reduces delivery risk because the stakeholders are given the option to have the solution delivered into production when it makes sense to do so.
  • Iteration demos. At the end of each construction iteration the team should demo what they have built to their key stakeholders. The primary goal is to obtain feedback from the stakeholders and thereby improve the solution they’re producing, decreasing functionality risk. A secondary goal is to indicate the health of the project by showing their completed work, thereby decreasing political risk (assuming the team is working successfully).
  • Active stakeholder participation. The basic idea is that not only should stakeholders, or their representatives (i.e., product owners), provide information and make decisions in a timely manner, they can also be actively involved in the development effort itself. For example, stakeholders can often be actively involved in modeling when inclusive tools such as paper and whiteboards are used. Active stakeholder involvement through the entire iteration, and not just at demos, helps to reduce both delivery and functionality risk due to the greater opportunities to provide feedback to the team.

DAD extends current agile strategies for addressing risk on IT delivery projects, but also adopts explicit, lightweight milestones to further reduce risk. At each of these milestones an explicit assessment as to the viability of the project is made by key stakeholders and a decision as to whether the project should proceed is made. These milestones, indicated on the DAD lifecycle depicted previously in Figure 1.3, are

  • Stakeholder consensus. Held at the end of the Inception phase, the goal of this milestone is to ensure that the project stakeholders have come to a reasonable consensus as to the vision of the release. By coming to this agreement we reduce both functionality and delivery risk substantially even though little investment has been made to date in the development of a working solution. Note that the right outcome for the business may in fact be that stakeholder consensus cannot be reached for a given project vision. Our experience is that you should actually expect to cancel upwards to10% of your projects at this milestone, and potentially 25% of projects that find themselves in scaling situations (and are therefore higher risk).
  • Proven architecture. In the early Construction phase iterations we are concerned with reducing most of the risk and uncertainty related to the project. Risk can be related to many things, such as requirements uncertainty, team productivity, business risk, and schedule risk. However, at this point in time much of the risk on an IT delivery project is typically related to technology, specifically at the architecture level. Although the high-level architecture models created during the Inception phase are helpful for thinking through the architecture, the only way to be truly sure that the architecture can support the requirements is by proving it with working code. This is a vertical slice through the software and hardware tiers that touches all points of the architecture from end to end. In the UP this is referred to as “architectural coverage” and in XP as a “steel thread” or “tracer bullet.” By writing software to prove out the architecture DAD teams greatly reduce a large source of technical risk and uncertainty by discovering and then addressing any deficiencies in their architecture early in the project.
  • Continued viability. In Scrum the idea is that at the end of each sprint (iteration) your stakeholders consider the viability of your project. In theory this is a great idea, but in practice it rarely seems to happen. The cause of this problem is varied—perhaps the stakeholders being asked to make this decision have too much political stake in the project to back out of it unless things get really bad, and perhaps psychologically people don’t notice that a project gets into trouble in the small periods of time typical of agile iterations. The implication is that you need to have purposeful milestone reviews where the viability of the project is explicitly considered. We suggest that for a given release you want to do this at least twice, so for a six month project you would do it every second month, and for longer projects minimally once a quarter.
  • Sufficient functionality. The Construction phase milestone is reached when enough functionality has been completed to justify the expense of transitioning the solution into production. The solution must meet the acceptance criteria agreed to earlier in the project, or be close enough that it is likely any critical quality issues will be addressed during the Transition phase.
  • Production ready. At the end of the Transition phase your key stakeholders need to determine whether the solution should be released into production. At this milestone, the business stakeholders are satisfied with and accept the solution and the operations and support staff are satisfied with the relevant procedures and documentation.
  • Delighted stakeholders. The solution is running in production and stakeholders have indicated they are delighted with it.
  • + 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.

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