Overview and Rules
Sprints Overview
The bootcamp is structured into 4 sprints, each focused on a specific system module and different technologies and concepts. This approach allows for progressive learning and the incremental construction of the feedback system.
Skills Developed per Sprint
In addition to business objectives, each sprint will focus on specific technical skills:
Rules and Guidelines
General Rules
-
Participation in Ceremonies: All team members must participate in Scrum ceremonies (Daily, Planning, Review, Retrospective).
-
Communication: Maintain transparent and frequent communication. If you encounter difficulties, communicate them as soon as possible.
-
Code Quality: All code must follow the established quality standards (Clean Code and SOLID).
-
Code Review: All code must be reviewed by at least one other team member and the tech lead tutor before being integrated.
-
Do not break the stories: The stories are already broken down in a very granular way. Breaking them down further will create unproductive granularity. The task breakdown is also already done here in this manual in the Detailed Epics sections of each sprint. Only change the breakdown if you think it can help reduce merge conflicts in pull requests.
Note
It is very important not to break the stories down more than they already are. Create new stories only in cases of bugs or important technical adjustments.
AI Usage
-
AI First Approach: Use AI tools like Flow to increase your productivity, but maintain critical thinking.
-
Review of Generated Code: All code generated by AI must be critically reviewed before being integrated.
-
Balancing: Find a balance between using AI and developing your own technical skills.
Evaluation
During the bootcamp, you will be evaluated based on the following criteria:
-
Technical Quality: Ability to apply the presented concepts and technologies.
-
Collaboration: Active participation in ceremonies and contribution to the team's success.
-
Adaptability: Ability to learn new technologies and adapt to different contexts.
-
Problem Solving: Skill in identifying and solving problems effectively.
-
Communication: Clarity in communicating ideas, problems, and solutions.
-
Value Delivery: Ability to deliver features that meet business requirements.
Technical Evaluation Details
Here is the list of what will be evaluated throughout the bootcamp. It is not necessary to study all these techniques at once; you will have the opportunity to deal with all of them gradually during the bootcamp. This list is here so you are aware that we will be evaluating these topics to understand which CI&T contexts you will fit into at the end of the bootcamp. This is your opportunity to show which skills you prefer to master to specialize within CI&T. Although a Full Stack profile is very good, specialist profiles in areas like Frontend, Backend, or Data are always welcome.
Here is a summary of what we want to see regarding technical competencies:
- Versioning: such as the use of the branch model, commit creation, and conflict resolution. The ability to understand and apply merge concepts is also essential.
- JAVA Programming: We want you to apply the concepts of Spring, JPA, Generics, and JUnit.
- REACT Development: The focus will be on the efficient use of React Hooks, granular componentization, and integrations with Next.js to ensure you build modern and responsive interfaces.
- Python: We will evaluate your aptitude in applying object-oriented programming concepts with Python, especially in implementing repositories and controllers, as well as your ability to work with entities.
- DDD (Domain Driven Design): Your ability to understand and apply DDD principles, such as defining subdomains, entities, repositories, and services.
- TDD (Test Driven Development): The application of functional, integration, and decoupled tests to ensure code quality and the robustness of deliveries.
- NodeJS: We want to see how you use Promises, Express, and Middlewares.
- SOLID and Coding Standards: The ability to apply at least these 3 SOLID principles: S, L, and D.
- Requirements Understanding: We expect you to demonstrate an understanding of the project requirements and know how to break them down into manageable tasks, as well as understand their interactions.
Behavioral Competencies are as Important as Technical Competencies
During the bootcamp, the main behavioral competencies (Soft Skills) we will evaluate are:
- Task Management: Active participation in meetings, updating task statuses, and collaborating with the team are essential for the project's smooth progress.
- Learning Ability: The pursuit of new knowledge and the willingness to apply new skills in daily work are highly valued.
- Proactivity: We want to see how you handle feedback and changes, maintaining a collaborative attitude and being alert to opportunities for improvement.
- Communication: Clear expression of ideas, seeking help when necessary, and communicating the impacts of your activities are fundamental for team integration.
- Execution: We look for quality in your activities, with an understanding of the team's workflow, on-time delivery, and identification of areas where you can improve your effectiveness.
- Teamwork: We want to observe how you recognize the role of each team member, your adaptation to group dynamics, active participation in discussions, and development of positive relationships, respecting everyone's contributions.
Note
We have already said that the bootcamp is not a competition, but you will be evaluated on both technical and code quality, as well as behavior. This is important for us to allocate you to teams after the bootcamp.
Note
Remember that we are not expecting you to have this knowledge right from the start, but this is a roadmap of what you can develop throughout the Bootcamp internship!
Structure of Each Sprint
Each sprint will last 2 weeks, with the following structure:
Day 1: Sprint Start
- Sprint Planning: Planning the sprint delivery using the planning guide.
- Development Kick-off: A round of Story Openings among team members.
Days 2-9: Development
- Daily Scrum: Daily team synchronization.
- Development: Implementation of features.
- Code Review: Continuous review of the produced code.
Day 10: Sprint Closing
- Development Wrap-up: Completion of pending tasks.
- Sprint Retrospective: Reflection on the process and identification of improvements.
- Coffee Break: Relax, have a coffee, and network.
Note
The project was planned to run in 4 sprints, each focused on a specific module and with a well-defined business objective. But it's important to remember: sprint and feature are different things. Don't worry if they aren't always aligned. Here, the main thing is to learn from the process. This simulation is an opportunity to grow, so more than just delivering the product on time, we want each sprint to help you better understand how everything works.
Next Steps
Now that you understand the structure and rules of the bootcamp, you are ready to dive into the first sprint. Sprint 1 will focus on user management and authentication, establishing the foundation for the rest of the system.
Remember that the bootcamp is a learning journey. Don't worry about mastering all the technologies and concepts from the beginning. The important thing is to maintain a growth mindset and learn from every challenge.
Good luck and happy coding!