Home > Articles > Software Development & Management

This chapter is from the book

Other Applications

We have examined in detail how the four components of the eSell functional measurement program (CPM extensions, FPE worksheet, PDB, and process) are used in the most common application—namely to perform size, effort, and cost estimates at project kick-off to produce a realistic project plan. The following sections examine some of the other ways these techniques are being used during the sales cycle to improve eSell's traction with its customer base. These are

  • Pre-sales: The make versus buy decision

  • Post-sales: Project staffing

  • During implementation: Project control

Pre-Sales: The Make versus Buy Decision

Do not conclude at this point that the measurement and estimation process provides value only in the post-sales or implementation phases of projects. It is also a key component of the pre-sales environment. Here is a case in point.

When a corporate e-commerce initiative is established, the prudent response of the customer's executive management is to determine whether the solution should be built in-house (make) or purchased from an outside supplier such as eSell (buy). Most IT organizations instinctively look at these projects as make opportunities in which they can learn new technologies and keep their staff busy and productive. From a corporate perspective, however, developing these applications from scratch may not be the most fiscally responsible decision. More often than not, the custom development projects incur large hidden costs: learning curves for new technologies, the team's not knowing what it does not know, inability to manage scope creep, ongoing maintenance and support, and so on. These discoveries can be costly in time, effort, and competitive advantage.

With FP techniques, eSell formulated a quantitative analysis to estimate the cost of making product functionality in-house that was equivalent to what they could buy off the shelf. This showed clearly that buy's advantages far outweighed make's. This Make vs. Buy analysis became a formal sales tool. The analysis (described here) was trivial arithmetically but powerful in its objectivity and quantitative perspective.

  1. A third-party-validated FP application count was done on each off-the-shelf (buy) product to obtain its exact functional Size in FP. In this example, the size of the complete product offering was counted as 3200 FP.

  2. Industry-standard Productivity numbers (FP/Staff-Month or FP/SM) were obtained from various databases, and the average was used. In this example, the average was 10.0 FP/SM, the median between the identified extremes of 8.0 and 12.0.

  3. Estimates of Effort (SM) were calculated, using the above two sets of figures, to show approximately how much time it would take an industry-standard project team to deploy the equivalent functionality (Effort = Size / Productivity). In this example, Effort was calculated at 320 SM or 26.7 Staff-Years (SY).

  4. Industry-standard Loaded Labor Rates ($/SY) for comparable high-tech industries were obtained. These were estimated at $150,000/SY (per employee per year).

  5. Estimates of labor-only Make Cost ($) were calculated by using the effort estimates and the loaded labor rates (Make Cost = Effort * Loaded Labor Rates). This was computed at $4M.

  6. This labor-only cost compared quite unfavorably with the (buy) license fees of the already-released software products (in this case, Buy Cost approximately $1M). This factor of almost 4x was a clear and objective argument that, in this case, buy was a better value than make. Note: the $4M make cost did not, of course, include large, subtle hidden costs such as opportunity loss, time delay, and support and maintenance costs, relegating the make alternative to even lower attractiveness.

eSell's customers found this compelling. They might not have agreed with the exact numbers used, but they found the analysis and argument valid.

Post-Sales: Project Staffing

Another useful application of the FP sizing and estimation process is used in the post-sales time frame. Here the methodology helps the team managers (eSell's and the client's) better determine what skill sets and domain expertise (team roles) must be represented on the project team to have a successful project and how much their time will be impacted. Again, the PDB plays a central role, as follows:

After project kickoff and the FP estimation process, the project managers have an idea of the functional requirements, their size, and the effort required to implement them. In the FPE worksheet, they also have documentation of the productivity factors affecting each ability-to, including the technologies involved. The PDB contains accurate, actual historical data, including the team make-up for each past project. The project manager can cross-reference the estimate data of the new project with historical data in the PDB by finding one or more past projects that best match the new one. Previous efforts by role are used to determine the percentage contribution to the entire project by each role.

For example, for some projects, the Project Manager's contribution absorbs 20 percent of the overall project budget. The Java Developer contingent (this is Web, after all) is 35 percent, the ERP Developer 15 percent, and so on. From this historical data, staffing projections can be done for eSell, partner, and client resources based on role. The appropriate resource with the needed expertise for the required time can be allocated to the team in each case.

During Implementation: Project Control

The final application of functional metrics at eSell is in the area of project control and monitoring during implementation. A measurement process that takes the accuracy of its data seriously also recognizes that accuracy can be achieved only with constant monitoring, remeasuring, and iterative corrections. The project sizing and estimation process described earlier is done at project launch. At that point, there is only an approximation ("educated guess") of what functionality might be required. The sizing estimate for each of those ability-to statements will be fairly accurate (given a good understanding of the function). But even the effort estimate will be somewhat suspect since (a) the predicted productivity factors that influence the timing can only be guessed, (b) inaccuracies exist in the assumptions and risk assessments, and (c) functionality and understanding will mature during the project.

As explained earlier, these inaccuracies are constantly under scrutiny and being corrected, because the final, live project application is FP counted for actual size, and the actual productivity is computed from time-sheet data. But this corrective process is too late for the project itself. Monitoring must be done during the project at key milestones to check progress against the estimate, and then the estimate itself is refined.

Therefore, a pivotal process is used in eSell's project methodology: the Focus Group. At short intervals (typically 3–4 weeks), the project team is convened along with the client's customer representatives—the ultimate end-users. The development product to date is demonstrated for the team, and another pass is made at required functionality. Feedback from the client and their end-users at this point is vital to the success of the final deployment. The list of ability-to statements is revisited. Existing ones (from launch or earlier Focus Groups) are validated, rejected, or postponed, and some new ability-to statements are discovered. These changes dictate the need to recalculate the original sizing and effort estimate.

Another FPE meeting is convened on the revised set of ability-to statements, and a new size and effort estimate is obtained. A supplemental worksheet is used (one outside the scope of this paper) that enables the project team to re-estimate the new size, effort, and budgetary costs. New information such as the following is taken into account:

  • Some work is already completed and delivered and thus paid for.

  • Some work estimated but not started or completed has now been rejected (a cost savings).

  • Some new, unexpected work has been added to the mix.

In fact, some analysis reveals nine combinations of ability-to statements, in two dimensions of 3 X 3. These are Original Work Delivered, Original Undelivered, and New Work versus Approved, Rejected, and Deferred (by the client or end-user). The re-estimation worksheet provides a revised effort and cost estimate for the remaining work. The client can then apply the same line-item-veto process to the revised ability-to statements to assure the remaining costs fit the dollar, resource, and time budgets.

Thus, the fine-grained project-progress monitoring is facilitated by the FP estimation (and re-estimation).

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