Previous Lecture lect04 Next Lecture

lect04, Mon 10/11

Project Management: README.md, Leadership, Retros, Learning plan

Announcements:

Today

Brief discussion of team leadership roles

Brief discussion of retros

Team Activity #1 in team/LEADERSHIP.md

In your project repo, in file team/LEADERSHIP.md

You can use a Markdown table to make this easy to read. It’s fine to just record this directly on the master branch, even editing directly in the GitHub web interface.

Example:

# Leadership roles

| Date      | Name              | Activity                                               |
|-----------|-------------------|--------------------------------------------------------|
| Mon 10/04 | Chris Gaucho      | Led team discussion to define MVP                      | 
| Tue 10/05 | Lauren del Playa  | Led team discussion of Sprint01 and learning plan      | 
| Wed 10/13 | Taylor Chen       | Will lead first Retro                                  |

Sprint Planning

Part of your lab02 deliverables include documentation of at least one Sprint Planning meeting in a team/sprint0?/ folder in your main repo (question mark for number of your current sprint, which may vary from team to team). For the purpose and mechanisms of a Sprint Planning meeting see, e.g., pages 25-27 of our Scrum booklet. It is OK for such a meeting to already have happened and to be documented retroactively.

Team Activity #2 in team/LEARNING.md

More on the learning plan

The format of the learning plan is up to the team, as long as it includes the following:

The plan could include things like:

An ideal plan will incorporate both breadth and depth:

A Partial List of important technologies, by Stack

You might use this list to come up with ideas for your /team/LEARNING.md file.

Note that:

General Web Dev Skills

React, Next.js

Spring Boot

Project Specific APIs, data sources, etc.

Your project may have specific APIs, data sources, specialized skills etc. that you may need to work with.

It may helpful to identify the ones needed for your project, and be sure that at least one team member is looking into each of those.

Examples:

Spikes, Skunk-works, Proofs of Concepts

You are not only permitted, but strongly encouraged even, to make additional repos in addition to your main project repo that contains extra “proof of concept”, and “practice code” for your project.

These are someetimes called spikes.

You can name these with private or public repos in the ucsb-cs148-s21 github org names such as spike-t1-try-spotify-api and then give your team access to them.

You may want to make such repos part of your learning plan.

If you have extra time