GithubHelp home page GithubHelp logo

m5's Introduction

Milestone 5: Final Project Delivery and Demonstration

1 Purpose of this milestone

Milestone 5 is the final delivery of your term project. It provides the basis for final project grading. Milestone 5 consists:

  1. Live demonstration and presentation of your application
  2. Delivery of a complete final project portfolio
    We strongly recommend all team members attend the final project demonstration.
    Final project will be graded based on final project grading rubric. Make sure no required section is missing. Pay attention to your content and format.

2 Delivery 1: Demonstration of your final product

Please see “Final Product Demonstration Guideline” for details.

3 Delivery 1: Complete Project Documentation Portfolio

The final complete project portfolio must have the following content, in well-formatted aesthetically pleasing manner.

3.1 Cover page

  1. Course name and term (e.g., CEN 4010 Spring 2018) Final Project Portfolio
  2. Your project/application title and name (you can use the name you chose for your application)
  3. Team number
  4. Names of students and team members roles, for example, Scrum Master, Product Owner, Develop Team, and their emails
  5. Date of the document
  6. URL to your team’s project
  7. Revision history table. Note: you will update this document based on instructor’s feedback so this is important. Project Summary

3.2 Project Summary

Copy it from Milestone 4. They are listed here again for completeness of Milestone 5. 1) Name of the product

  1. Name of the product
  2. Explicit list of ALL major committed functions. These are your FINAL Priority 1 functions for which you will be graded and that your team shall actually deliver and test for. You should use plain English as if you would talk to a customer, and not the language used for formal requirements specification. This is your FINAL functional commitment. In other words, failure to deliver on some of Priority 1 functions will result in reduced grade. Please write it in the list format (each item max 1-3 lines) so it is easy to check.
  3. Describe unique features in your product (if any)
  4. URL to your product accessible to instructors, on deployment server Length: max 1 page. Write it for wider audience: executives, marketing, customers. The list of final functions will be checked on your final delivery for functionality and correct operation as you specified them. Failure to deliver complete list of these committed functions may result in reduced grade.

3.3 Milestone documents

  1. Put your modified Milestone 3 here after incorporating feedback.
  2. summarize instructor’s feedback of Milestone 3 and 4

3.4 Screenshots of actual final product as shown in the demo

Section title “Product Screenshots” contains ALL main functionalities of your final system as an illustration of your finished product.

3.5 Google analytics plot for your website (1 page)

Use Google Analytics to analyze your website traffic https://analytics.google.com/analytics/web/provision/?authuser=0#provision/SignUp/

3.6 Team members contribution

  1. List each team members’ contribution to the project. Use “Project Peer Evaluation” (posted on Canvas under “Resources”), to give each team member’s contribution points. Note: All team members should reach consensus of those points.
  2. Describe each team members contribution to teamwork (technically and any other contribution). No more than half page. Bulletin format is fine
  3. Number of submissions each team member made to GitHub team development branch

3.7 Post-project analysis (one page or so)

In many organizations, after the project is finished, people engage in analysis of the experience, issues, and lessons learned. In the classroom, one often learns more from mistakes. But for real learning to happen, one needs to be able to understand what mistakes were made and what would need to be done to avoid them in the future. BTW: this is also worthy of discussion in your job interviews – employers love those real stories about challenges and how there were dealt with. In about one page team lead should summarize: a) main challenges; and b) what would you do better next time to address those challenges. Team lead should consult with team members before completing this task. Please be honest and identify issues and mistakes, this will help your learning.
Also include:

  1. Features you have finished and those you’d like to finish but couldn’t be able to, and the reasons
  2. Knowledge gained and lessons learnt from your project and teamwork

4 Submission

Submit the following to Canvas by due date:
a. Final project report, in word format,
b. Your presentation PPT

5 Grading criteria

See “Project Grading Rubric” for details.

m5's People

Contributors

jessicacarmona2 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.