Module 2: Build Sprint 1

Understanding Your First Ticket

This is the first Build Sprint of Labs. Now that you are locally setup, it's time to start work on your first ticket.

First Ticket Details

View your first ticket details and requirements on GitHub:

First Ticket Documentation

Note: You should be working off a forked version of the starter repo.

Step-by-Step Workflow

Here is the exact step-by-step workflow you should follow when you access your ticket above:

1. Familiarize Yourself with the Repository
  • Read the documentation thoroughly to understand the repository. This may include API contracts, READMEs, or docs on Google/Notion.
  • Check the README of the ticket you have been assigned to know what is expected of you.
2. Understanding the Deliverable
  • Check the deployed version of the product to see the expected output and match it with what you have to build.
  • Read the example of the expected output provided in the README.
3. Code Unit Test (if applicable)
  • If a relevant test exists, follow the test-driven development approach to guide your development.
  • Validate your code using the unit test to ensure you've produced the expected outcome.
4. Code the Component/Feature
  • Code your deliverable, the feature described in the ticket.
5. Record a Loom Video
  • Demonstrate the feature in the video.
  • Provide a detailed explanation of your thought process while coding.

Key Components of a Ticket

  • Title - Clear description of the task
  • Description - Detailed explanation of what needs to be done
  • Acceptance Criteria - What conditions must be met for the ticket to be considered complete
  • Story Points - Estimate of complexity/effort
  • Priority - How important/urgent the ticket is
  • Assignee - Who is responsible for completing the ticket
  • Status - Current state of the ticket (To Do, In Progress, etc.)

Submit your Sprint 1 Deliverables: Loom and Code

Technical Interview Simulation

You're in the middle of your first technical interview. The interviewer is going through your resume and stops at the section describing your Labs project. They turn to you and ask:

"How would you describe the project you built in BloomTech Labs and the contributions you had on it?"

Using Loom, record a video articulating to a hiring manager the product you'll be working on in Labs. Feel free to reference your code and ticket.

You should concisely answer the following questions:

  • What were the deliverables for your ticket?
  • What requirements did you have to keep in mind? Think tech stack, constraints, etc.
  • How did you go about shipping your ticket?
  • Why did you take the approach you took?

The video should be no longer than 5 minutes, and you must demo the project in the video.

Submission Details

Submit the links to your Loom video and code on GitHub using the form below.

You can access the submission form here.

Note: If any one link is missing, the assignment will not be graded and you will have to resubmit.

Your code should:

  • be on a forked version of the project repo.
  • meet all the requirements listed on the ticket in the README file for this build sprint.

In your Loom video, you must:

  • demo the code you created for this ticket.
  • articulate how you coded this ticket and why you took that approach.
  • showcase your workflow and what steps you took to code this ticket.

All submissions will be graded based on criteria set forth in the rubric below.

Never used Loom before?

How to get started with Loom

How to use the Loom Chrome Extension

Build Sprint Grading Criteria

Criteria Ratings
This criterion is linked to a Learning OutcomePresenting Their Work
The student clearly and accurately explains all aspects of their work, including their approach, design decisions, and results.		 Meets Expectations Needs Improvement
This criterion is linked to a Learning OutcomeOrganization
The video is well-organized, easy to follow, and presents information in a logical and coherent manner.		 Meets Expectations Needs Improvement
This criterion is linked to a Learning OutcomeTechnical Knowledge
The student demonstrates a solid understanding of the technical concepts and tools used in their work. They are able to answer technical questions.		 Meets Expectations Needs Improvement
This criterion is linked to a Learning OutcomeCode Quality
The code is well-organized and readable, follows the best practices that they learned, and the code is readable 		Meets Expectations Needs Improvement
This criterion is linked to a Learning OutcomeFunctionality
The code runs without errors and produces the expected results. The code is complete and meets the requirements of the assignment.		 Meets Expectations Needs Improvement
This criterion is linked to a Learning OutcomeCommenting
Comments are clear and provide enough information to understand the purpose and function of the code.		 Meets Expectations Needs Improvement
This criterion is linked to a Learning OutcomeCorrectness
The code is implemented in a correct, efficient and optimal way.		 Meets Expectations Needs Improvement
This criterion is linked to a Learning OutcomeTest Execution
The student is able to execute tests and document issues or bugs found. They are able to explain how the tests are verifying the functionality of the system.		 Meets Expectations Needs Improvement
This criterion is linked to a Learning OutcomeCommunication & Delivery
The student communicates effectively and professionally, speaking clearly, using appropriate nonverbal communication, and expressing themselves in a confident and engaging manner. They show active listening skills and can build rapport.		 Meets Expectations Needs Improvement
This criterion is linked to a Learning OutcomePreparation & Self-Presentation
The student presents themselves in a professional and polished manner and is well-prepared. They project confidence and enthusiasm.		 Meets Expectations Needs Improvement
This criterion is linked to a Learning OutcomeAdaptability
The student demonstrates an ability to adapt to new information and respond appropriately to unexpected questions or changes in the interview. They display flexibility and some initiative.		 Meets Expectations Needs Improvement

Backend Implementation

Learn how to implement backend features using Spring Boot, including REST endpoints, services, and repositories.

Key Concepts

  • Controllers - Handle HTTP requests and responses
  • Services - Contain business logic
  • Repositories - Interface with the database
  • DTOs - Data Transfer Objects for request/response payloads
  • Entities - Database models

Resources

Testing Your Code

Learn about writing unit tests and integration tests for your Spring Boot application.

Testing Strategies

  • Unit Tests - Test individual components in isolation
  • Integration Tests - Test interactions between components
  • Mock Objects - Simulate dependencies for unit testing
  • Test Containers - For database and other infrastructure tests

Example Test

@SpringBootTest
public class AssignmentServiceTest {

    @MockBean
    private AssignmentRepository assignmentRepository;
    
    @Autowired
    private AssignmentService assignmentService;
    
    @Test
    public void testGetAssignmentById() {
        // Arrange
        Assignment assignment = new Assignment();
        assignment.setId(1L);
        assignment.setTitle("Test Assignment");
        
        when(assignmentRepository.findById(1L))
            .thenReturn(Optional.of(assignment));
        
        // Act
        AssignmentDTO result = assignmentService.getById(1L);
        
        // Assert
        assertNotNull(result);
        assertEquals("Test Assignment", result.getTitle());
        verify(assignmentRepository).findById(1L);
    }
}

Resources

Code Reviews

Learn how to effectively review code and respond to feedback on your own code.

Code Review Best Practices

  • Be Specific - Point to specific lines and explain issues clearly
  • Ask Questions - Instead of making demands, ask questions to understand the code
  • Focus on the Code - Not the coder
  • Provide Constructive Feedback - Suggest improvements, not just point out problems
  • Be Timely - Review code promptly to avoid delays
  • Be Open to Discussion - Code reviews should be a dialogue

Resources

Daily Standups

Learn about daily standup meetings and how to communicate effectively with your team.

Standup Format

In a standup meeting, each team member typically answers these three questions:

  1. What did I accomplish yesterday?
  2. What will I work on today?
  3. What blockers or challenges am I facing?

Keep your update concise and focused on these points. If detailed discussions are needed, they should be taken "offline" after the standup.

Tips for Effective Standups

  • Be Punctual - Arrive on time or even a few minutes early
  • Be Prepared - Know what you're going to say before the meeting starts
  • Be Concise - Keep your update under 2 minutes
  • Listen Actively - Pay attention to what others are saying
  • Focus on Progress - Highlight movement toward sprint goals
  • Raise Blockers - Don't hesitate to mention impediments

Resources