Possible discussion topics: Review Kathy’s comments Discuss typical software development process - what we do, what HealthFlow does, where to find information. Andrea ask LeeAnn for help with questionnaire Discuss learnings from LinkedIn Learning and web research (see notes below) Invite Sarah P to talk about what she would do differently and critique the plan?
Andrea’s notes and thoughts prompted by Linked In Learning There is a standard software development process. HealthFlow takes direction from us, but we are not equipped, experienced, or using a traditional software development process on our end. Example of STEVE (State and Territorial Exchange of Vital Events) -I managed a major overhaul and was guided through the process by the software developers. There is a whole process starting with requirements gathering. LeeAnn dis-covered that in her thinking process, i.e., asking potential users what they want rather than starting with what we think they need. Agile vs Waterfall https://en.wikipedia.org/wiki/Software_development_process
Establish requirements now (Source 2) Establish acceptance criteria (Source 2) 
Phase 1. Requirement collection - Goal: to gather and document business requirements Develop user stories for what you WANT the software to do Gather requirements (there is an entire field on this - and a format for requirements that makes it easy to communicate to the software developers)
Phase 2. Design - Goal: to translate software development requirements into design Phase 3. Software development -Goal: To build the actual software Phase 4. Testing - Goal: To ensure the software meets requirements Phase 5. Deployment - Goal: To deliver completed software to users Source: https://ncube.com/blog/software-development-life-cycle-guide |