Project Phase
The goal of the capstone project is to train all the skills you need to succeed in a real job environment. While coding is an essential component, it's just one aspect of what makes a successful developer.
In addition to improving your programming skills, you will also explore important professional aspects such as teamwork and workflow adaptation. This provides the way for improving skills in communication, planning, prioritization, peer support, and feedback management.
💡
Remember that programming is only one part of a developer's daily tasks.
Capstones Routines
Daily
| 9:00 am | 9:30 am | 5:00 pm |
|---|---|---|
| Student Meeting without coaches | Daily Standup with teams and Coaches | Checkout |
| Photo of attendance | What did I/we work on yesterday? | |
| What will I/we work on today? | ||
| Any blockers? |
ℹ️
Attendance is required in Zoom from 9:00 am to 6:30 pm.
Weekly / Once per Sprint
| Weekday depends on the Capstone start | Two days before Sprint end |
|---|---|
| Sprint Planning and refinement of User Stories | Backlog grooming with Coaches/Product Owners |
| Public Sprint Review starts from the second sprint |
ℹ️
Dates for Sprint Planning, Public Sprint Review and Backlog grooming will be announced at short notice in the course.
Capstone Project Tips
- Code Quality has priority: good code is better than many features.
- KISS Keep It Simple Stupid: Avoid unnecessary technologies or complexities.
- Base your development on the CRUD operations:
- Create - Add data
- Read - Display data
- Update - Edit or update data
- Delete - Delete data
Workflow Tips
- Kill your Darlings: Say goodbye to beloved ideas when necessary.
- Dog Days are okay: Accept unproductive days.
- Expectation Managment: Fit and review your expectations regularly.
- Personal Responsibility: Proactively ask for feedback and help.
- Make Reviews: They promote learning.
- Teamwork makes the dream work: Support each other and watch the Slack Channels.