스프린트 플래닝·추정 회의 영어 표현 가이드: Story Point 논의·기술 부채 대화·백로그 리파인먼트 실전 영어

[미팅 오프닝]

"Alright everyone, let's kick off our sprint planning for Sprint 24."
(자, 모두들 스프린트 24의 플래닝을 시작합시다.)

"Before we dive into the backlog, let's align on the sprint goal."
(백로그에 들어가기 전에, 스프린트 목표를 맞춰봅시다.)

"The Product Owner has proposed the following sprint goal:
deliver the checkout optimization feature to staging."
(Product Owner가 다음과 같은 스프린트 목표를 제안했습니다:
체크아웃 최적화 기능을 스테이징에 배포하는 것.)

"Does anyone have concerns about this sprint goal?"
(이 스프린트 목표에 대해 우려사항이 있는 분?)

[가용성 확인]

"Let's do a quick capacity check. Any PTO or reduced availability
this sprint?"
(가용성을 빠르게 확인합시다. 이번 스프린트에 휴가나 가용성이
줄어드는 분이 있나요?)

"I'll be out on Thursday and Friday, so my capacity is about
60 percent this sprint."
(목요일과 금요일에 부재할 예정이라 이번 스프린트 가용성은
약 60퍼센트입니다.)

"We also have the on-call rotation — Sarah is primary on-call
this sprint."
(온콜 로테이션도 있습니다 — 이번 스프린트는 Sarah가
Primary 온콜입니다.)

[벨로시티 논의]

"Let's start by reviewing our velocity from the last sprint."
(지난 스프린트의 벨로시티를 검토하는 것부터 시작합시다.)

"Our average velocity over the last three sprints has been 42 points."
(최근 세 스프린트의 평균 벨로시티는 42포인트였습니다.)

"Given the reduced capacity, I'd suggest we plan for about
35 points this sprint."
(가용성이 줄어든 것을 고려하면, 이번 스프린트는 약 35포인트로
계획하는 것을 제안합니다.)

"Keep in mind that velocity is a forecast, not a commitment."
(벨로시티는 예측이지 약속이 아니라는 점을 기억합시다.)

[상황: Scrum Master(Alex)가 스프린트 플래닝을 시작한다]

Alex (Scrum Master):
  "Good morning, team. Let's kick off Sprint 24 planning.
   First, a quick capacity check — any time off or
   reduced availability?"

You (Developer):
  "I have a dentist appointment on Wednesday afternoon,
   but otherwise I'm fully available."

Sarah (Developer):
  "I'm primary on-call this sprint, so I'd say my capacity
   is about 80 percent."

Alex:
  "Noted. Our velocity last sprint was 45 points, and
   the three-sprint average is 42. With Sarah's reduced
   capacity, I'd suggest we target around 38 points.
   Does that feel reasonable?"

You:
  "That sounds about right. We also carried over two
   unfinished stories from last sprint, so we should
   factor those in first."

Alex:
  "Great point. Let's pull those in and then look at
   the prioritized backlog."

[Planning Poker 진행]

"Let's estimate this story using planning poker.
 Everyone, show your cards on three — one, two, three."
(이 스토리를 플래닝 포커로 추정합시다.
 셋에 카드를 보여주세요 — 하나, 둘, 셋.)

"We have a spread — I see a 3, two 5s, and an 8.
 Let's hear from the low and high estimators."
(추정값이 퍼져 있네요 — 3이 하나, 5가 둘, 8이 하나입니다.
 가장 낮은 분과 높은 분의 의견을 듣겠습니다.)

"Can you walk us through your reasoning for the 8?"
(8로 추정하신 이유를 설명해 주시겠어요?)

[추정 근거 설명]

"I'd estimate this at 5 points — there's moderate complexity
in the integration layer, and we've done similar work before."
(5포인트로 추정합니다 — 통합 레이어에 중간 정도의 복잡도가 있고,
이전에 비슷한 작업을 한 적이 있습니다.)

"I went with 8 because this touches three different services,
and the testing effort alone could take a full day."
(8로 잡은 이유는 세 가지 서비스에 걸쳐 있고,
테스트만으로도 하루가 걸릴 수 있기 때문입니다.)

"My concern is the unknown unknowns in the legacy code path.
 That's why I estimated higher."
(레거시 코드 경로에서 예측 불가능한 요소가 우려됩니다.
 그래서 더 높게 추정했습니다.)

[스토리 분할 제안]

