Project Sessions

Semester Outline

• Weeks 1 - 3: Tools configuration, development environment setup, project management process overview

• Remaining weeks: Split into 3-week sprints. Each sprint contains a focus topic according to the project type that needs to be completed. Milestones will break down the project into smaller deliverables. Expect weekly homework (project work) during this period.

• Demo Day: At the end of the semester, each team will present their projects to the audience of ReDI course community members.

Weekly Sessions

Day	Session	Description	Roles
Monday 19:00 - 21:00	Project Session	We meet for two weekly online sessions to support the students work step-by-step on the project. Agenda: General stand ups, updates in main room, then breakout rooms	Guides Team
Wednesday 19:00 - 21:00	Project Session	Agenda: General stand ups, updates in main room, then breakout rooms	Guides Team

Sprint Outline

Sprint Phase	Duration	Key Activities
Sprint Kickoff	Day 1	Sprint Planning, Refinement, Work Time
Sprint	Weeks 1-3	Standups, Work Time, Optional Lessons
Sprint Conclusion	Week 3 Day 2	Demo, Retrospective, Next Sprint Brainstorming

More Information about the Semester & Sprint Flow

Activity Description

Work Time

• This is where the students are working on their projects in class and the teachers are available to help.

• We can encourage them to be investigating their tickets so that they can already start finding any unknowns that we can instruct them on, or to inform us what the next lesson should be about.

• Pair with students, answer their questions

• We do code reviews, look at their work, and see how we can be helping them improve as mentors.

• Prepare the upcoming tickets for the next classes.

Standup

The PM of each team walks them through standup:

• Check the status of the tasks on the board: Any updates, anything blocked or anyone need help?

• Keep it brief - standups are about exchanging important information and connecting with people who can solve your problems, not about solving them there or showing off.

Refinement

• The teachers will already have prepared the relevant tickets for the rest of the week.

• In refinement, you take your team through them and ask the questions: “Is the User Story + Acceptance Criteria clear? Is the task too large to accomplish? Is the task blocked / do you need more info before you could start on it?”. Refine the tasks to the point where the team feels comfortable taking them and working on them.

Planning

• Roughly figuring out who will work on what for the rest of the week. Mainly looking for:

• Does every student have meaningful work available to them?

• Will anyone be blocked by others, and can we avoid that?

Demo

Give the students a chance in front of everyone to showcase what they’ve been working on and made, what they’re proud of.

Retro

At the end of every sprint, we’ll have a retrospective where we address two main points:

• Likes: What did we like (about anything - the tasks, the project, the code, the course, other people?)

• Wishes: What do we wish for, how could we make things better (about the tasks, or the project, the code, or the course).

Sprint Brainstorming

• A large gathering of the entire class where everyone is participating in coming up with ideas for what the next sprint projects could be, and finding out who is interested in them (to form which teams).

Lesson

When we see students needing help on a specific topic (or they request a specific one), then the Instructor prepares a short (20m-1h) lesson on the topic. This should be a bit of a lecture with some slides or other visual materials, and ideally some examples and practice code/session for the students. We will record these lessons.