IT Project Workshop 11
===

###### tags: `IT PROJECT`

## Deadlines

### Meeting

- [ ] Handover meeting & demonstration `schedule this please`
- [ ] Presentation `FRI 30/10`

### Submit

- [x] Professional Communication Report `WED 21/10`
- [ ] Individual Report `23/11`
- [ ] Team Product Submission `20/11`

## Marking Breakdown (updated)

### Process

- [x] Sprint 1 (10%)
- [x] Sprint 2 (10%)
- [ ] Sprint 3 (10%)
- [ ] Overall team performance (10%)

### Individual Reports

- [x] Professional Communication Report (8%)
- Due now - no late penalty within reason but don't test the waters.
- [ ] Final Reflective Report (10%)
- See lms for details

### Presentation and Demonstrations

- [ ] Presentation (10%)
- From your presentation on the final Friday, average mark of the three markers which include Leon, external marker and myself.
- [ ] Demonstration (5%)
- Assessed during product handover with client by me

### Product and Team Reports

- [ ] Product (15%) [add the 5% from demo for 20%]
- Note that a team product submission document is required of 4-10 pages detailing what was accomplished. See LMS for further information.

### Individual mark

- [ ] Individual contribution (12%) [comes from peer feedback and myself]

## Workshop Substitute

### Housekeeping

Please can you schedule a meeting with your client for the final handover between now and the end of SWOTVAC.

I need to attend this meeting to assess your final demonstration. You can use when2meet to gauge availability.

Please have this meeting scheduled by Monday next week.

### Presentation Notes

Note the following suggestions from Leon:

>Suggestions for the presentation:
One slide on your team;
One slide on the client and their requirements;
One slide on the technologies used
One slide on the collaboration tools used
Discuss Key Challenges
Discuss Lessons Learned
A demonstration during the presentation is optional.
Assessment: 10% of your total mark comprising 5% - 3% - 2%
for Content – style - entertainment value respectively

I believe this is a great structure, however there are some important things to be aware.

- **team**
- Introduce members, maybe include a photo of each member on this slide. Nothing unexpected here.
- **client and their requirements**
- Introduce your client(s), discuss their background and then the important user stories (requirements) that they had. This step is **VERY IMPORTANT** to frame the rest of your presentation.
- **collaboration tools used**
- Be aware that Leon and the external marker are going to sit through 63 presentations prior to this throughout the week. Don't focus on slack/trello basic functionalities. Instead use this opportunity to discuss your notifications intergration with Slack, Github and Trello / other above and beyond things you used here that showcase your teams high professional standards.
- **technologies used**
- Disccuss database technology (sql/nosql), front end framework and backend. Importantly discuss why you selected these. Now would be a great time to show a Cloudcraft or other diagram that shows your architecture and tech in an easily digestible format.
- If you have testing / pipelines / deployment now is also a good time to advocate how they helped your team and flex.
- **key challenges**
- This fits well into the sprint retrospectives you conducted. Ideally you raise some points here that were picked up by your team as "could be improved".
- Likewise, with your client meetings following each sprint its also a great opportunity to show a timeline of events here.
- **lessons learned**
- Following the setup in the previous slide(s) of teamwork/process/tech challenges you noticed. Here is the slide to talk about how you addressed them. You want the marker to see how you discovered an issue and then solved it for the betterment of your team.
- This can be both product related (e.g. UI Issues / features) and team ( PR's, how you ticket work or testing)
- **demo**
- **KEEP IT BRIEF**. You want to showcase the most impressive and best parts of your application here. This section should be ideally focussed on running through the user stories you talked about in the earlier slide and showing how your product fulfills those specifically. The best presentations will frame this demo with respect to the user and their use cases.
- Don't go through monotonous or boring things. We don't need to see the full application and every feature (such as uploading every single document type). Focus on the best and most important to your client. You can showcase all the added functionality during the demo with your client (at the handover).
- **PRACTICE THIS**. In my presentation, my team mate decided to drop a production database collection in MongoDB 5 mins prior to presenting to "clear the content" for the presentation. Needless to say it broke a page of our application. Don't do that.

Marking Breakdown:

| Criteria | /Mark |
| -------- | ----- |
| Content | 5/10 |
| Style | 3/10 |
| Entertainment | 2/10 |

### Demo and client handover

This is very similar to what you have done twice already. Showcase all the features of your application. Talk through some user flows. It's fine for this demo to include more of your application than shown at the presentation.

Marking here is assigned by me **out of 5**

The marking will follow a largely consistent criteria of:

**Look**
**Functionality**
**Complexity**

### Team Product Submission

>Each team needs to submit a final product report (between 4 and 10 pages) through Canvas.
>The report should include the agreed requirements, a list of the features implemented, and the testing that has been done on the product, and most importantly a link to the team repository. If a deployment has been made, details of any deployment pipelines should be given. The report should include a ‘boasting page’, which says which aspects of your product the team is most proud of.