SPECIAL NOTICE
D -- RFI: W91CRB_Agile Software Development Methodologies & Cost Estimating
- Notice Date
- 4/5/2022 8:51:13 AM
- Notice Type
- Special Notice
- NAICS
- 511210
— Software Publishers
- Contracting Office
- W6QK ACC-APG ABERDEEN PROVING GROU MD 21005-5001 USA
- ZIP Code
- 21005-5001
- Response Due
- 4/13/2022 7:00:00 AM
- Point of Contact
- Ms. Karen Gibson, Phone: 0000000000, Ms. Lisa J. Yamakawa, Phone: 0000000000
- E-Mail Address
-
karen.gibson2.civ@army.mil, lisa.j.yamakawa.civ@army.mil
(karen.gibson2.civ@army.mil, lisa.j.yamakawa.civ@army.mil)
- Description
- Request for Information (RFI) -� Agile Software Development Methodology and Cost Estimating The U.S. Army Contracting Command-Aberdeen Proving Ground (ACC-APG) is seeking information from industry professionals regarding non-proprietary,�Agile Software development methodologies and associated cost estimating practices. Introduction This Request for Information (RFI) is being submitted in support of Government Cost Analysis Teams, to help build knowledge of the Agile Software development methodology. Information submitted will be used to help develop an Agile Software, cost estimating template that will be used across current and future projects. 1. �This RFI is being issued solely for information and planning purposes. Responses shall not contain any proprietary data or proprietary estimating methods from the responding company. Various concepts may be examined based upon input provided. The contracting organization responsible for this effort is Army Contracting Command � Aberdeen Proving Ground (ACC-APG). Telephone requests for additional information or to request a meeting to discuss this request will not be honored. 2. This RFI does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. A solicitation is not available at this time; Requests for a solicitation will not receive a response; unsolicited proposal responses to this request will not be considered as offers. This notice does not constitute a commitment by the United States Government to contract for any supply or service whatsoever. All information submitted in response to this announcement is voluntary, therefore the United States Government will not pay for information requested nor will it compensate any respondent for any cost incurred in developing information provided to the United States Government. 3. Not responding to this RFI does not preclude any vendor from participating in any future RFP, if any is issued. If a solicitation is released, it will be synopsized via the System for Award Management (SAM.gov) website. It is the responsibility of vendors to monitor this website for additional information pertaining to this requirement. Cost Estimation Areas of Interest Provide answers to the following questions below to highlight processes and approaches but do not include any company proprietary data. Data will not be shared and is for internal, Government use only. Requirements� How are software products defined for delivery? By sprint count? Builds? Drops? Other? How are development costs determined per project? Biggest cost drivers? How is the size of the development team determined? (e.g. number of FTEs) What would be some (if any) Non-recurring development costs that would be passed on to the Government by the developer? What historical knowledge can be shared from previous Agile Software methodology projects that exposed cost challenges? Schedule� How is the cost determined for the sprint schedules? Is the time between sprints consistent or is it determined as development progresses? Who should be communicating to cost team in regards to critical path and updates to road map? Backlog? What are some key dependencies to identify when prioritizing road map milestones/backlog? What features should be used when tracing the schedule horizontally/vertically? How often should a schedule risk analysis be conducted? How is Earned Value Management (EVM) measured in a cost perspective? Team Is the level of expertise assigned to a labor force an overall rate, or is it determined for each sprint? If so, what kind of breakout is used to identify the various expertise? Are rates determined per sprint or per hour? Does an Agile Software developer have their own internal cost analyst? What are their key cost measurements? How often should an IPT meet during development and implementation? Experience and Qualifications Describe your organization's size, qualifications and experiences regarding development of an Agile Software development and utilization methodology and/or Agile Software cost estimation process that can be of assistance in developing an Agile Software cost estimating template. RFI Response: Format and Submission Respondents are requested to highlight their industry experience with cost estimation for Agile Software development and utilization based upon the information and requirements presented in this RFI. Responses are limited to the following: a page limit of five (5) pages maximum, typed in Times New Roman, size 12 font, single spaced, one (1) inch margins.� 1. The Vendor responses to this notice shall include the following information: Vendor's name, address, business size (Large, Small, or any other small/socio-economic type), point of contact, phone number, and e-mail address. Vendor's detailed description of their experience with Agile Software and/or Agile Software cost estimation. 2. Vendor responses to this notice shall be submitted to: Points of Contact: Ms. Karen Gibson (Karen.gibson2.civ@army.mil) and Ms. Lisa J. Yamakawa (lisa.j.yamakawa.civ@army.mil). Time/Date: Responses shall be submitted to the above stated Points of Contact no later than 10:00 a.m. Eastern Daylight Time on Wednesday, 13 April 2022.
- Web Link
-
SAM.gov Permalink
(https://sam.gov/opp/cea907b7e6414ad69fa1852a8b7b0019/view)
- Record
- SN06289293-F 20220407/220405230054 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |