Agile Professional Services _ APS _ Questions and Answers as of 07.09.2026.xlsx
XLSX spreadsheet 44 KB Posted
- Attached to
- Agile Professional Services _CPE ST3
- Solicitation number
- W900KK-26-ST3-Professional-Services
About this file
This is a Questions and Answers document for the Agile Professional Services (APS) procurement by the Department of the Army Materiel Command, Contracting Command Orlando, on behalf of Capability Program Executive Simulation, Training, Test & Threat (CPE ST3). The document addresses 107 questions submitted by industry regarding the acquisition strategy, contract structure, performance expectations, and operational governance for professional services supporting CPE ST3's portfolio of over 370 products deployed at more than 400 locations worldwide.
The Government has finalized its acquisition strategy as a FAR Part 12 Request for Proposal to be solicited as a total small business set-aside, with a Draft RFP released in July 2026 and final proposals due in August 2026, targeting award in October/November 2026 and full operational execution by February 2027. The requirement includes a mandatory 6-month Prototype Phase serving as a discovery and validation gate, followed by a 54-month performance period under a Fixed Price-Labor Hour (FP-LH) contract structure. Services encompass product management, engineering support, digital engineering, DevSecOps integration, validation and verification, test planning and execution, training support, data analytics, and sustainment planning, delivered through a Scaled Agile Framework (SAFe) or equivalent Agile methodology. Key performance considerations include stakeholder coordination, organizational change management, and Agile governance facilitation as core deliverables during the prototype phase, transitioning to inherent operational responsibilities thereafter. The Government emphasizes that contractors will not be held liable under CPARS for Government-caused delays, incomplete stakeholder participation, or organizational maturation gaps, with all operational information provided via SAM.gov to ensure equitable competition. NAICS code 541330 applies, and organizational conflicts of interest will be governed by FAR Subpart 9.5, with clarifying OCI statements to be included in the draft RFP.
View the file
Other files
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Draft CSO Questions
| Question # | QUESTION DETAIL | GOVERNMENT RESPONSE | STATUS |
| 1 | Did more than one small business respond to the RFI sufficiently? Are the subcontractors performing well on the current contract? The company I work for gives CPE ST3 a true opportunity to start fresh providing these same Agile solutions for other Army customers, is CPE ST3 okay with a total reset or would they prefer a company who has experience in that office? | Yes, more than one small business responded to the RFI. Prior experience with CPE ST3 is not required and not necessarily preferred. | Final |
| 2 | During Industry Day, the Government stated that multiple acquisition approaches remain under consideration, including OASIS+, MAPS, FAR-based acquisition approaches, OTA/prototype-based approaches, and potential hybrid acquisition structures. The Government also indicated that legal and procurement developments associated with MAPS and related acquisition considerations may not be fully resolved until later in the acquisition cycle.Given the currently projected schedule of Draft RFP release in June 2026, Final RFP release in July 2026, proposal submissions in August 2026, award in October/November 2026, transition activities immediately thereafter, and full operational execution by February 2027, how does the Government intend to ensure that sufficient acquisition, operational, governance, and organizational maturity exists prior to Final RFP release to support stable proposal development, realistic pricing, executable transition planning, equitable competition, and sustainable enterprise-wide operational execution? | The FINAL Acquisition Strategy has been determined to be a FAR Part 12 Request for Proposal. |
| The requirement exists to determine all prospective awardees "Responsible" prior to issuance of any award. Offeror porposals and entity data will be used to ascertain whether offerors can be determined to be "Responsible, in accordance with statutory and regulatory requirements. | Final | |||||||||||||||
| 3 | What acquisition-planning analysis consistent with FAR Part 7 has the Government performed to validate that the enterprise environment, backlog maturity, governance structure, organizational readiness, and transformation scope are sufficiently mature to support the proposed acquisition strategy and implementation timeline? | Government conducted a rigorous business-case analysis that determined full enterprise maturity is not a prerequisite for award, but rather a capability to be systematically proven. By structuring the procurement around an initial 6-month Prototype CLIN, the Government has directly aligned its acquisition planning with the current "as-is" state of the organization. This prototyping strategy allows the Government to validate the technical environment, baseline backlog maturity, and test the proposed governance structure within a controlled, representative pilot environment, effectively mitigating enterprise-wide transformation risks and establishing objective, data-driven maturity baselines before committing to a full-scale production rollout. | Final | Statuses | Responding POC | Troy Darling | Rodney Figaroa | Lovisa Parks | Sophia Dasilva | Christina Bell | Richard Beljour | Theresa Barkdoll | Constance Hastings | Branden Smith | Redundant | |
| 4 | During Industry Day, the Government repeatedly encouraged industry to provide tracked changes, recommend acquisition approaches, propose Agile governance structures, recommend enterprise operating models, suggest pricing methodologies, and rewrite portions of the PWS and Agile execution framework. Because industry feedback may materially influence the acquisition strategy, operating construct, pricing framework, evaluation methodology, Agile governance structure, and execution model itself, how does the Government intend to ensure that all offerors ultimately compete against a common operational baseline with standardized enterprise assumptions, normalized governance expectations, and objectively comparable evaluation criteria consistent with FAR Part 15 principles? | The FINAL Acquisition Strategy has been determined to be a FAR Part 12 Request for Proposal. |
| The requirement exists to determine all prospective awardees "Responsible" prior to issuance of any award. Offeror porposals and entity data will be used to ascertain whether offerors can be determined to be "Responsible, in accordance with statutory and regulatory requirements. | Final | Pending | Troy Darling | ||
| 5 | Additionally, does the Government anticipate additional industry engagement sessions, revised Draft RFP releases, iterative PWS refinement cycles, operational scenario workshops, or phased acquisition feedback activities prior to issuance of the Final RFP? | The FINAL Acquisition Strategy has been determined to be a FAR Part 12 Request for Proposal. |
| The Government intends to issue a draft RFP in July, with a fresh opportunity for Q&A. | Final | Draft | Sophia Dasilva | ||
| 6 | During Industry Day, the Government stated that its market research identified two or more viable small businesses capable of performing the contemplated requirement. Given FAR 19.502-2(b), which establishes the Rule of Two and generally requires a total small business set-aside when there is a reasonable expectation that offers will be received from at least two responsible small business concerns at fair market prices, how has the Government incorporated these market research findings into its acquisition planning and source-selection strategy? | The final Acquisition Strategy has been determined to be a FAR Part 12 Request for Proposal, to be solicited under a total small business set-aside. | |||
| Final | Final | Constance Hastings | |||
| 7 | Additionally, if the Government intends to pursue an acquisition approach other than a total small business set-aside, what specific market research, capability analysis, mission requirements, risk considerations, or pricing rationale support that determination? | The final Acquisition Strategy has been determined to be a FAR Part 12 Request for Proposal, to be solicited under a total small business set-aside. | |||
| Final | Theresa Barkdoll | ||||
| 8 | Finally, how does the Government intend to ensure that any deviation from a total small business set-aside approach remains consistent with the underlying objectives of FAR Part 19 and is supported by a documented acquisition rationale capable of withstanding future scrutiny? | The requirements of FAR 52.219-14 WILL apply to the resultant FAR-Based contract. |
| Final | Rodney Figaroa | ||
| 9 | The Government stated during Industry Day that several foundational areas of the acquisition remain under active evolution, including the acquisition strategy, pricing structure, evaluation methodology, OCI framework, Agile governance model, backlog-management approach, dynamic resource-allocation methodology, and overall enterprise operating structure. At the same time, industry is being encouraged to propose materially different Agile implementation strategies, governance models, staffing approaches, tooling ecosystems, Release Train structures, backlog-management methodologies, Product Owner engagement models, and enterprise transformation approaches. Because these differing assumptions may materially impact staffing levels, pricing models, operational scalability, lifecycle cost, implementation complexity, and execution risk, how does the Government intend to normalize materially different proposal assumptions during technical and price evaluation to ensure objective proposal comparability, equitable competition, pricing-realism consistency, defensible best-value determinations, and protest-resistant source-selection outcomes consistent with FAR Part 15? | The purpose under a FAR Part 12 is that Evaluation will be conducted based on the specific merit-based criteria outlined in the RFP, rather than against a rigid, standardized technical baseline. |
| Final | Lovisa Parks | |||||
| 10 | If the Government proceeds using an OTA, prototype-based, or hybrid acquisition approach in which industry is effectively being asked to help shape the enterprise operating model, Agile governance structure, pricing assumptions, evaluation methodology, and portions of the PWS itself, how does the Government intend to distinguish between innovation and execution risk while maintaining objective and consistent source-selection evaluation across proposals that may represent fundamentally different enterprise operating philosophies? | The final Acquisition Strategy has been determined to be a FAR Part 12 Request for Proposal, to be solicited under a total small business set-aside. | ||||
| Final | Christina Bell | |||||
| 11 | Will the Government provide visibility prior to Final RFP release into which industry recommendations are accepted, how the PWS evolves between Draft and Final RFP, and whether material changes occur to the enterprise governance structure, backlog-management expectations, pricing framework, Agile operating model, evaluation methodology, organizational transformation responsibilities, or Government participation expectations? | No, offeror proposed PWS documents represent their own respective intellectual property and will be considered source selection sensitive. | Final | Branden Smith | ||
| 12 | Additionally, how does the Government intend to ensure that all offerors receive equivalent operational information and normalized enterprise assumptions so that no offeror gains a competitive advantage based upon differing interpretations of evolving Government expectations, operating constructs, or transformation responsibilities? | All "Operational Information" will be provided in the SAM.Gov posting, to ensure that no prospective offeror received priveledged information or a competitive advantage. | Final | Richard Beljour | ||
| 13 | The Government emphasized during Industry Day that enterprise success will require dynamic allocation of resources, enterprise-level Agile synchronization, sustained Government stakeholder participation, and significant organizational transformation across multiple mission and support organizations. The Government also acknowledged that portions of the organization are not yet fully prepared for Agile accountability and operational participation expectations. Because successful enterprise Agile execution requires sustained Government engagement in backlog refinement, prioritization, sprint planning, PI planning, dependency resolution, acceptance activities, and enterprise synchronization, how does the Government intend to establish stakeholder accountability, manage organizational resistance, and ensure consistent Government participation across organizations with varying levels of Agile maturity? | The plan for inculcating Agile into the Government SOP is neccessarily a component of the project proposal. The Government has been clear that this is a key weakness and we are seeking innovative ideas from offerors as to how the organizational culture of resistance could be mitigated. | Final | |||
| 14 | Finally, how will the Government evaluate contractor performance and CPARS outcomes under FAR 42.15 in situations where mission execution challenges are materially impacted by inconsistent Government participation, delayed stakeholder decisions, organizational resistance, or incomplete Government Agile adoption? | Under FAR 52.249 and 52.212-4 contractors shall not be liable for acts of Government. | Final | |||
| 15 | Under an FFP contract structure governed by FAR Part 16 principles, how does the Government intend to distinguish between normal Agile reprioritization, enterprise transformation activities, operational workload growth, Government-directed changes, and scope expansion requiring contractual modification or equitable adjustment? | |||||
| The Government distinguishes Agile flexibility from contractual scope expansion by tying flexibility to capacity rather than open-ended requirements. Normal Agile reprioritization and baseline enterprise transformation activities are covered under the core FP-LH contract and managed dynamically via the Product Backlog without requiring contract modifications. Conversely, operational workload growth, Government-directed changes or out-of-scope expansions will be managed through contract actions. | Final | |||||
| 16 | Additionally, what contractual and governance mechanisms does the Government intend to establish to prevent excessive post-award change activity, pricing escalation, operational disputes, and execution instability resulting from evolving enterprise assumptions that may not yet be fully mature at the time of award? | To prevent post-award instability and pricing escalation under immature enterprise conditions, the Government is establishing the 6-month Prototype phase as a mandatory contractual "Discovery and Validation" gate. | Final | |||
| 17 | Because contractors may therefore expend significant effort supporting stakeholder coordination, governance facilitation, Agile coaching, dependency management, organizational change management, and operational relationship management activities that are not traditionally associated with standard professional-services execution, how does the Government intend to account for those transformation-related activities within the proposed pricing structure and performance expectations? | |||||
| The Government explicitly accounts for stakeholder coordination, Agile coaching, and organizational change management (OCM) by designating them as direct, core deliverables within the 6-month Prototype pricing structure, rather than treating them as administrative overhead. | Final | |||||
| 18 | Additionally, will those efforts be treated as inherent operational responsibilities, separately priced transformation activities, optional support services, or Government-led responsibilities? |
| The Government intends to treat these transformation-enabling efforts (coaching, OCM, and governance facilitation) as separately priced transformation activities during the initial 6-month Prototype Phase, which then transition into inherent operational responsibilities embedded within the baseline Fixed Price - Labor Hour (FP-LH) 54-month Performance Period. Throughout the entire 60-month lifecycle, the final authority to enforce compliance remains a strictly Government-led responsibility. | Final | |||
| 19 | Finally, how will the Government prevent unpriced organizational-transformation obligations from creating execution risk, pricing instability, excessive equitable-adjustment activity, and increased CPARS exposure under FAR 42.15 associated with factors outside the contractor’s reasonable control? | This will, neccessarily be a function of Contractor/COR/KO Change Management and control coordination. In no event, shall the contractor be held liable (under CPARS or otherwise) for Government caused delays or disruptions. | Final | |
| 20 | Because dynamic enterprise resource allocation may materially impact staffing stability, labor utilization, workload predictability, surge support expectations, and operational continuity, how does the Government intend to define the operational and contractual boundaries of dynamic resource allocation under an FFP construct consistent with FAR Part 16 risk-allocation principles? | That will, in large part, be a function to be defined by respective offerors. The Government is receptive to all proposed solutions, and will finalize Government controls based on the selected Solution. | Final | |
| 21 | Additionally, how will the Government ensure that continuous reprioritization and enterprise-wide resource shifting do not unintentionally create hidden workload growth, staffing inefficiencies, operational instability, or recurring contractual disputes regarding scope, pricing responsibility, and performance accountability? | That will, in large part, be a function to be defined by respective offerors. The Government is receptive to all proposed solutions, and will finalize Government controls based on the selected Solution. | Final | |
| 22 | Does the Government intend to consider phased pricing approaches, transition CLINs, pilot execution periods, hybrid contract structures, or limited Time-and-Materials elements during early enterprise transformation activities until backlog maturity, governance consistency, organizational participation, and operational baselines stabilize across the enterprise? If not, how does the Government intend to mitigate the substantial execution and pricing risk associated with implementing a large-scale enterprise Agile transformation under a fully FFP construct prior to achieving the reasonably stable operational environment contemplated under FAR 16.202-1? | This is a particular area of interest from the Government, as proposed transition and performance architecture are intended to be workproducts of the Offeror. This will include prospective CLIN structures during the formal Proposal phase of the Evaluation. The Government intents to execute a 6-month Prototype Phase, which then transitions to a 54-month performance period. | Final | |
| 23 | How does the Government intend to evaluate contractor performance and CPARS outcomes under FAR 42.15 in situations where delivery challenges are materially impacted by inconsistent Government participation, delayed stakeholder decisions, unresolved prioritization conflicts, incomplete Product Owner engagement, organizational resistance, or evolving Government governance structures | This will, neccessarily be a function of Contractor/COR/KO Change Management and control coordination. In no event, shall the contractor be held liable (under CPARS or otherwise) for Government caused delays or disruptions. | Final | |
| 24 | Additionally, what safeguards will the Government establish to ensure contractors are not negatively evaluated for execution challenges materially driven by Government organizational immaturity or incomplete enterprise Agile adoption? | In no event shall the contractor be held liable (under CPARS or otherwise) for Government caused delays or disruptions. | Final | |
| 25 | Because OCI determinations may materially impact teaming strategies, subcontractor participation, incumbent transition planning, competitive positioning, and long-term business decisions across the industrial base, when does the Government intend to release formal OCI guidance defining future competition limitations, affiliate restrictions, subcontractor participation boundaries, firewall expectations, organizational-separation requirements, and long-term eligibility implications? | The general rules in 9.505-1 through 9.505-4 prescribe limitations on contracting as the means of avoiding, neutralizing, or mitigating organizational conflicts of interest that might otherwise exist in the stated situations. | Final | |
| 26 | Additionally, how will the Government ensure that OCI guidance remains sufficiently stable throughout the acquisition lifecycle to allow industry to make informed and responsible teaming, staffing, and investment decisions? | The general rules in 9.505-1 through 9.505-4 prescribe limitations on contracting as the means of avoiding, neutralizing, or mitigating organizational conflicts of interest that might otherwise exist in the stated situations. | Final | |
| 27 | The Government stated during Industry Day that even subcontractors may ultimately be restricted to participating on only one side of the acquisition due to potential OCI considerations. Because this restriction could significantly impact specialized teaming arrangements, small-business participation, incumbent transition strategies, and access to highly specialized technical expertise, how does the Government intend to ensure that OCI restrictions implemented pursuant to FAR Subpart 9.5 do not unintentionally reduce competition, constrain innovation, limit access to critical expertise, reduce small-business participation, or create uneven competitive conditions across offerors? | The primary interest concerned with OCI mitigation is the preservation of Procurement Integrity, and thus some impact is deemed acceptable. That said, the Government does not intend to exceed the standards set in FAR 9.505-1 through 9.505-4. | Final | |
| 28 | Additionally, how will the Government prevent differing OCI interpretations, evolving acquisition strategies, or inconsistent mitigation standards from creating unequal competitive conditions or materially different participation limitations across offerors? | The final Acquisition Strategy has been determined to be a FAR Part 12 Request for Proposal, to be solicited under a total small business set-aside. |
| A clarifying OCI statement will be included in the forthcoming RFP. | Final | |||
| 29 | Will the Government provide a formal process through which offerors may seek OCI clarification, validate proposed teaming structures, request advisory opinions, or obtain pre-award guidance regarding proposed mitigation approaches prior to Final proposal submission? | No, not until later in the evaluation, as will be disclosed in the draft RFP, where an OCI disclosure and Mitigation Plan will be required. All offerors are expected to understand the OCI outlook through the prizm of FAR 9.5, and to be prepared to address any real or aparent conflicts of interest. | Final | |
| 30 | Additionally, how will the Government distinguish between contractor performance deficiencies and enterprise execution challenges materially driven by Government organizational maturity, stakeholder participation gaps, or evolving governance structures when evaluating contractor performance and CPARS outcomes under FAR 42.15? | This will, neccessarily be a function of Contractor/COR/KO Change Management and control coordination. In no event, shall the contractor be held liable (under CPARS or otherwise) for Government caused delays or disruptions. | Final | |
| 31 | Finally, how will the Government ensure that contractors are not negatively evaluated for mission delays or operational instability materially driven by incomplete Government organizational adoption or stakeholder participation challenges? | This will, neccessarily be a function of Contractor/COR/KO Change Management and control coordination. In no event, shall the contractor be held liable (under CPARS or otherwise) for Government caused delays or disruptions. | Final | |
| 32 | Additionally, what mechanisms will the Government establish to ensure that evolving governance structures or changing reporting expectations do not unintentionally create hidden workload growth, inconsistent performance measurement, operational inefficiencies, or recurring contractual disputes regarding reporting responsibility and execution accountability? | Answered Elsewhere | Final | |
| 33 | If so, what authority will that organization possess relative to PMs, PLs, HQ organizations, acquisition portfolios, cyber activities, and mission-support organizations operating under separate leadership structures and operational priorities? | Answered Elsewhere | Final | |
| 34 | Because enterprise Agile transformation activities may require substantial stakeholder coordination, executive alignment, governance facilitation, organizational coaching, relationship management, and cultural adaptation support, how does the Government intend to define the contractual boundaries between operational execution responsibilities, enterprise transformation activities, stakeholder coaching, Government-led change management, and organizational adoption support? | Answered Elsewhere | Final | |
| 35 | Additionally, will those activities be treated as inherent operational execution requirements, separately priced transformation services, optional support activities, or Government-furnished responsibilities? | Answered Elsewhere | Final | |
| 36 | How does the Government intend to measure and enforce Government stakeholder participation and organizational accountability throughout execution, particularly in situations where Product Owner engagement is inconsistent, operational decisions are delayed, backlog priorities conflict, governance responsibilities remain unclear, or organizational resistance materially impacts Agile execution activities? | Answered Elsewhere | Final | |
| 37 | ecause enterprise Agile transformation within professional-services environments has historically varied significantly across both Government and industry implementations, and because no universally standardized SAFe operating construct currently exists for large-scale enterprise professional-services execution, offerors may reasonably propose materially different transformation methodologies, governance frameworks, stakeholder-engagement approaches, Release Train structures, organizational-alignment models, and operational execution philosophies. How does the Government intend to normalize these differing transformation assumptions during technical evaluation to ensure equitable competition, objective proposal comparability, defensible best-value determinations, and protest-resistant source-selection outcomes consistent with FAR Part 15 principles? | Answered Elsewhere | Final | |
| 38 | Additionally, what standardized transformation baseline or enterprise operating framework will the Government establish to ensure proposals are evaluated against consistent organizational expectations rather than differing interpretations of Agile transformation philosophy and implementation maturity? | Answered Elsewhere | Final | |
| 39 | Because organizational maturity, stakeholder participation, governance consistency, and operational readiness may continue evolving after award, how does the Government intend to prevent continuous organizational change activities from creating recurring operational instability, excessive reprioritization, hidden workload growth, workforce burnout, staffing inefficiencies, or repeated contractual disputes regarding transformation responsibilities and operational accountability? | Answered Elsewhere | Final | |
| 40 | Additionally, what governance mechanisms will exist to ensure that enterprise transformation activities remain operationally sustainable, measurable, and aligned to clearly defined contractual and organizational responsibilities throughout the lifecycle of the program? | Answered Elsewhere | Final | |
| 41 | The draft PWS requires implementation of SAFe or an equivalent Agile methodology across all task areas. Has the Government identified designated Product Owners, Business Owners, Release Train Engineers, Scrum Masters, and decision authorities for each value stream, PMO, and HQ directorate? | Answered Elsewhere | Final | |
| 42 | Will Government Product Owners be formally identified before award, and will they have delegated authority to prioritize backlog items, approve sprint objectives, accept completed work, and make tradeoff decisions during execution? | Answered Elsewhere | Final | |
| 43 | How will the Government ensure consistent participation of Government Product Owners and stakeholders during backlog refinement, sprint planning, PI planning, sprint reviews, retrospectives, and acceptance activities? | Answered Elsewhere | Final | |
| 44 | Has the Government established an enterprise Agile governance framework that defines decision rights, backlog ownership, escalation paths, impediment resolution, release approval, and acceptance authority? | Answered Elsewhere | Final | |
| 45 | If PI planning is required, what cadence does the Government anticipate for PI planning, system demos, Inspect-and-Adapt events, portfolio syncs, and enterprise synchronization across geographically dispersed teams? | Answered Elsewhere | Final | |
| 46 | How will the Government synchronize priorities and dependencies across PMOs, HQ directorates, acquisition portfolios, cyber directives, FMS activities, and mission requirements operating under separate funding lines? | Answered Elsewhere | Final | |
| 47 | The PWS requires backlog management and prioritization. What process will the Government use to adjudicate competing priorities across PMOs, HQ organizations, operational requirements, cyber directives, urgent acquisition actions, and emergent taskings? | Answered Elsewhere | Final | |
| 48 | How will the Government manage unplanned operational work, emergent cyber taskings, urgent acquisition requests, external dependencies, and leadership-directed changes within committed sprint or PI objectives? | Redundant | Final | |
| 49 | The transcript indicates the Government is considering dynamic resource allocation as a major discriminator. How will the Government define, evaluate, and measure successful dynamic resource allocation across enterprise priorities? | Redundant | Final | |
| 50 | What authority will the contractor have to recommend or execute resource reallocation when demand exceeds capacity, and what Government approvals will be required before moving resources between PMs/PLs, HQ, FMS, cyber, test, or acquisition activities? | Redundant | Final | |
| 51 | Will the Government provide historical workload data for more than three months, including completed tasks, cycle times, surge periods, task complexity, labor categories used, acceptance timelines, and defect/rework history? | Redundant | Final | |
| 52 | Will the Government define enterprise Jira standards, including issue hierarchy, workflow states, required fields, taxonomy, Definition of Ready, Definition of Done, story-point estimation, dependency tracking, risk tagging, release tagging, and sprint closure rules? | Redundant | Final | |
| 53 | The Government has expressed interest in a Firm Fixed Price. What workload baseline, service levels, acceptance criteria, task volume assumptions, surge assumptions, and Government-furnished data will be provided to enable offerors to submit a realistic FFP proposal? | Redundant | Final | |
| 54 | Has the Government determined which portions of the requirement are suitable for FFP versus Time and Materials, Labor Hour, or hybrid pricing, particularly for emergent mission work, surge support, cyber response, and cross-enterprise tasking? | Redundant | Final | |
| 55 | How will the Government evaluate price reasonableness if offerors make different assumptions about workload volume, backlog quality, staffing capacity, Agile maturity, Government availability, and surge demand? | Redundant | Final | |
| 56 | If priorities shift mid-sprint or mid-PI due to CPE leadership direction, emergent threats, cyber directives, funding changes, or acquisition urgency, will the Government treat that as in-scope Agile reprioritization or as a contract change requiring adjustment? | Redundant | Final | |
| 57 | Will the Government establish standardized KPI definitions across all task orders to ensure consistent measurement of Agile maturity, sprint predictability, backlog health, delivery quality, stakeholder acceptance, and mission impact? | Redundant | Final | |
| 58 | How will the Government correlate Agile performance metrics with acquisition outcomes, operational readiness, Warfighter capability delivery, test-event readiness, cybersecurity compliance, and schedule performance? | Redundant | Final | |
| 59 | The PWS references a shift from staffing-based execution to outcome-focused Agile delivery. Has the Government conducted an Agile maturity assessment across PMOs, PLs, HQ directorates, and current contractor teams to determine readiness for SAFe implementation? | Redundant | Final | |
| 60 | What organizational change management activities will the Government perform internally to address active resistance, inconsistent Agile adoption, legacy waterfall governance, and Government personnel who are not currently managing backlogs or participating in Agile ceremonies effectively? | Redundant | Final | |
| 61 | Does the Government intend to establish a Lean Agile Center of Excellence or an enterprise transformation office to govern Agile adoption, coaching, maturity measurement, process standardization, and continuous improvement across CPE ST3? | Redundant | Final | |
| 62 | The transition section requires migration to an Agile Program Management model. Will Agile transformation activities occur during transition-in, after full operational performance begins, or as a separately scoped and priced transformation workstream? | Redundant | Final | |
| 63 | Given the Government’s continued refinement of the PWS, vehicle, pricing model, evaluation approach, Jira data set, Agile governance model, and SAFe operating construct, will the Government consider releasing an updated draft PWS, sample backlog, evaluation scenario, pricing assumptions, and Agile governance model for industry review before requesting final proposals? | Redundant | Final | |
| 64 | The Government has indicated that available Jira/backlog data may have limitations. What validation has the Government performed to confirm that the data provided to offerors is accurate, representative of the expected workload, and sufficient to support the development of technical approaches, staffing assumptions, and Firm Fixed Price pricing? | Redundant | Final | |
| 65 | How will the Government define and validate successful performance under this Agile Professional Services model, including measurable outcomes, acceptance criteria, mission-value metrics, and the distinction between contractor performance issues and Government-caused delays, such as unavailable Product Owners, changing priorities, or delayed approvals? | Redundant | Final | |
| 66 | If the Government requires Firm Fixed Price pricing, what specific workload baseline, task volume assumptions, surge assumptions, acceptance timelines, Government participation commitments, and success criteria will the Government provide so offerors can price the requirement without adding unnecessary risk premium for unknowns? | Redundant | Final | |
| 67 | Given that the Government is still seeking industry input on the PWS, Agile operating model, Jira data, evaluation approach, pricing structure, and contract vehicle, will the Government consider issuing a revised draft PWS or follow-on RFI before requesting final proposals to ensure all offerors have a common understanding of the requirement and basis for award? | Redundant | Final | |
| 68 | How will the Government ensure successful contractor performance during transition if CPE ST3 is simultaneously transforming its internal operating model, maturing Product Owner participation, improving backlog discipline, and shifting from a legacy staffing model to an enterprise Agile model? Will the Government share lessons learned from the current transformation or bridge effort before final proposal submission? | Redundant | Final | |
| 69 | If the requirement is set aside for small business, how will the Government apply and evaluate the limitations on subcontracting, including work performed by the small business prime and any similarly situated entities? | Redundant | Final | |
| 70 | How will the Government ensure dynamic resource allocation remains compliant with appropriation, FMS case, and funding-line restrictions when contractor personnel may shift between Project Management Offices, Headquarters functions, FMS activities, cyber tasks, test events, and acquisition-support work? | Redundant | Final | |
| 71 | What Government-furnished information, system access, facility access, stakeholder access, current process documentation, active workload data, and training records will be available during transition, and when will that information be provided to the awardee? | Redundant | Final | |
| 72 | Will the Government provide the draft QASP before final proposal submission, including task-level performance standards, acceptable quality levels, inspection methods, acceptance timelines, and how Agile dashboard metrics will be used for surveillance and CPARS input? | Redundant | Final | |
| 73 | The PWS appears to require contractor support for backlog management, prioritization support, enterprise resource allocation, Agile governance, and decision-support activities. How will the Government ensure the requirement does not create a personal services arrangement or improperly shift inherently governmental functions to the contractor, particularly where contractor personnel may influence priorities, resource allocation, acceptance workflows, acquisition planning, or enterprise governance decisions? | Redundant | Final | |
| 74 | The Government has identified certain functions, such as Program Manager, system engineer, and administrative support, as restricted or disfavored labor categories. Will the Government provide a clear crosswalk showing which PWS tasks are permissible contractor functions, which are inherently governmental, and which are prohibited or restricted under current Department and Army guidance? | Redundant | Final | |
| 75 | If the Government uses an OTA or prototype-based pathway, what specific prototype is being acquired, what statutory authority supports the approach, and how will the Government distinguish prototype evaluation from procurement of recurring professional services? | Redundant | Final | |
| 76 | If the Government uses an OTA, how will the Government ensure fair opportunity, competition, small-business participation, price reasonableness, data protection, and protest-risk mitigation given that the contemplated requirement appears to include recurring enterprise professional services rather than a discrete prototype effort? | Redundant | Final | |
| 77 | The Government has stated that offerors may be asked to demonstrate performance in a Jira-based challenge environment. Will the Government release the same scenario, data set, evaluation rules, scoring methodology, Government stakeholder scripts, and time constraints to all offerors before Phase 2, and how will the Government ensure that the challenge does not favor firms with incumbent knowledge of current workflows, backlog patterns, or stakeholder preferences? | Redundant | Final | |
| 78 | Will the Government release the draft QASP, performance standards, acceptable quality levels, inspection methods, acceptance timelines, and CPARS inputs before final proposal submission so offerors can understand how performance will be measured and priced? | Redundant | Final | |
| 79 | How will the Government ensure that dynamic resource allocation remains compliant with appropriation law, FMS case restrictions, CLIN boundaries, color-of-money limitations, and task-order funding controls when contractor resources may shift across PMOs, HQ functions, FMS activities, cyber tasks, test events, and acquisition-support work? | Redundant | Final | |
| 80 | What data rights, ownership rights, license rights, and transition requirements will apply to contractor-created Jira workflows, dashboards, scripts, automations, reports, data models, APIs, integrations, knowledge-management structures, and performance metrics developed during contract performance? | Redundant | Final | |
| 81 | What cybersecurity, RMF, CMMC, data-hosting, access-control, audit, and authorization requirements will apply to contractor-developed dashboards, Jira integrations, APIs, automation scripts, data connectors, and reporting environments used to support Agile execution? | Redundant | Final | |
| 82 | Will the Government identify the minimum clearance, facility, network, system-access, and onboarding requirements for each major task area before proposal submission, and will those access timelines be included in the transition schedule and performance-risk assumptions? | Redundant | Final | |
| 83 | How will the Government distinguish between contractor delay and Government delay when performance depends on timely Government access approvals, Product Owner participation, backlog decisions, acceptance actions, security reviews, funding availability, and cross-organization dependency resolution? | Redundant | Final | |
| 84 | Has the Government completed an acquisition strategy risk assessment addressing whether the current timeline provides enough time to finalize the vehicle, small-business strategy, OCI rules, pricing structure, QASP, evaluation scenario, Jira data set, funding model, labor-category restrictions, and transition baseline before final proposal submission? | Redundant | Final | |
| 85 | The size standard for the AOS is 541330, but in the Q&A you said the NAICS 541990 may be considered. This is very small, at $20M. Please, just consider the NAICS 541330. | The Government will consider the recommendation | Final | |
| 86 | Have you considered the USDS Digital IT Acquisition Professional Training Program to equip your contracting professionals with Agile methodology including modern best practices of Fed IT? https://techfarhub.usds.gov/get-started/ditap/ | Many team members have already taken various Agile and SCRUM certifications, additional training is continuously sought though none is currently under way due to mission requirements. The Army has access to Udemy training that also helps add to the Agile methodology knowledge base for the workforce. | Final | |
| 87 | How does the Government intend to measure Agile "capacity" and "value delivered" across the enterprise? | Redundant | Final | |
| 88 | What role does the Government envision for AI-enabled process improvement and knowledge management? | Redundant | Final | |
| 89 | How heavily will cyber, RMF, DevSecOps, and enterprise architecture expertise be weighted in evaluation? | Succesful solution will provide all the necessary expertise to support the full lifecyle of the programs within the portfolio. | Final | |
| 90 | Will offerors be permitted to demonstrate proprietary dashboards, workflow automation, and analytics capabilities during the Live Pitch? | No, proprietary solutions are not desired. | Final | |
| 91 | How much importance will be placed on organizational change management and Agile cultural transformation? | A successful solution, as discussed during the Industry session, should include the necessary business processes, policies, and training required to position the enterprise for an outcome‑based approach. This also includes addressing any cultural barriers that may need to be overcome | Final | |
| 92 | to what extent will future requirements involve support to AI/ML, cyber, EW, digital engineering, test, and training system portfolios? | As CPE ST3 continues transitioning to an outcome‑based acquisition model, Agile Professional Services (SETA) support will be essential in enabling the analysis, integration, and oversight needed across these evolving mission areas. The demand for expertise in data-driven decision-making, and rapid technology evaluation is expected to increase as these capabilities become more central to Army modernization priorities | Final | |
| 93 | What characteristics would define a highly successful Agile Professional Services solution at the end of the demonstration phase? | A highly successful Agile Professional Services solution at the end of the demonstration phase would be one that measurably improves CPE ST3’s ability to plan, execute, and oversee complex acquisition activities with enhanced agility, transparency, and technical rigor. Key characteristics would include: |
• Demonstrated ability to rapidly alocate SETA support to evolving mission priorities
• Mature, repeatable workflows that enable faster decision‑making, increased responsiveness to change, increased visibility and improved collaboration across government and industry teams.
• Clear evidence of outcome‑based delivery, where the contractor consistently meets defined performance metrics, provides actionable insights, and strengthens government oversight capabilities.
• Effective knowledge transfer and workforce enablement, including documentation, training, and coaching that leave the teams equipped with the necesary tools and knowledge to execute the mission.
| Final | |||
| 94 | May an individual be proposed as key personnel (e.g., the Agile Program Manager) by more than one offeror for this Call, or is exclusive commitment to a single offeror required at the Solution Brief phase? | Yes, a single member may be identified by multiple offerors. | Final |
| 95 | At the Phase 1 Solution Brief stage, is a signed letter of commitment required for proposed key personnel, or is the resume sufficient? | No, a resume is sufficient | Final |
| 96 | For a small business offeror, will the Government apply any limitation on subcontracting, and how will the relative roles of the prime versus team members be evaluated in the Solution Brief? | The requirements of FAR 52.219-14 will apply. | Final |
| 97 | What NAICS code and corresponding small business size standard apply to this Call for Solution? | Redundant | Final |
| 98 | Does the OCI firewall between Part I (APS) and Part II (APS-HQ) preclude a single offeror from submitting Solution Briefs for both Parts? | Upon reevaluation a single award will be issued covering both "parts". | Final |
| 99 | Which functions are anticipated to require on-site presence (e.g., 24/7 operations at Redstone Arsenal) versus which may be performed remotely or hybrid? | A mix of on‑site, hybrid, and remote support is anticipated based on mission needs and security requirements. Functions requiring on‑site presence will generally align to activities that involve direct coordination with government personnel, access to classified systems or facilities, or support to time‑sensitive operational needs. These functions may include acquisition planning and execution support tied to secure networks, certain engineering and test activities, and participation in in‑person technical reviews or integrated product team events. |
| Other functions that do not require continuous access to secure environments may be performed remotely or in a hybrid capacity. The intent is to balance mission effectiveness, collaboration, and flexibility while ensuring personnel are available on‑site when required to support CPE ST3’s operational tempo and decision timelines | Final | |||
| 100 | For the Phase 2 Live Pitch, will the Government provide the Jira sandbox in advance for configuration, or is configuration performed live during the pitch? | Redundant | Final | |
| 101 | Eligibility pathways: The same provision allows either a domestic FOCI-mitigated small business or a domestic non-traditional FOCI-mitigated vendor of any size. Will the Government provide its working definition of "non-traditional" for this Call (e.g., consistent with 10 U.S.C. § 3014), to support accurate self-assessment? | No longer applicable, as this requirement is now to be solicited under FAR Part 12, as a Total Small Business Set-Aside. |
| Final | |||
| 102 | For an offeror that does not independently meet the small business size standard, can the Government confirm whether such an entity may participate as a subcontractor or teaming partner to an eligible prime, and whether any limitations on subcontracting (e.g., FAR 52.219-14) will apply to resultant awards? | The requirements of FAR 52.219-14 will apply. | Final |
| 103 | Can you clarify that we cannot bid both? Hypothetically, if we propose both and are down selected on both, would you all choose, or would we have to choose which one we would support? Can you provide clarity on how this works? | Upon reevaluation a single award will be issued covering both "parts". |
| Final | |||
| 104 | Are the historic workload hours for both parts provided per year? | Yes, though that data is withheld as it is deemed unreliable and inapplicable to true Agile performance of the identified Enterprise capability. | Final |
| 105 | The historic workload hours do not line up well with the contact values for SETA II or the extension. Has there been a decrease in responsibilities for this CPE ST3? | Yes, from the contract support perspective and alignement to the recent Executive Orders | Final |
| 106 | Will the Agile Program Manager be required to have a Top Secret with SCI eligibility? | The Agile Program Manager will be responsible for performance across all classification levels. | Final |
| 107 | Are any of the incumbent security personnel covered by CBAs? | No | Final |
File details come from the government source that posted it. Updated .