We met weekly in person and online to brainstorm, explore, discover, and finally decide on the range of epics we wanted to build on. During these meetings, the team reviewed the stories, graphics, sample data from their Apple Watch use, and discussed their data and the visuals on their Apple iPhones. We built the sprint plan, sprint backlog, estimates and the commitment to complete the beta version of the prototype.  Task lists were determined and updated at each meeting to identify the sets of work effort that needs to be completed by a specific member of the project and for interdependencies.

• User Stories that capture features, options, functionality, and requirements of other types from interviews with end-users and system owners. These stories also integrate into test cases and map to specific iterations;
• Task Lists identify the sets of work effort by person and interdependencies.
• Bug Lists that clearly define logical and system errors identified by error logs, compiler output, and testers;
• Workbooks that assign bugs, issues, and tasks to specific personnel during specific iterations;
• Task-boards, Storyboards, and Dashboards that track and display all the artifacts, progress, and status; and,
• Reports that offer a static view of any particular moment in the project.

We used Jira and Github for our Continuous Integration/Continuous Deployment (CI/CD) pipeline to match our expertise in automated CI/CD in AWS. The backlog comprises user stories with features, options, functionality, and requirements and test cases.

• Sprint Review:
  During our reviews we were able to demo their completed UI/UX and coding tasks for continuous improvement.
• Sprint Retrospective:
  We discuss what went well, what could be improved and selected action items for further improvement of the process.