Capstone Project:
Getting Started
Congratulations on reaching the final phase of the bootcamp! The Capstone Project is your chance to demonstrate all the skills you've learned. This project is a crucial step toward graduation, and we're excited to see what you create.
The final product should be a fully functional application that you've designed and built from the ground up. Before you begin coding, you'll need to complete the following three steps within the first two days of the Capstone Project:
- Determine Your Team Preference
- Submit Your Project Proposal
- Get Project Approval
Step 1: Team Preference
Decide how you'd like to work on this project. You can work alone, with a partner, or in a group. Please let a coach know your preference as soon as possible.
Step 2: Project Proposal
Your proposal should be more than just a project title. You will need to submit a comprehensive plan that outlines the key aspects of your project. This proposal must include:
- Project Description: A brief overview of your project idea.
- Feature Prioritization: A list of must-have features (the essential components for a functional project) and nice-to-have features (optional additions if time permits).
- Page Sketches: A simple diagram or sketch of your web pages to visualize the layout and user flow. A complex wireframe is not necessary; a clear drawing is sufficient.
- Database Design: A plan for your database schema, outlining your collections and their references.
- Technology Stack: A list of the specific technologies, libraries, and APIs you intend to use.
If you are unsure, we recommend you to use the technologies that we taught you in the bootcamp so far.
Step 3: Project Approval
Your project idea and proposal must be approved by a coach before you can begin to work. This approval must be obtained within the first two days of the capstone period.
Once your project is approved, you can start creating user stories to guide your development process. This will help you break down each feature into actionable steps.
Project Period and Requirements
You will have approximately two weeks to complete this project. The final deliverable must be a functional application. Your graduation is dependent on the successful completion of this project.
Daily Attendance:
Daily attendance is also mandatory. If you are absent for any reason, you must inform your coach immediately.
Mandatory Progress Check-ins:
Throughout the project, you will have scheduled check-ins to showcase your progress. Your attendance at these meetings is mandatory. Missing a check-in without prior notification may impact your ability to graduate. If you are unable to attend due to unforeseen circumstances, you must inform a coach as soon as possible to reschedule.
Remember: For specific schedules and cohort-related updates, check your cohort channel and the official schedule.
Capstones Routines
Daily
| 9:00 am | 9:30 am | 4:45 pm |
|---|---|---|
| Student Meeting without coaches | Daily Standup with teams and Coaches | Checkout |
| What did I/we work on yesterday? | ||
| What will I/we work on today? | ||
| Any blockers? |
Participation in Google Meet is required for the whole day.
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 Management: 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 Discord Channels.
- DRY: Don't repeat yourself