"This story feels too large. Can we split it into smaller,
independently deliverable pieces?"
(이 스토리가 너무 큰 것 같습니다. 독립적으로 전달 가능한
작은 조각으로 분할할 수 있을까요?)

"I'd suggest splitting this into the API layer and the
frontend implementation as two separate stories."
(API 레이어와 프론트엔드 구현으로 두 개의 별도 스토리로
나누는 것을 제안합니다.)

"If we can't estimate it confidently, maybe we need a
spike first to reduce the uncertainty."
(자신 있게 추정할 수 없다면, 불확실성을 줄이기 위해
먼저 스파이크가 필요할 수 있습니다.)

[상황: 팀이 결제 시스템 리팩토링 스토리를 추정한다]

Alex:
  "Next story — refactor the payment processing module
   to support the new payment gateway. Cards up —
   one, two, three."

(카드를 보여준 결과: You=5, Sarah=8, Mike=5, Alex=3)

Alex:
  "Interesting spread. I went with 3 because we already
   have the adapter pattern in place. Sarah, why 8?"

Sarah:
  "The adapter pattern helps, but we also need to handle
   three new error codes and update the retry logic.
   Plus, the current test coverage is only at 40 percent,
   so we'll need significant testing effort."

You:
  "That's a fair point about the test coverage. I hadn't
   considered the retry logic changes. I'd revise my
   estimate up to an 8 as well."

Mike:
  "Same here. With the testing effort, 8 makes more sense."

Alex:
  "I'm convinced. Let's go with 8. Sarah, good catch
   on the test coverage gap."

[기술 부채 보고]

"I'd like to flag a growing area of technical debt
in our authentication module."
(인증 모듈에서 기술 부채가 증가하고 있는 부분을
알리고 싶습니다.)

"This technical debt is increasing our cycle time by
roughly 20 percent for any story that touches the
user service."
(이 기술 부채가 사용자 서비스에 관련된 스토리의 사이클 타임을
약 20퍼센트 증가시키고 있습니다.)

"We've been working around this issue for three sprints now,
and the workarounds are becoming increasingly fragile."
(이 문제를 세 스프린트 동안 우회해서 처리해 왔는데,
우회 방법이 점점 취약해지고 있습니다.)

[PO와의 기술 부채 논의]

"If we don't address this now, every feature that touches
payments will take an extra two to three days."
(지금 해결하지 않으면, 결제에 관련된 모든 기능이
추가로 이삼일이 더 걸립니다.)

"I'm not proposing we stop everything — I'm suggesting
we allocate 20 percent of our capacity to pay down
this debt over the next two sprints."
(모든 걸 멈추자는 게 아닙니다 — 다음 두 스프린트에 걸쳐
가용성의 20퍼센트를 이 부채 해소에 할당하자는 것입니다.)

"The risk of not addressing this is that our deployment
frequency will continue to drop, and incident response
time will increase."
(이걸 해결하지 않으면 배포 빈도가 계속 떨어지고,
장애 대응 시간이 늘어날 위험이 있습니다.)

[상황: 당신이 PO(Jessica)에게 기술 부채 해소의 필요성을 설명한다]

You:
  "Jessica, I'd like to bring up a technical debt item
   during this planning session. Our database query layer
   in the order service has accumulated significant debt
   over the past six months."

Jessica (PO):
  "Can you help me understand the impact? How does this
   affect our delivery timeline?"

You:
  "Sure. Right now, any story that involves order-related
   queries takes about 30 percent longer than it should.
   Last sprint alone, we spent an extra three days
   on workarounds."

Jessica:
  "That's substantial. What would addressing this look like?"

You:
  "I'd propose a two-sprint approach. We dedicate about
   15 percent of our capacity each sprint to incrementally
   refactor the query layer. We wouldn't need a full
   feature freeze — we can do this alongside regular work."

Jessica:
  "And what's the expected outcome?"

You:
  "After the refactoring, we expect order-related stories
   to return to their normal velocity. We'd also reduce
   our P2 incident rate in that area, which has been
   trending upward."

Jessica:
  "That makes sense. Let's include it in the sprint backlog.
   Can you create the stories so we can track progress?"

You:
  "Absolutely. I'll break it down into four incremental
   stories and have them ready by end of day."

[DoR 확인]

"Does this story meet our Definition of Ready?"
(이 스토리가 우리의 Definition of Ready를 충족하나요?)

"We're missing the acceptance criteria for the error
handling scenarios."
(에러 처리 시나리오에 대한 인수 조건이 빠져 있습니다.)

"I don't think this is ready for estimation yet.
 We need design mockups for the new UI flow."
