iteration planning

 During Refinement

Focus on:

clarity

readiness

dependencies

technical understanding

blockers

You MAY:

suggest tentative weight

discuss possible owner

During Iteration Planning

You should actively:

add iteration

assign engineer

add weights

confirm priorities

move status

confirm commitment

“Let’s go through the prioritized items for this iteration, validate readiness and align on ownership and delivery expectations.”

“Before we plan the next iteration, let’s quickly review current iteration items and identify what will be completed by Friday and what needs to carry forward.”

Which items need to carry over?

Which items should go back to backlog?

Ask engineers:

“Is this expected to close by Friday?”

“If not, should we carry this into next iteration or move it back to backlog?”

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$4

“Now let’s move to planning the next iteration and review the prioritized/backlog candidates we want to commit.”

Opening First Item

“Let’s start with this item. It’s currently prioritized for upcoming iteration. Can we quickly validate readiness and ownership here?”

-

“Is ownership already aligned?”

“Still on track?”

“Any dependency concerns?”

“Expected completion timeline?”

“Need any support/escalation?”

“Does current weight still look fine?”

Does the weight still look correct?

“Are we comfortable taking this in current iteration?”

##################-

blocked items 

Let’s review blocked items and understand whether any dependency or external action is pending from our side.”

::}

For each blocked item ask:

what exactly is blocked?

by whom?

ETA?

should it remain blocked?

should it move back to backlog?

######################

If Item Has Dependency

“Looks like there’s dependency on Microsoft/Terraform here — are we still comfortable pulling this into current iteration?”

If Blocked

“Since this is externally blocked, should we keep it in iteration for tracking visibility or move it back to backlog until dependency clears?”

#######################

“Since scope and ownership are aligned, shall we commit this item for current iteration?”

Mid-Call Summary

After 20-30 mins:

“So far we have aligned ownership for these items, identified a few dependency risks and still need confirmation on couple of pending implementations.”

Closing the Call

Last 5 mins:

So for the next iteration, we are carrying forward these items and adding these new items. Any concerns on capacity or delivery risk before we finalize?

“Before we close — any additional risks, dependency concerns or items we should not commit for this iteration?”

::}

Then:

“I’ll update the board/items accordingly after the call. Thanks everyone.”

##

@@ Labels

Which items need to carry over?

Which items should go back to backlog?

Weight by Emgineer