C790 Nursing Informatics (WGU) Project Management, Top Exam Questions and answers, Graded A+

Document Content and Description Below

C790 Nursing Informatics (WGU) Project Management, Top Exam Questions and answers, Graded A+ project management - ✔✔-organizing and directing other people to achieve a planned result within... a predetermined schedule and budget. oversight committee - ✔✔-clients and key managers who review the progress and direct the project Level of formality or ceremony - ✔✔-the rigor of holding formal meetings and producing detailed documentation Agile Project Management - ✔✔-a way of balancing flexibility and chaos: how to be agile and flexible while maintaining control of the project schedule, budget, and deliverables. agile time frame-difficult to create/maintain project schedule cost estimates are difficult to make, especially with a project in which the requirements are expected to change throughout. project manager controls cost quality management: each iteration has a deliverable. testing spread throughout project, also process evaluations of each iteration system vision document (SVD) - ✔✔-a document to help define the scope of a new system business benefits - ✔✔-the benefits that accrue to the organization; usually measured in dollars (part of SVD) system capabilities - ✔✔-the required capabilities of a new system; part of a System Vision Document (part of SVD) cost/benefit analysis - ✔✔-process of comparing costs and benefits to see whether investing in a new system will be beneficial net present value (NPV) - ✔✔-the present value of dollar benefits and dollar costs of a particular investment break-even point - ✔✔-the point in time at which dollar benefits offset dollar costs payback period - ✔✔-the time period during which the dollar benefits offset the dollar costs tangible benefit - ✔✔-a benefit that can be measured or estimated in terms of dollars intangible benefit - ✔✔-a benefit that accrues to an organization but that can't be measured quantitatively or estimated accurately project dashboard - ✔✔-allows all types of project information to be posted and viewed by Web browsers project iteration schedule - ✔✔-the list of iterations and use cases or user stories assigned to each iteration detailed work schedule - ✔✔-the schedule that lists, organizes, and describes the dependencies of the detailed work tasks Work Breakdown Structure (WBS) - ✔✔-the list or hierarchy of activities and tasks of a project; used to estimate the work to be done and to create a detailed work schedule Gantt chart - ✔✔-a bar chart that portrays the schedule by the length of horizontal bars superimposed on a calendar critical path - ✔✔-a sequence of tasks that can't be delayed without causing the entire project to be delayed retrospective - ✔✔-a meeting held by the team at the end of an iteration to determine what was successful and what can be improved Core Process 1 - ✔✔-the objective of which is to identify the business need and to get the project initiated. These activities include: ▪ Identifying the problem ▪ Extending the project approval factors ▪ Performing risk and feasibility analysis ▪ Reviewing with the client and obtaining approval Tall Man Lettering - ✔✔-mixed case lettering ie NiFEDipine scope creep - ✔✔-occurs when requirements are added after the initial project is defined and those added requirements are substantial enough to affect the project timeline. Best of Breed implementation of EHR - ✔✔-involves reviewing several vendors for their "best" module or application, such as an admission, discharge, and transfer (ADT) system or emergency department module. Then multiple modules are purchased from different vendors to create a full suite of functions. Integrated Health System - ✔✔-an electronic health record system that includes a suite of modules to support care. It is typically easier to install and easier to support and usually has a similar-looking user interface across modules, which helps users to learn the EHR more quickly. Systems Life Cycle SLC - ✔✔-Analyze: The existing environment and systems are evaluated. Major problems and deficiencies are identified using informal or formal methods. A needs assessment is developed. Gaps are noted and current capabilities and limitations are outlined. Initial user and system requirements are formulated. •Plan: The proposed system is planned comprehensively. Planning includes strategic levels, such as whether the system will be developed internally, purchased and tailored, or designed and developed jointly with a vendor. •Develop or purchase: At this stage either the system is purchased or the new system development begins. New components and programs are obtained and installed. For vendorsupported solutions, extensive tailoring occurs. •Test: At this stage extensive testing occurs just before Stage 5 and "go" or "no go" decisions are made about deadlines. Toward the end of this phase, marketing and communication efforts are accelerated to make users aware of the impending change. •Implement or go-live: The system is implemented using a selected method best suited to the organization and its tolerance for risk. User training is completed. •Maintain and evolve: Once the system has been formally acknowledged as passing user acceptance testing, typically at 90 or 120 days after go-live, it enters a maintenance phase. •Evaluate: Activities in each phase are assessed for their quality and effectiveness. [Show More]

Last updated: 1 year ago

Preview 1 out of 5 pages