hi600 u02_inst_slides
TRANSCRIPT
![Page 1: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/1.jpg)
HI-600: Analysis and Design of Health Information Systems
Planning: Part IISelection of Priorities and Methodologies
![Page 2: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/2.jpg)
Project Selection and Management• Increased demand for IT projects• Project selection process is harder• A solution: Project Portfolio Management
• Project portfolio management has become a critical success factor for IT departments.
• A selected system development project must undergo a thorough process of project management.
• A critical success factor for project management is to start with a realistic assessment of the work and then manage the project according to the plan.
![Page 3: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/3.jpg)
PROJECT SELECTION• Projects are not independent, considered
within the context of the project portfolio• Need to categorize to be able to manage
all at once based on size, cost, purpose, length, risk, scope, and economic value
• Selection based on organization’s priorities, not on individual divisions’ priorities
![Page 4: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/4.jpg)
Concluding Remarks on Project Selection• What are we doing, and why?• What are we not doing, and why?• Organizations have finite resources, and
limited windows of opportunity. There must be sufficient governance in place to decide which initiatives will get the green light, which will get deferred, or rejected.
• Governance groups should operate on guiding principles.
![Page 5: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/5.jpg)
CREATING THE PROJECT PLAN• Selecting appropriate development
methodology• Estimating project time frame• Identifying tasks• Developing the Work Plan
![Page 6: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/6.jpg)
Project Methodology Options• A methodology is a formalized approach to implementing
the SDLC• Waterfall Development
• Parallel Development• V-model
• Rapid Application Development (RAD)• Iterative Development• System Prototyping• Throwaway Prototyping
• Agile Development• Extreme Programming (XP)• Scrum• Dynamic Systems Development Method (DSDM)
![Page 7: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/7.jpg)
Waterfall Development
Parallel V-Model
![Page 8: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/8.jpg)
Rapid Application Development (RAD)Iterative System Prototyping
Throwaway Prototyping
![Page 9: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/9.jpg)
Agile Development• Extreme programming – emphasizes
customer satisfaction and teamwork. Core values are communication, simplicity, feedback, and courage
![Page 10: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/10.jpg)
Selecting the Appropriate Development Methodology
![Page 11: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/11.jpg)
Estimating the Project Time Frame• Using Industry Standards
• Function point approach (Appendix 2A)
![Page 12: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/12.jpg)
Developing the Project Work Plan
![Page 13: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/13.jpg)
STAFFING THE PROJECT• Staffing Plan• Quantity and type of personnel • Potential changes overtime• Management hierarchy: functional lead and technical
lead• Motivation: monetary and intrinsic rewards• Conflict management• Coordination of project activities• Computer Aided Software Engineering (CASE) tools• Standards• Documentation
![Page 14: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/14.jpg)
MANAGING AND CONTROLLING THE PROJECT
![Page 15: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/15.jpg)
SUMMARY• The project selection process takes into
account all of the projects in the organization, using project portfolio management.
• The project plan defines the tasks, task time estimates, and other information.
• A project requires staffing and coordinating project activities.
• Managing and controlling the project include scope management, time-boxing, and risk assessment.
![Page 16: HI600 U02_inst_slides](https://reader035.vdocuments.mx/reader035/viewer/2022081521/58709a3e1a28ab412b8b779f/html5/thumbnails/16.jpg)
Outcome of the Planning Phase• A vendor or project is selected • The organizational structure is put in place to
support said project (new hires or contractors)• Timelines and deliverables are calculated • Costs are estimated and budgets are set
accordingly.• Unknown costs and resources are budgeted for
and planned for at some level.• A maintenance plan is put in place.• This is the boring part, but it is 60-70% of IT