Developer

How you work

1) …

2) …

3) You own the outcome of your work
You don’t just “implement.” You make sure the issue is truly done: tested, reviewed, and reliable enough that we don’t have to reopen it later.

Part of owning the outcome is giving a realistic estimate and updating it when reality changes (see How We Estimate And Prioritize Issues)

4) You overcommunicate to prevent rework
When scope or acceptance criteria are unclear, you ask early. You confirm your interpretation with the strategist, keep the team updated on progress, share blockers quickly, and always leave a clear trail of what changed and why.

If you want estimates included without adding a third point, fold it into point 1 with one extra sentence:

What you deliver

1) …

2) …

3) Daily short updates on what you are working on

In slack, including links to the specific issues.

4)