Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operations32-month overall project schedule. The PMO will have the people, tools, and processes in place tomeasure, monitor, and lead.Team Noridian’s comprehensive management approach contributes to our success in two ways. First, itcontains a set of integrated processes for performing project work focused on Department satisfaction.Second, it provides a control structure that governs how we will plan, execute, control, track, and closeout the tasks and activities described in our project work plan. Our project management methodology isbased on the Project Management Institute's (PMI) Project Management Body of Knowledge (PMBOK),combined with our MMIS implementation experience and lessons learned. Our project managementmethodology establishes the processes, templates, checklists, schedule, metrics, and milestones necessaryto provide the "guard rails" for monitoring the contract. Our PMO establishes a project performanceenvironment that is poised for success. We will use our project management discipline to integrate andcontrol the execution of MMIS activities, ensuring that the operational system fully meets theDepartment's business needs.We have also blended the structure anddiscipline of PMBOK processes with theCapability Maturity Model Integration(CMMI) for organizational maturity. CMMILevel 2 and 3 processes form the fabric ofTeam Noridian’s iVision360 ISDM. OuriVision360 ISDM is specifically customized forthe Medicaid market, and represents a uniqueblend of the waterfall methodology, iterativeagile development, and rapid prototyping,resulting in the following benefits:• User Centric. Our primary motivation in developing iVision360 was to put the user at the center ofthe entire life cycle. Software projects succeed or fail largely from the level of understanding thedeveloping organization has regarding the customer’s business rules, requirements, and needs. Themore insight the developing organization can gain, the greater the quality and likelihood of success ofthe software project. Successful projects have significant interaction with end users and place the userat the center of the development life cycle. Every phase and task of iVision360 focuses on interactionand collaboration with the user community. We do this by implementing agile techniques andbuilding functioning software in an iterative fashion with user validation at periodic intervals.• Common Goals. Users actively participate in design sessions with an integrated team of developers,analysts, and testers. This method avoids the pitfalls of waterfall development and test methods,which leave, for example, test case refinement and execution until the full completion ofdevelopment. In an implementation, it provides the team with a sense of purpose, goal, and drive toaccomplish the end objective—software that meets the business requirements.• Testing Early and Often. The formal system and subsequent test phases are more likely to meetschedule expectations with a lower error rate.• Prototyping to Reduce Complexity. Prototypes are developed, where necessary, to model andpresent complex interactions, thereby further reducing the risk of problems being discovered in laterphases of development.The collaborative and somewhat “free-form nature” of iterative, agile development is balanced with thestructure and baseline management features of the waterfall methodology. By introducing the baselinemanagement features of waterfall, we minimize the risk of scope creep that can be associated withiterative development, and we achieve the clarity of a common understanding of the scope of work.Moreover, implementing and integrating with our PMO processes will provide integrated change, issue,8 | 2