Define ready work
Sprint planning improves when the team agrees on what makes an item ready. Supply the proposed backlog, readiness criteria, known dependencies, and any capacity inputs the team trusts.
Ask Nema to flag gaps rather than fill them. Missing acceptance criteria should stay missing until the product or engineering owner provides them.
Prepare the packet
Nema can group work by goal, identify items without owners or estimates, and show dependencies that cross teams. It can summarize recent channel decisions that change scope, provided those messages are within the allowed context.
The result is a planning aid. It is not a commitment or an automated estimate.
Include work carried over from the previous sprint and explain why it moved. That context can reveal a dependency or scope problem. Nema can group carried work without assuming it must receive priority.
Review in Slack
Post the packet before the meeting so engineers and product managers can resolve straightforward gaps. A teammate can add a dependency, correct an outdated status, or remove an item from consideration. Nema updates the packet in the thread.
A practical example
The proposed sprint has twelve items. Nema finds four without acceptance criteria, two blocked on an API change, and one whose owner is on leave. It groups the remaining work by sprint goal and asks the team to confirm the available capacity.
The product manager supplies criteria for two items. Engineering decides which dependency risk to accept and makes the final commitment during planning.
Keep estimates human
Past velocity can inform discussion, but it does not prove future capacity. Leave estimates, tradeoffs, and commitment with the team. Nema can show the inputs and record the decision afterward.
After planning, ask Nema to summarize what entered the sprint, what was deferred, and which assumptions the team accepted. This creates a reference for the next review without replacing the issue tracker.
If priorities change after planning, return to the same record. Nema can show which committed item would move and which dependency changes, while the team decides whether to revise the sprint.
Common questions
Can Nema estimate story points?
It can summarize historical information if provided, but the team should own estimates and commitment.
Can Nema change the backlog?
It can draft proposed changes. Actual writes require a verified connection and the team's approval policy.
What makes the packet useful?
A clear readiness checklist, current backlog export, and explicit dependency owners produce a more reliable review.