Scope Creep

Scope creep: When the scope of the project exceeds the original instructions and additional features get added in the sprint.

Be mindful of this because its very common in various places.

Ways to protect yourself:

• Document every meeting. Don't just take notes, identify action items, who's responsible for them and a summary of what's expected. I usually email them to the team as well, so I have a paper trail of the discussion to be referred later.
• Identify the full scope to the best of your ability. What will it take to get started? What will it take to completion? Are there any blockers? Are there any dependencies? Where are the blind spots in the project?
• Stick to the immediate task of the sprint. I have historically been really bad about this because I want to be able to do everything including deliver the moon! However, when assigned a task for a sprint, its important to stick to the ask at hand to avoid having added responsibility mid-sprint and then being held accountable for that added work when it all comes due.

In what projects have you come across tech debt and how did you mitigate or overcome this?

Stay safe and happy coding, ya'll!