Deadline: Monday 5/4, 11:59pm ET
In Milestone 2 you made substantial progress on your project. Now it’s time finish most of the deliverables or get them 90% of the way there!
Credit: 15% of your grade. The instructor will assign your grade by coordinating with your client.
Submit all artifacts to your team’s Git repository. Markdown or PDF artifacts are preferred. Add an entry for each artifact to your repository’s table of contents. Only artifacts listed in the table of contents will be graded. Please use Markdown for all submission artifacts when possible.
Note: Failure to submit (Git push) will result in 0 points. Failure to include an artifact’s entry in the table of contents will result in a 0 for the artifact. Double check your submission!
Cornell’s Standard Project Agreement (CSP) protects your client’s intellectual property. You are legally obligated to meet the conditions specified in this agreement.
Many of your clients will sign the CSP using Option C: The Organization is the owner of all Intellectual Property. If your client signs with this option, you are required to sanitized any privileged information when submitting assignments.
IMPORTANT! Any work that you place in your team’s Git repository should not include any privileged or confidential information.
_Before your instruction check-in meeting, email your weekly 4-box update to info5901-prof@cornell.edu. The instructor will review these to keep up to date on the status on your project. You should also share your 4-Box with your client. Consider cc’ing the client when you submit your 4-box.
Always be honest when reporting your status. Misrepresenting your project’s status is a considered academic misconduct.
Each individual team member will submit a 1 page “Individual Contribution Update” each week to report what they individually completed on the project during the previous week. Each team member should submit a PDF version of their update to CMS.
Each week you will submit a short summary of the following information (when applicable):
Required: What were your contributions for the week? How much time did you spend working on them?
Provide enough detail that the instructor understands what you did.
For each contribution, provide a rough estimate of the number of hours worked.
Bullets points are acceptable.
What did you learned during the week?
The MPS Project is about furthering your knowledge in Information Science. These projects are designed to further this objective. Tell us what you learned.
Any personal and/or team issues.
Are your team members failing to commit 10-12 hours per week on the project? The instructor needs to know this.
If there are issues on your team, feel free to share them with the instructor.
Do you need any help/assistance from the course staff?
Please note that your update is what you personally worked on for the week. Do not include what your team worked on. If you collaboratively work on something, please describe the portion that you contributed. If you find yourself spending more than 30 minutes writing your update, you’re probably spending too much time on it.
Always be honest when reporting your status. Misrepresenting your project’s status is a considered academic misconduct.
In Milestone 3 you should nearly complete your deliverables (~90%). In milestone 2 you made it about 50% of the way there. Now it’s time to finish the next big chunk of work and get your deliverable almost ready to deliver to your client.
No schedule is ever perfect. You should be updating your schedule each work, if not daily, to track your team’s progress. Commit each update to Git. We will check your Git history to check that you are revising this regularly.
Sometimes, you’ll run over a deadline, that’s normal. Just make sure you update the schedule to compensate for the late delivery to keep all future activities/deliverables on track to deliver at the end of the semester.
Continue to leverage your risk mitigation plan throughout milestone 3. Since there’s still about 10% left to do for the final submission, make sure you’ve updated your risk assessment and mitigation plan to reflect any risk that may realize before you submit and deliver the final version of project.
Regular client communication is important for keeping your project on track. Surprises are bad. Regularly meet with your client, share your progress, provide status updates (4-box), and raise issues/concerns/risks.
When meeting with your client, take notes. Your meeting’s minutes should be shared with the entire team via your team’s git repository.
Share a copy of your milestone 2 with your client. They need to see the progress you are making.
All artifacts should be submitted to your team’s Git repository and should be accessible from the table of contents.
Your table of contents should include:
Provide a 1-2 page summary of what you completed during this milestone.
In your summary you should include an assessment of your client’s general attitude towards your project and your progress. Are they pleased? Are they concerned? etc.
You should also communicate any concerns you have about your project and progress.
Provide a brief/concise paragraph about how well your team is working together. Please tell us about any issues that you had and how you resolved them. Please also let us know if you’re having difficultly with team work and whether you might need our help.