Using your ideas for developing a high-level schedule from Task 6, Part 1 of this case, develop a more detailed schedule for the minimum viable product (MVP) you defined in Part 2. You can use scheduling freeware that you download from the Internet or create a schedule with pen and paper. Include milestones within this revised schedule. Recall from Module 6 that a milestone is a significant event that normally has no duration; it is a marker to assist you in identifying necessary activities. It can take multiple activities and extensive work to complete a milestone. They are also helpful for establishing schedule goals and checking your progress. In a software project, milestones can be represented by the completion of specific modules, tabs, and feature sets.

Task 6 Ideas

1. During the daily scrum see if we are able to speak with the stakeholders if we can try to incorporate other built in apps into the data collection for our own to give better results to the user

2. During product backlog making start with already pre existing functions other applications may have as they will be the quickest to implement

3. All development team members as well as the owner and master review the Product Backlog while the Product Owner also provides insight into the goals and context for each item.

4. At the end of each meeting the backlog should be a list of assigned tasks with time estimate of completion