Cimentar Futuro Foundation

Learning Objectives

Participate constructively in a code review
Estimate and communicate progress on a task realistically
Understand agile ceremonies like standups and sprint planning

Writing code that works is only part of being a professional engineer; working well within a team is just as essential. In code review, you will learn to give feedback focused on the code, not the person, explaining the reasoning behind a suggestion rather than just stating a preference, and to receive feedback without defensiveness, since a review's purpose is a better product, not a verdict on your worth. Many teams, including many fully remote teams with engineers across different time zones and countries, use agile practices: short daily standups where each person shares what they did, what's next, and any blockers, and sprint planning, where the team agrees on a realistic scope of work for the next one-to-two-week period. You will also practice realistic estimation, flagging risk early rather than silently falling behind.

Module Quiz

1. A daily standup meeting is typically meant to:

Last at least two hoursReplace all written documentationConduct a full code review of every featureQuickly share progress, next steps, and blockers across the team

2. Effective code review feedback should primarily focus on:

The personal habits of the authorApproving everything quickly to avoid conflictFinding as many unrelated complaints as possibleThe code itself and the reasoning behind suggested changes

3. If you realize midway through a sprint that a task will take longer than estimated, the best practice is to:

Say nothing and hope to catch up unnoticedFlag it to the team as early as possible so plans can adjustRush the work and skip testingWait until the sprint review to mention it

Module 11: Working on an Engineering Team