Dev standup je ten istý 15-minutový formát ako v Daily standup po anglicky — ale obsah je ticket, PR, sprint a infra, nie všeobecný „dnes robím report“. Tento článok je pre programátorov v agile/Scrum tíme.
Kontext IT: Angličtina pre IT. Meetingy: Meeting po anglicky.
Dev standup vs. všeobecný standup
<a id="section-0"></a>
| Aspekt | Všeobecný standup | Dev standup |
|---|---|---|
| Referencie | Projekt, klient | Ticket #, PR #, branch |
| Blockery | Schválenie, feedback | Review, env, dependency |
| Done | Úloha hotová | Merged, deployed, in QA |
| Čas | Často fixný | Často po timezone sync |
Štruktúra pre developera
<a id="section-1"></a>
Šablóna s dev kontextom:
Yesterday I [merged/finished/reviewed] [ticket/PR]. Today I'm [implementing/testing/deploying] [ticket]. [Blocker: review / env / dependency / no blockers].
Yesterday — dev príklady
<a id="section-2"></a>
Feature work:
- Yesterday I finished ticket #4521 — password reset flow. PR is merged to develop.
- I completed the API integration for Stripe and pushed to staging.
- I reviewed two PRs from the team and left comments on the auth module.
Bugfix a incident:
- Yesterday I hotfixed the production login issue — deployed at 4 PM.
- I investigated the memory leak — root cause is in the image cache.
Research a spike:
- Yesterday I spike on GraphQL vs REST for the new endpoint — documented pros/cons in Confluence.
- I was in refinement — no coding, but clarified acceptance criteria for sprint 24.
Today — dev príklady
<a id="section-3"></a>
- Today I'm implementing ticket #4530 — export to CSV.
- I'll write unit tests for the payment module and open a PR.
- My plan is to deploy the hotfix to production after QA sign-off.
- I'm pairing with Maria on the OAuth refactor — 2 hours blocked.
Dev blockery — typy a frázy
<a id="section-4"></a>
Code review
<a id="section-5"></a>
- I'm blocked on merge — PR #901 needs approval from a senior dev.
- Waiting on feedback from yesterday's review — one blocking comment on security.
Infra a prostredie
<a id="section-6"></a>
- Staging is down — I can't test the integration.
- I'm blocked on production DB read access for the migration script.
- CI pipeline failed — investigating, might delay my PR today.
Dependencies a iné tímy
<a id="section-7"></a>
- Blocked on the design API spec — backend team promised it Monday.
- Waiting for QA to confirm if this is a bug or expected behavior.
- Third-party SDK update broke our build — need license approval from legal.
Žiadny blocker
<a id="section-8"></a>
- No blockers — PR is in review but I can work on the next ticket.
- All good — moving ticket #4530 to done by EOD.
Detail: Ako vysvetliť blocker po anglicky.
Sprint kontext na standupe
<a id="section-9"></a>
Keď tím sleduje sprint goal:
- We're on track for the sprint goal — checkout refactor is 80% done.
- Sprint goal at risk — we're one ticket behind because of the incident.
- I'll carry ticket #4540 to next sprint — scope was underestimated.
Kompletné príklady
<a id="section-10"></a>
Backend dev (B2)
<a id="section-11"></a>
Yesterday I merged PR #880 — rate limiting on public endpoints. Ticket #4521 is done and in QA. Today I'm starting #4535 — webhook retry logic. I'm blocked on staging credentials — I pinged DevOps in Slack, no response yet. If someone can escalate, that would help.
Frontend dev (B1)
<a id="section-12"></a>
Yesterday I fixed the button on checkout page. Ticket #4499. Today I work on mobile menu — ticket #4502. I need design file for icons — waiting on design team.
Po incidente (B2)
<a id="section-13"></a>
Yesterday was mostly incident response — we rolled back the bad deploy and I wrote the postmortem draft. Today I'm back on feature work — ticket #4510. No blockers.
Frázy pre dev standup
<a id="section-14"></a>
Začiatok:
- Quick dev update…
- From backend side…
- Sprint 24 update from me…
Presun diskusie:
- Technical details — let's sync after standup.
- This needs architecture discussion — not for standup.
Ponuka pomoci:
- I can review your PR after standup if urgent.
- Happy to pair on the OAuth issue — ping me.
Checklist pred dev standupom
<a id="section-15"></a>
- Ticket numbers ready (#4521, not „the payment thing“)
- PR stav — open, in review, merged
- Blocker + kto môže pomôcť
- Sprint impact — on track / at risk (ak relevantné)
- Max 90 sekúnd nahlas
Precvičenie
<a id="section-16"></a>
Napíš standup pre svoj skutočný alebo fiktívny sprint — 4 vety s ticket ID. Povedz nahlas s časovačom. Vyskúšaj standup scenár.
Súvisiace články
<a id="section-17"></a>
| Téma | Článok |
|---|---|
| Všeobecný standup | Daily standup po anglicky |
| Programátori | Angličtina pre programátorov |
| Progress | Progress update po anglicky |
Záver
<a id="section-18"></a>
Standup anglicky pre developerov = konkrétne tickety, PR a technické blockery. Nepotrebuješ dlhý monolog — tím potrebuje vedieť, čo je merged, čo blokuje release a kto môže pomôcť. Priprav čísla ticketov vopred a drž sa 90 sekúnd.