Meeting Participation

Meeting: Sprint Planning
Time: Tuesday 10am (2 hours)
Attendees: Dev team + PM

Agenda:
- Review last sprint velocity
- Prioritise user stories
- Estimate effort
- Identify blockers

My prep:
- Review user stories beforehand
- Prepare questions about requirements
- Think about technical dependencies

What I want to say:
✓ Flag technical debt in auth module
✓ Propose refactoring before adding features
✓ Suggest pairing on complex stories

Key phrases to use:
- "I'd like to raise a concern about..."
- "Have we considered...?"
- "I suggest we..."

Terms I might need:
- Refactoring
- Technical debt
- Code review
- Unit testing
- Integration
- Deployment

Interrupting Politely:
"Sorry to interrupt, but..."
"Can I add something here?"
"May I jump in for a moment?"
"Building on what Sarah said..."

Waiting for Pause:
"I have a thought on this."
"Could I add something?"
"I'd like to share a perspective."

Agreeing:
"I completely agree with that approach."
"That's a great point."
"Exactly—I was thinking the same thing."
"That makes sense to me."

Disagreeing:
"I see it differently because..."
"I have a concern about that approach..."
"Have we considered the downside?"
"I'm not sure that will work because..."

Partial Agreement:
"I agree with X, but I'm concerned about Y."
"That's true in most cases, except..."
"Good point, though we should also consider..."

Clarification:
"Could you clarify what you mean by...?"
"I'm not sure I understand. Are you saying...?"
"Just to confirm, you mean...?"

Understanding Requirements:
"What's the expected behavior when...?"
"How should we handle edge cases like...?"
"What's the priority if we can't do both?"

Technical Details:
"What's the performance requirement?"
"Do we need backward compatibility?"
"What's the error handling strategy?"

Proposing Ideas:
"What if we...?"
"Have we thought about...?"
"Another option would be to..."
"I'd like to propose..."

Offering Help:
"I can look into that."
"I'd be happy to research options."
"I can pair with someone on this."
"Let me take that action item."

Immediate:
"I'm sorry, I didn't catch that. Could you repeat?"
"Could you speak a bit more slowly?"
"I'm having trouble hearing you."

Later:
"Can we circle back to the API design discussion? 
I want to make sure I understood correctly."

1. What did you do yesterday?
2. What are you doing today?
3. Any blockers?

"Yesterday I completed the authentication endpoints and 
wrote unit tests. Coverage is at 87%.

Today I'm starting on the password reset flow and will 
pair with Maria on the email integration.

No blockers right now, but I might need help with the 
email template design later this week."

Progress:
"I finished..."
"I completed..."
"I made progress on..."
"I'm about 80% done with..."

Current Work:
"I'm working on..."
"I'm starting..."
"I'm continuing..."
"Today I plan to..."

Blockers:
"I'm blocked by..."
"I'm waiting for..."
"I need help with..."
"I have a question about..."

Asking for Clarity:
"Can you walk through the acceptance criteria?"
"What's the expected user flow?"
"Are there designs for this?"

Estimating:
"This looks like a 3-pointer to me."
"I'd estimate 5 days including testing."
"This is bigger than it looks—maybe split into two stories?"

Raising Concerns:
"We'll need to refactor X first."
"This depends on the API being deployed."
"There's technical debt we should address first."

Volunteering:
"I can take this one."
"I'd like to work on the payment integration."
"I'm interested in the performance optimization story."

PM: "Next story is user profile editing."

You: "Quick clarification—does this include avatar 
upload or just text fields?"

PM: "Just text fields for now."

You: "OK, that's simpler. I'd estimate 3 points. We 
already have the form validation logic, so it's mainly 
wiring up the API. I can pair with someone on this."

Positive Feedback:
"I really appreciated how the team..."
"The new testing approach worked well because..."
"I'm happy with our progress on..."

Constructive Feedback:
"I think we could improve..."
"One challenge I noticed was..."
"I struggled with... and I'm wondering if..."

Suggestions:
"What if we tried...?"
"Could we experiment with...?"
"I'd like to propose we..."

Action Items:
"I'll take ownership of that."
"Can we assign someone to research this?"
"Let's make that an action item."

Facilitator: "What went well this sprint?"

