Grade sheet (pdf)
This milestone will get your team organized and begin the process of working together as a group. Don't underestimate the difficulty of doing simple things as a group. Communicate, communicate, communicate!
In step 6 you will create a Git repository for your team. This is where all the documents created during each Milestone should be placed (neatly and in appropriate folders). A note on file formats: you should default to plain text files for everything. The resumes (e.g. Word) and logos, etc. (e.g. png) can and should be in the appropriate formats, but if you're only writing text, put it in a Plain Old Text file. Of course, html and Markdown are plain text and also give you formatting options if you so desire.
The 3+branch, with Pull Requests Git Workflow that we'll be using all term isn't introduced until Milestone 2. For now you can either learn the workflow ahead of time, or do the less-than-desired method of manually transferring files to the repo owner, who should add/commit/push them. Under no circumstances should all team members have admin or write access to the team repository. That's a great way to screw up your repo. Last term we all had our own repositories and could control the entire push/pull cycles. Imagine 4 people randomly adding, committing, pushing and pulling!
This section of the milestone will include a resume for each member of the team. All of the resumes should look the same and contain the same major headings, and have the same format including font size and type, and order of sections.
The Rockport Institute contains some good information for writing resumes. For the resume in this section, your resumes must conform to the combinatorial type described in the website. It must contain the sections outlined below. Resumes that are not consistent with each other and the required format will not be considered completed and will receive 0 completion points.
As you will see when you search the web, there are three basic resume types: Chronological, Functional, Combinational
For this class we will be using a version of the Combinational Resume. Your resume should be no longer than one page and contain the following sections. As pointed out in the Rockport site, the resume is advertising copy whose purpose is to obtain an interview.
Your resume for this class should contain
Skills Section
A listing of various computer science related skills such as Software Engineering, Operating Systems. Keep in mind that probably every CS graduate in the country knows how to use Microsoft Windows and program in Java. You need to focus on those skills that make you unique. In looking at the Rockport site focus on the way in which “selected skills and accomplishments” are written. You might consider naming sections after courses you have taken in your program. The use of strong active verbs is important. It is ok if these sections make the resume exceed one page. When applying for a particular job, you can remove some of the sections to make it fit within one page.
Employment History and Education
These are two separate sections. I mention them together because the ordering depends on which you have more of. If you are a returning student who has managerial experience, definitely put the employment history first. If you went straight to college from high school, probably the Education should go first.
Both of these sections should be listed in “reverse chronological order”, that is most recent first. You would list your college graduation before high school.
Most of the things that would be listed as part of your experiences in a chronological resume have been moved up into the skills section and need not be repeated here. This section basically becomes a chronological list.
One last note on Education, if your GPA is in the top 10% list it, otherwise leave it out. A neat trick with GPA is to calculate only classes within the major.
Acquire and assemble a three ring binder with dividers for each work product
Create a schedule for your team that lists five hours of meetings during the week. Although you will not use all of them, it is good to know they are available during “crunch time”. There are several specific meetings described in the SCRUM tutorials that are required! Define some of your schedule times for the five defined SCRUM meetings. Standup meetings occur at the beginning of each class, and the scheduled meeting with your team instructor can function as the sprint review meeting. Schedule time for the remaining meetings into your team’s weekly schedule. See the SCRUM reference card for a quick overview of the meetings.
As just mentioned, you will need to schedule a fixed time to meet with your project advisor during the week. As in the real world, you will need to find a time that is convenient for them. Not one that works for your schedule. Your best bets are to look at times that match already scheduled office hours or are next to existing courses. Do not expect a professor done with courses at 10AM to meet you at 4:30 PM because it works for you.