List of team members, first & last name.

Following agile, conduct a five-minute agile standup meeting where everyone stands in a circle and each team member talks for one minute about what he/she has been working on, what he/she will work on and are there any challenges he/she is facing.

Following agile, conduct a sprint retrospective meeting, where the entire team discusses about the happenings of the sprint - what went well, what didn’t go well, what should be improved upon in the next sprint.

What are the known risks that may prevent our team from completing this project on time? Risks could include: the working environment, lack of experience of the team in the area of focus, lack of access to a specific resource, etc.

Describe the version control method and repository we will be using for the deliverables created for the project. GitHub is strongly recommended. Once a repository is determined, we must share access to the repository with our instructor, our TA, grader, and all project team members.

This project milestone 5 submission should be a file named TESTING.md with the following contents included in the repository:

• Who: List of people on the team
• Title: of the project
• Vision: from Project Milestone 1 Proposal
• Automated Tests: Explanation and Screenshot (see above)
• User Acceptance Tests: Copy of at least three UAT plans

Select our database software tool (MySQL is strongly recommended). Create the database and populate it with ample data necessary to conduct initial program testing. Creating and populating the database should be done using SQL scripts. These scripts should be included in our GitHub repository.

Describe the background and reasons for developing this product.

Which software product will we use to plan and track the progress of our project? (Popular tools are Trello and Zoho.)

Using this tool, capture the requirements for our project. Requirements must include critical features including user requirements and functional requirements. We can create two separate lists for each of these requirements or combine them into one titled as Product Backlog.

Discuss and document a project plan. The project plan includes details such as the number of sprints we require to finish the project and tasks (feature development) planned for each sprint.

Take a screen shot of the project management tool which displays our project dashboard (containing the user and functional requirements, sprint tasks and owners, ToDo, InProgress and Done lists).

Create a three-week sprint or waterfall cycle in our project management tool. Create tasks for the feature development planned in this sprint. Discuss and take ownership of the tasks and have due dates assigned for each of these tasks in the sprint.

Initially all these tasks will be in the To Do list and eventually when the owners pick up a task and start working, then the task should be moved by the owner to In Progress list and once the task is completed, it should be moved to the Done list in your project management tool like Trello.

Select a collaboration tool for team members to utilize for coordination of their work and communication among team members. Popular tools are Slack and HipChat.

Propose an architecture for your app. What technologies will we be using on the backend? What technologies on the front end? How will they communicate with each other? Which technologies will be responsible for which functionalities?

We must deploy the project and store our source code, test cases, and documents in GitHub.

To submit Milestone 7, create a PDF named ProjectMilestone7_[Team Name].pdf in /Milestones. The PDF document must contain the following in the order provided as a bullet-point list or table (not an essay!):

• Title: Project title
• Who: Names of each person in the group
• Project Tracker: (Trello or similar tool)
  • Link to our Project Tracker (for instructor & TAs)
  • Screenshot showing our project in the project tracker
• (Optional) Video: 5 minute or less video demonstrating our project. Our audience is a potential customer or person interested in using the product.
• VCS: Link to your VCS Repository (for instructor & TAs)

The following will be checked in the VCS repository:

• Source Code (throughout the semester)
  • Test Cases
  • Auto-documenter documents (optional)
  • Video demo (optional)
  • README.md in GitHub explaining to others what our project is about
• Project Milestone 7 document titled as ProjectMilestone7_[TeamName].pdf
• Screenshot of each member’s contributions throughout the semester from GitHub
• Deployment: link to deployment environment or a written description of how the app was deployed and how one might access/run the app
• The app must be live, working, and accessible to the instruction team.
• (Optional) Auto-doc: The purpose is to run an auto-documenter on our code base. While Doxygen is very common (and Javadoc is used for Java), we may need (or want) to use another documenter. Make sure we choose a documenter that produces a PDF file or a HTML website.
  • List which program(s) we documented
  • Link to GitHub where the auto-generated docs are

Be sure to

• Ensure that all the TAs all have access to all links for grading
• Tag the repo with "Final Submission" (make sure to push the tag)
• Include a README in the repo:
  • Describe repo organization/structure
  • Describe where to find and/or how to build the docs
  • Describe how to build/run/test/etc code
  • If using a Continuous Integration system, provide a link to the CI status page

Provide a link to the tool we use to automate testing, or explain how to run the automated test cases or schedule time with the TAs to demonstrate our automated tests. Provide a copy of the output showing the results of the automated test cases running.

A simple, one-sentence statement describing the clear and inspirational desired state resulting from our team’s efforts to create our product.

We will conduct a live presentation of the project in front of the other students. Presentations will be given during the Week 16 lecture time or during the Week 16 lab recitation times. We will sign up in Moodle for our chosen presentation date/time. The presentation requires all members to be present and standing up front. If an individual on the team is not present for the presentation, then he/she will get a zero for the presentation portion of the project. Each team member must discuss something about the project during the presentation. We must target 10 minutes for our presentation (no more; no less). We should cover the following items in whatever creative way we wish:

• Title of the project
• Names of each person in the group
• All the tools your group used
  • Name of the tool, logo, and purpose (e.g., Project Tracking, VCS)
  • Our group’s rating on how useful/good this tool/methodology was (ranked 1..5 where 5 stars is best and 1 star is useless
  • Methodologies (Iterative, Waterfall, agile, TDD, pair programming, peer code reviews, other…)
• Expected tools
  • Project Tracker (Trello or similar)
  • VCS repository (GitHub or similar)
  • Database (MySQL or similar)
  • Testing tool (PyUnit or similar)
  • Auto-documenter (optional. Doxygen or similar)
  • Deployment environment
  • (Optional Additional tools we may have used)
    • IDE (e.g. Eclipse, Code::Blocks, xCode.)
    • Framework (e.g. Laravel, Ruby on Rails, Node.js, Android Studio)
    • Hardware (e.g. RaspberryPi, Arduino)
• Challenges we encountered, how we overcame them, and how it may have affected our original project plans
• Demo the project. This must be a live demo. Practice beforehand.

A short (2-3 paragraphs) description of the project. Provide enough information to explain what value our product will provide to our users.

Create a document that describes how at least three features within our finished product will be tested. The test plan should include specific test cases (user acceptance test cases) that describe the data and the user activity that will be executed in order to verify proper functionality of the feature.

A detailed plan showing how the team will mitigate each stated risk. Describe how we will succeed given the stated risks.

Create a document that visually depicts the contents and structure of the database. For example, an entity relationship diagram showing all database tables, attributes, primary keys, and relationships between tables. We must use at least 2 tables.

Which software development methodology will our team follow? Describe the methodology and the features/steps we will follow. Common methodologies include waterfall, agile/scrum, iterative, spiral, etc.

Moniker to be used in all presentations and documentation.