E58: Experience a team presentation

By the end of this module, you should have:

• Formed a team.
• Carried out the “bonding” exercise to learn about each other (E55)
• Created a GitHub organization and a github.io repository along with a README.md file, and published it as the home page for your organization. (E56)
• Created the first Project representing the work for the first Milestone. It contains at least two issues for each team member.

Now you will present your team and project to the class. Your presentation should be approximately 10 minutes long:

• The first three minutes should: (a) introduce your team members, (b) explain your coordination strategy (how often and where will you meet?) and (c) present the “Big Picture Vision” for your application.
• The next three minutes should present your GitHub project page for the Final Project Milestone M1. Note: you do not have to have an HTML mockup for this presentation. As an alternative, you can embed pictures of paper-and-pencil mockups into this page. Here’s an example GitHub project page from Bowfolios: https://bowfolios.github.io/.
• The final three minutes should present your M1 Project. Make sure the Project is organized according to the IDPM guidelines. Here’s an example Project Board from BowFolios: https://github.com/orgs/bowfolios/projects/1/views/1.

All presentations will be accomplished via the instructor’s laptop. You should DM the instructor or put the URLs to any pages you want presented at the beginning of your presentation time in the #final_projects channel. We will need the URL to your organization home page as well as to your M1 Project page.

If you want to use slides to present your team, please do not send PPT files to load into PowerPoint; often the format gets messed up. Instead, put your presentations online so we can access them via a URL. Consider using SpeakerDeck, Haiku Deck, Reveal.JS (or slides.com), Prezi or something similar.

Submission Instructions

You will be evaluated based upon your in-class team presentation on the date associated with this on the Schedule, as well as the structure and completeness of your GitHub. More specifically, you must have:

• Created a GitHub organization for your project, with two repos: one that provides the home page for your organization, and one that provides the source code for your application.

• The organization home page must describe your project and team members.

• All team members must have commit access to all repositories in the organization.

• All team members must have uploaded a profile picture to GitHub. That way, it is easy to associate issues in the Project with the team member assigned to it.

• The application repo should have a set of issues, at least two per team member.

• There should be one defined project, called “M1”. Update the Project workflows to automatically update issues status.

• Each issue’s description field should start with the line, “Do all work for this task in a branch called issue-XX”, where “XX” is replaced by the number associated with this issue. The remainder of the issue description field should outline what needs to be accomplished for this task. You can define an issue template to ensure that this template text appears in all new issues.

• Each issue should appear in the project M1. The issue status should reflect its current state.

Please review the issue driven project management screencast if these instructions are confusing to you. Also consult the IDPM Guidelines. If, after watching the screencast, you still have questions, please post to the #final_project Discord channel.