You: "I think the pairing sessions were really effective. 
We solved the caching issue much faster together than 
I would have alone. I'd like to continue that practice."

Facilitator: "What could we improve?"

You: "I noticed we had a lot of last-minute requirement 
changes. Could we freeze requirements midway through the 
sprint? That would help us maintain velocity."

1. Problem Statement
"We need to improve API performance. Current response 
time is 500ms, target is under 100ms."

2. Proposed Solution
"I propose adding Redis caching at the controller level."

3. Alternatives Considered
"I also looked at database query optimization and CDN 
caching, but Redis gives us the most control."

4. Trade-offs
"Pros: Fast, flexible, well-documented.
Cons: Another service to maintain, cache invalidation 
complexity."

5. Open Questions
"Should we cache at the route level or response level?
I'd like feedback on that."

Know the Answer:
"Good question. We handle that by..."
"I researched that, and..."
"The documentation says..."

Don't Know:
"That's a good point. I haven't considered that yet."
"I'm not sure. Can we discuss that after?"
"I'll research that and follow up."

Pushback:
"I understand your concern. The reason I chose this 
approach is..."
"You're right that's a risk. We could mitigate it by..."
"That's a valid alternative. The trade-off is..."

Topics:
- Your progress
- Career goals
- Feedback
- Support needed

Opening:
"Thanks for the time. I wanted to discuss my progress 
on the authentication project and get your feedback."

Asking for Feedback:
"How do you think I'm doing overall?"
"What's one area where I could improve?"
"Am I meeting expectations for my level?"

Discussing Goals:
"I'm interested in moving toward more backend work."
"I'd like to work on my leadership skills."
"Could I take on more complex projects?"

Raising Issues:
"I'm finding it hard to focus with so many meetings."
"I'd appreciate more context on the project priorities."
"I'm not sure I have the support I need for this project."

Pairing Check:
"How did you feel the pairing session went?"
"What could I do to be a better pair?"

Knowledge Sharing:
"I learned a great technique for testing async code. 
Want me to share it?"

Asking for Help:
"I'm stuck on the authentication flow. Do you have 
time to look at it together?"

Company Direction:
"Can you share more about the product roadmap for Q2?"
"What are the company's priorities this quarter?"

Process:
"Will we be hiring more engineers this year?"
"Are there plans to improve the deployment process?"

Clarification:
"Could you clarify what you meant by...?"
"I didn't quite understand the new policy. Could you 
explain...?"

"Sorry, could you slow down a bit?"
"I'm having trouble following. Could you repeat that?"
"Let me make sure I understood [summarise]"

"I'm having trouble with the audio. Could you type 
that in chat?"
"Sorry, I missed that. Could you repeat?"

"That's a good question. Let me think for a second..."
"Hmm, I need to consider that..."
"Could I come back to that in a moment?"
"Let me gather my thoughts..."

Soft:
"I'm not sure I agree because..."
"I see it a bit differently..."
"I have a different perspective..."

Strong (when necessary):
"I disagree with that approach because..."
"I have serious concerns about..."
"I don't think that will work because..."

"But I'm open to being convinced otherwise."
"What am I missing?"
"Help me understand why you think that's the best approach."

"If I could just finish my point..."
"Let me complete this thought..."
"As I was saying..."
"Hold on, I wasn't done yet."

"I appreciate your input, but I'd like to finish 
explaining my reasoning first."

"So if I understand correctly, you're saying..."
"Let me make sure I got this: you want us to..."
"Just to confirm, the plan is to..."

"We have 5 minutes left. Should we wrap up?"
"This is taking longer than expected. Should we schedule 
a follow-up?"
"Let's table this discussion and continue async."

"I took notes—I'll send them to the channel."
"Action items:
- John: Research caching solutions by Friday
- Sarah: Draft API proposal
- Mike: Set up staging environment"

"Thanks for the productive discussion. To summarise:
- We decided to go with approach A
- I'll create the tech spec by Friday
- Sarah will review over the weekend
- We'll start implementation Monday

Let me know if I missed anything."

Good Chat Uses:
- Links to references
- Clarifying questions
- +1 to support ideas
- Sharing code snippets
- Links to docs

Avoid:
- Side conversations
- Jokes during serious topics
- Anything you wouldn't say aloud