RFQ ID RFQ1508611
“3. Scope of Work
The contractor shall provide all qualified labor, expertise, supervision, materials, transportation and operations to conduct the work under this task order. The contractor may use its own staff to carry out the work or may draw on the expertise of one or more outside technical experts where appropriate.
Prior to the commencement of work under activities under Tasks 2-5, the contractor shall provide the Contracting Officer’s Representative (COR) with a specified plan and timeline for addressing the request and estimated budget hours that will be used as the not-to-exceed amount for the activity. The contractor must receive the COR’s approval of the estimated budget before beginning work.
Additionally, the contractor shall address in the plan how all services and deliverables rendered by the contractor will leverage leading-edge front-end design and user experience (UX) trends and practices, such that the OEDARM’s work reflects “best in class” quality and presentation compared to that of other federal agencies. Minimally, PM, and Product Owner review of UX prototypes, sketches, or mockups prior to execution of design shall be included in all project plans to ensure that user interface design is revalidated as functional progress is accomplished.
3.1 (Task 1): Contract Management (Base)
The contractor shall manage the task order in an efficient manner that fosters communications with the COR and other relevant staff. Required task order management activities and deliverables shall include planning for and facilitating a post-award kick-off meeting, developing a project plan, and submitting monthly progress reports.
The contractor will work in a team-based Agile project environment and shall be responsible for creating and maintaining application roadmaps, project plans, and product and release backlogs that will be the basis for the team’s work for each of the projects defined in Sections of this SOW. The Program Manager will serve as or identify the Product Owner, who will specify high-level requirements to the team. As in Scrum-like Agile processes, the Product Owner will work together with the team to develop and estimate user stories and establish acceptance criteria. These acceptance criteria will specify expected functionality for a user story, as well as any non-functional requirements that must be met in the development of the story. The Agency Product Owner, supported by SMEs and business analysts, will determine whether acceptance criteria have been satisfied…”
“3.2 (Task 2): Edison Operations and Maintenance
Edison is the OEDARM’s suite of digital tools. The government requires user, password, role, and incident management; daily monitoring of data feeds; and monthly controls testing to support FISMA compliance. Accordingly, the contractor shall execute these tasks and refer to the government for decision any matters which are inherently governmental, according to OEDARM’s documented controls procedures and the Department OCIO’s policies…”
“3.3 (Task 3): Continued Edison Development
The Department requires continued support with accruing backlogs based on user feedback on all current and future Edison applications to inform future Agile Sprints and with executing the development sprints. Accordingly, the contractor shall execute all application development tasks (including developing user stories, requirements gathering, and user testing) which are not inherently governmental functions, as outlined in the COR-approved Project Plan according to Agile methodology. The PM shall have the opportunity to attend all sprint-related meetings, including sprint planning, daily standing, review, and retrospective meetings…”
XFactor Members access the complete set of documents here.
To register for a free XFactor trial, read more here.