(아직 추정할 준비가 안 된 것 같습니다.
 새 UI 플로우의 디자인 목업이 필요합니다.)

[인수 조건 논의]

"Can we clarify the acceptance criteria for this story?
 I want to make sure we're aligned on what 'done' looks like."
(이 스토리의 인수 조건을 명확히 할 수 있을까요?
 '완료'가 어떤 모습인지 맞춰두고 싶습니다.)

"Should the acceptance criteria include performance
requirements? For example, response time under 200
milliseconds?"
(인수 조건에 성능 요구사항도 포함해야 할까요?
 예를 들어, 응답 시간 200밀리초 이내?)

"I'd suggest we add a criterion for backward compatibility
with the existing API consumers."
(기존 API 소비자와의 하위 호환성에 대한 조건을
추가하는 것을 제안합니다.)

[의존성 식별]

"This story has a dependency on the platform team's
API changes. Have those been deployed yet?"
(이 스토리는 플랫폼 팀의 API 변경에 의존성이 있습니다.
 이미 배포되었나요?)

"We're blocked on this until the design team finalizes
the component library update."
(디자인 팀이 컴포넌트 라이브러리 업데이트를 완료할 때까지
이 작업은 블로킹 상태입니다.)

"I'd recommend we identify all cross-team dependencies
upfront to avoid surprises mid-sprint."
(스프린트 중에 서프라이즈를 피하기 위해 팀 간 의존성을
사전에 파악하는 것을 권장합니다.)

[상황: 팀이 다음 스프린트 후보 스토리를 리파인한다]

Alex:
  "Let's look at the next story — implement real-time
   notifications for order status updates."

You:
  "Before we estimate, I want to flag a couple of things.
   First, the acceptance criteria don't specify which
   notification channels we need to support. Is it
   just in-app, or do we also need push and email?"

Jessica (PO):
  "Good question. For the first iteration, let's scope
   it to in-app notifications only. We can handle push
   and email as follow-up stories."

You:
  "That helps scope it down. Second, this has a dependency
   on the notification service that the platform team is
   building. Last I checked, it was still in progress."

Sarah:
  "I spoke with the platform team yesterday. They said
   the notification service should be ready by midweek.
   But I'd suggest we plan a fallback in case it's delayed."

Alex:
  "Agreed. Let's add 'notification service API available'
   as a precondition in the story, and have a backup plan
   to use the existing email service as a temporary bridge."

You:
  "Sounds good. With the scope limited to in-app only
   and assuming the API is available, I'd estimate this
   at 5 points."

[대안 제시]

"Instead of tackling this as one large story, what if
we broke it into two smaller ones?"
(하나의 큰 스토리로 처리하는 대신, 두 개의 작은 스토리로
나누면 어떨까요?)

"What if we timeboxed a spike for half a day to validate
our assumptions before committing to a full estimate?"
(전체 추정을 확정하기 전에 가정을 검증하기 위해
반나절 타임박스의 스파이크를 해보면 어떨까요?)

"I'd like to propose an alternative approach — we could
use the existing middleware instead of building from scratch."
(대안을 제안하고 싶습니다 — 처음부터 만드는 대신
기존 미들웨어를 활용할 수 있습니다.)

[합의 도출]

"It sounds like we're converging on 8 points. Does anyone
still have reservations?"
(8포인트로 수렴되는 것 같습니다. 아직 유보 의견이 있는 분?)

"Let's try a fist-of-five on this estimate.
 Five means fully confident, one means major concerns."
(이 추정에 대해 Fist of Five를 해봅시다.
 5는 완전 동의, 1은 큰 우려를 의미합니다.)

"Can we agree to go with 5 points for now and revisit
if we discover additional complexity during implementation?"
(지금은 5포인트로 가되, 구현 중 추가 복잡도가 발견되면
다시 논의하는 것으로 합의할 수 있을까요?)

[Action Item 정리]

"Let me summarize the action items before we wrap up."
(마무리하기 전에 액션 아이템을 정리하겠습니다.)

"You, Sarah — you'll pair on the database migration story.
 Mike — you'll reach out to the platform team about
 the API dependency."
(당신과 Sarah는 데이터베이스 마이그레이션 스토리를
페어로 진행합니다. Mike는 API 의존성에 대해
플랫폼 팀에 연락합니다.)

"Does anyone need any clarification on their tasks
for this sprint?"
(이번 스프린트 각자의 작업에 대해 추가 확인이 필요한 분?)

[회의 종료]

