Skip to content

Commit

Permalink
D1
Browse files Browse the repository at this point in the history
  • Loading branch information
ThierrySans committed Sep 16, 2017
1 parent d8723f7 commit 1c1c8b0
Show file tree
Hide file tree
Showing 5 changed files with 203 additions and 0 deletions.
4 changes: 4 additions & 0 deletions _data/work.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@

- week: Team Setup
type: team
handout: 04/
rubric:
- deliverable: https://grademy.work/rubric?id=C01F17-D1
- interview: https://grademy.work/rubric?id=C01F17-I1

- week: Product Management with Git
type: individual
Expand Down
43 changes: 43 additions & 0 deletions work/04/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
---
layout: default
permalink: /work/04/
---

# Project Deliverable 1

Welcome to your new software development team! Your first task is, of course, to get to know each other — you will be working together for the next 10 weeks.

## Getting Started

- Introduce the team: include your team’s name, a team logo, and a picture of the entire team. What are the team’s goals in this project? What are your team’s strengths?

- Introduce the team members: for each member, include a picture and a 150-word biography. A biography should describe you as a professional: think of how you would introduce yourself to a prospective employee.

- Share a meal: include a picture of all team members sharing a meal. You can have lunch, dinner, coffee-and-pastries, whatever, together — it’s your choice.

- Discuss every aspect of [the team agreement](src/team-agreement.pdf) and submit all your decisions.

## Presentation and Quality of Writing

You have several options of presenting all write-ups in the course.

- One option is to produce one or several PDF documents. Make sure your reports look professional. Do not forget to include a cover page and a table of contents. Think of a user who chooses to read your report in electronic format — include links where appropriate.

- Another option is to set up a website. Plain vanilla HTML is enough, provided the layout, fonts, etc. are such that it is easy to navigate and easy to read. If you choose this option, we ask you to push the content of this website (either the source code or PDF exports) in your team repository as a proof that project deliverables were published on time each time.

- Should you have a different idea of presenting your work, please, check with the instructor first.

Whatever format you choose, make sure the report looks professional and is very easy to read: the TAs will not have much time and you need to convince them you did an excellent job! The following will always be considered when grading your work in this course:

- Presentation: the report is well formatted, looks professional, is easy to read and to navigate.
- Quality of writing: language, grammar, clarity, professionalism.

## Submission

Submit your report by pushing it to your team’s GitHub repository by the due date and time.

## Coming next

There is no deliverable for this part.

As a team, you should start discussing the project requirements by sharing your understanding of what the client needs.
106 changes: 106 additions & 0 deletions work/04/rubric/deliverable.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,106 @@
- rubric: Team Introduction
questions:

- caption: Score for this rubric
type: Points
max: 20
- caption: The report contains
type: SelectAll
options:
- "the team's name"
- "the team's logo"
- "the team's picture"
- caption: "The team's goals are"
type: SelectOne
options:
- missing
- marginal
- adequate
- excellent
- caption: "The team's strengths are"
type: SelectOne
options:
- missing
- marginal
- adequate
- excellent
- caption: "The team members' biographies are"
type: SelectOne
options:
- missing completely
- missing for the most part
- marginal for the most part
- adequate but somehow inconsistent (content, writing style)
- adequate overall
- excellent overall
- caption: Comments from the course staff
type: Comment

- rubric: Team agreement
questions:

- caption: Score for this rubric
type: Points
max: 20

- caption: The methods of communications are
type: SelectOne
options:
- missing
- incomplete
- adequate
- excellent

- caption: The meetings setup is
type: SelectOne
options:
- missing
- incomplete
- adequate
- excellent

- caption: The team work setup (including version control, division of work, submission of deliverables, contengency planning) is of
type: SelectOne
options:
- missing
- incomplete
- adequate
- excellent

- caption: Comments from the course staff
type: Comment

- rubric: Quality of the deliverable
questions:

- caption: Score for this rubric
type: Points
max: 5

- caption: Quality of the report
type: SelectAll
options:
- the report is clear and well presented
- the writing style is clear and consistent throughout the report
- the report does not contain excessive spelling and grammar typos

- caption: Comments from the course staff
type: Comment

- rubric: Quality of the repository organization
questions:

- caption: Score for this rubric
type: Points
max: 5

- caption: "On Github,"
type: SelectAll
options:
- the team repository does not contain superfluous files
- directory and files are well organized
- the README file has been updated with the latest updates
- the latests commits have appropriate messages

- caption: Comments from the course staff
type: Comment
50 changes: 50 additions & 0 deletions work/04/rubric/interview.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
- rubric: Project Interview
questions:

- caption: Score for this rubric
type: Points
max: 20
- caption: "The answer to question #1 is"
type: SelectOne
options:
- missing
- unsatisfying
- adequate
- excellent
- caption: "The answer to question #2 is"
type: SelectOne
options:
- missing
- unsatisfying
- adequate
- excellent
- caption: "The answer to question #3 is"
type: SelectOne
options:
- missing
- unsatisfying
- adequate
- excellent
- caption: "The answer to question #4 is"
type: SelectOne
options:
- missing
- unsatisfying
- adequate
- excellent
- caption: "The answer to question #5 is"
type: SelectOne
options:
- missing
- unsatisfying
- adequate
- excellent
- caption: The overall performance of the team is
type: SelectOne
options:
- unsatisfying
- adequate
- excellent
- caption: Comments from the course staff
type: Comment

Binary file added work/04/src/team-agreement.pdf
Binary file not shown.

0 comments on commit 1c1c8b0

Please sign in to comment.