Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operations• Change Management Plan• Risk Management Plan• Issue Management Plan• Quality Management Plan• Application Implementation PlanTeam Noridian will also provide the Project Portal to function as the central repository of projectdocumentation and artifacts. The Project Portal is described in detail in 8.2.7.6.Our approach to managing and controlling the MMIS project is based on our lessons learned andexperience with state and federal PMOs, which provide the structure and processes we propose for ourPMO. One example of a lesson we have learned from prior implementations, is to introduce iterativedevelopment with iVision360 to improve tracking and control of development activities. We establish anenvironment where project management and quality assurance methodologies are integrated withtechnical processes necessary to build and deploy the solution. This integration is accomplished throughPMI PMBOK practices, Capability Maturity Model Integration (CMMI) processes, and the use of anearned value management system. Earned value management enables our management team to monitorprogress in an unambiguous and quantitative manner.Success with the MMIS necessitates that both the Department and Team Noridian remain fully aligned.Under the PMO, we will more effectively orchestrate processes and assign our resources to support thecollaborative delivery model of our iVision360 ISDM.8.2.7.4 Industry StandardsRFP Section 6.2.3.4Professional project management and the associated discipline of well-defined processes is the majorcontributor to our success. Team Noridian's plans and execution approach for the scope defined in theRFP and our project work plan is consistent with the PMI PMBOK. We integrated the PMBOK-basedproject management practices with the Software Engineering Institute's CMMI processes. In addition, weinternally measure and monitor our work using an earned value management system to enable ourmanagement team to monitor technical progress in an unambiguous and quantitative manner.In addition PMBOK, Team Noridian uses several other sources of standards such as PMBOK, ISO, IEEEand ANSI. Figure 8-9 provides a cross reference of IEEE standards referenced in RFP and how they areimplemented in our approach.RFP Par. # RFP Reference New Standard How We Implement6.2.3.4IEEE/EIA 12207.0-1996,Standard for InformationTechnology-SoftwareLife Cycle Processes(Note: There are 2companion 12207standards, 12207.1-1997; and 12207.2-1997. 12207.1 is stillactive and 12207.2 hasbeen superseded by12207.2008)Superseded by ISO/IEC/IEEE 12207.2008. This International Standardestablishes a common framework for software life cycle processes, with welldefinedterminology, that can be referenced by the software industry. Itapplies to the acquisition of systems and software products and services, tothe supply, development, operation, maintenance, and disposal of softwareproducts and the software portion of a system, whether performed internallyor externally to an organization. Those aspects of system definition neededto provide the context for software products and services are included.Software includes the software portion of firmware. This revision integratesISO/IEC 12207:1995 with its two amendments and was coordinated with theparallel revision of ISO/IEC 15288:2002 (System life cycle processes) toalign structure, terms, and corresponding organizational and projectprocesses. This standard may be used stand alone or jointly with ISO/IEC15288, and supplies a process reference model that supports processcapability assessment in accordance with ISO/IEC 15504-2 (Processassessment). An annex provides support for IEEE users and describesrelationships of this International Standard to IEEE standards.We use these standards as a frameworkfor creating our organizational life cycleprocess model and tailoring this modelto specific needs of each project. Thestandards provide us a comprehensivechecklist of phases, processes, tasks,and activities; and a set of outcomes foreach process that we use to verifyprocess adherence and as exit criteriafor “stage gate” reviews.8 | 16