"We've planned 37 points for this sprint, which is
within our forecasted capacity. The sprint goal is
to deliver the checkout optimization to staging."
(이번 스프린트에 37포인트를 계획했고, 이는 예측 가용성
범위 내입니다. 스프린트 목표는 체크아웃 최적화를
스테이징에 배포하는 것입니다.)

"Our daily standup is at 10 AM as usual. If you hit
any blockers, please raise them there or in the
team Slack channel."
(데일리 스탠드업은 평소와 같이 오전 10시입니다.
블로커가 발생하면 스탠드업이나 팀 슬랙 채널에서
공유해 주세요.)

"Great planning session, everyone. Let's have a
productive sprint."
(모두 좋은 플래닝이었습니다. 생산적인 스프린트가 되길.)

[참여자: Alex(Scrum Master), Jessica(PO), You, Sarah, Mike]

=== Phase 1: Opening ===

Alex:
  "Alright team, let's get started with Sprint 25 planning.
   Quick logistics — we have 60 minutes blocked for this.
   Jessica, do you want to kick us off with the sprint goal?"

Jessica:
  "Thanks, Alex. The business priority this sprint is to
   complete the new onboarding flow. We've been getting
   feedback that the current flow has a 40 percent
   drop-off rate, and this is directly impacting our
   conversion metrics."

Alex:
  "Clear goal. Let's do a capacity check. Any reduced
   availability this sprint?"

Mike:
  "I'm attending a two-day conference on Wednesday
   and Thursday, so about 60 percent capacity for me."

You:
  "Fully available. No conflicts on my end."

Sarah:
  "Same here, fully available."

Alex:
  "Got it. With Mike's reduced capacity, I'd suggest
   we target around 35 points. Our three-sprint average
   is 40, so 35 gives us a comfortable buffer."

=== Phase 2: Story Estimation ===

Jessica:
  "The first and highest-priority story is: 'As a new
   user, I can complete the signup flow in under
   two minutes.' The acceptance criteria are in the
   Jira ticket."

Alex:
  "Everyone had a chance to review this in refinement.
   Let's estimate — cards up. One, two, three."

(Cards: You=5, Sarah=5, Mike=8, Alex=5)

Alex:
  "Mostly aligned. Mike, you're at 8 — what's driving
   the higher estimate?"

Mike:
  "I think we're underestimating the email verification
   step. We need to integrate with the new email service,
   and their documentation is incomplete. I spent an hour
   looking at it yesterday and there are gaps."

You:
  "I hear your point. Have you considered that we could
   use our existing email service for now and swap it out
   later? That would remove the integration risk for
   this sprint."

Mike:
  "That could work as a short-term solution. If we go
   that route, I'd be comfortable with a 5."

Sarah:
  "I'd support that approach. We can create a follow-up
   story for the email service migration."

Alex:
  "Consensus on 5? Great, let's move on."

=== Phase 3: Technical Debt Discussion ===

You:
  "Before the next story, I'd like to bring up a tech
   debt item. The authentication middleware has been
   causing intermittent test failures for the past three
   sprints. It's costing us about half a day per sprint
   in debugging time."

Jessica:
  "How much effort would it take to fix?"

You:
  "I'd estimate it at 3 points. It's mostly about
   replacing the deprecated session handling library
   and updating the related tests."

Jessica:
  "Given that it's been a recurring time sink, I'm
   supportive of including it. Let's add it to the
   sprint backlog."

Alex:
  "Agreed. That brings us to 8 points so far with
   plenty of room."

=== Phase 4: Dependency and Risk ===

Alex:
  "Next story — implement social login with Google
   and GitHub."

Sarah:
  "I have a concern about this one. The security team
   needs to review our OAuth implementation before we
   can go live. Have they confirmed availability for
   a review this sprint?"

Alex:
  "Good catch. I'll reach out to the security team today
   to confirm. If they can't do the review this sprint,
   we might need to adjust our plan."

You:
  "Could we structure the story so that the implementation
   is one story and the security review is a separate
   blocker? That way we can proceed with the code and
   not merge until the review is complete."

Alex:
  "Smart. Let's split it that way."

=== Phase 5: Closing ===

Alex:
  "To summarize — we've planned 34 points for Sprint 25.
   The sprint goal is to deliver the new onboarding flow.
   Action items: I'll confirm the security review timeline,
   Mike will create the follow-up story for the email
   service migration, and everyone starts pulling from
   the top of the board tomorrow morning."

Jessica:
  "Thanks, team. I'm confident about this sprint goal.
   Let me know if any questions come up about the stories."

Alex:
  "Great session, everyone. Let's make it a strong sprint."