-
Introductions
- Facilitator
- Participants
-
Course description
- What to expect
- Commitment
- Time / effort requirements
- Accountability
- Learning objectives
- Key Outcomes
-
A team agreement defines the purpose of the team, how it will work, and what the expected outcomes are. Team agreements are usually completed when a new team is formed, but they can also be completed when there are changes to an existing team, or if expectations need to be clarified.
-
Baseline ratings for learning objectives
Rate your baselines for the Level Up learning objectives.
-
Starting resources
-
- Strong vs weak
- dynamic vs static
-
- TDD
- Introduction
- Value
- Four-phase test
- Testing pyramid
- TDD
-
Stand up
-
- Attributes of OOP
- encapsulation
- composition
- inheritance
- abstraction
- polymorphism
- OOP vs functional programming vs procedural programming
- Intro to SOLID
- Attributes of OOP
-
- Writing an effective README
- Commit messages
- Git history
-
- How to get your PRs accepted
- How to review PRs
-
Stand up
-
- What is Agile?
- Other development methodologies
- Agile frameworks: Scrum vs Kanban
- Writing user stories
- Writing user stories (TODO App)
- Pokemon API Client - Day 3
-
Stand up
-
Project work
-
Stand up
-
Retro
-
Stand up
-
Project work
-
Stand up
-
Retro
-
Project work
-
Stand up
-
Project work
-
Stand up
-
Code freeze
-
Learning outcomes - post-course
-
Stand up
-
Final project updates
-
Final Retro
-
Stand up
-
Project demos