Reassessment at the Next Sprint
1. Introduction (For Clients & Partners)
Sometimes, a feature or bugfix doesn’t make it to complete release within a sprint, or new information arises that requires further evaluation. In such cases, we move the item into “reassessment” status for the next sprint. This ensures nothing falls through the cracks and that we revisit the item with fresh perspective and updated priorities.
2. Who Is Involved
| Role | Involvement | Benefit to You |
|---|---|---|
| Scrum Master | Tracks incomplete or unresolved items and schedules them for reassessment. | Ensures your feature or bugfix remains visible and doesn’t get abandoned. |
| Product Owner | Confirms if the item still aligns with the roadmap or if it should be deferred. | Provides clear direction on whether to continue, postpone, or rework. |
| Dev Team | Re-evaluates technical constraints, completes carry-over tasks, or updates estimates. | Delivers any additional work needed to finalize or improve the solution. |
| QA Engineer | Re-tests the item in the next sprint if new code is needed or acceptance criteria changed. | Ensures the outcome meets quality standards when finally released. |
| You (Client/Partner) | May be consulted if more details or revised requirements are necessary. | Keeps you informed of the plan for completing your feature or fixing your issue. |
3. Process Flow / Schema
Here’s how an item is re-evaluated at the next sprint (using double quotes in the Mermaid diagram):
- Item Not Completed: A feature or bugfix remains partially done, or new issues arise.
- Mark as “Reassessment”: The Scrum Master tags it for the next sprint’s planning session.
- Review During Sprint Retrospective: The team discusses why it wasn’t completed and what’s needed.
- Decision:
- Yes: If the item still holds business value, it moves to Next Sprint Planning.
- No: If it’s no longer relevant or feasible, we either defer it or reject it altogether (with feedback).
- Next Sprint Work: The Dev Team clarifies tasks, updates estimates, and includes it in the new sprint backlog if capacity permits.
4. Short FAQ
Q1: Why wouldn’t a feature or bugfix be completed in a single sprint?
A1: Reasons include unexpected complexity, shifted priorities, or new details emerging mid-sprint.
Q2: Does “reassessment” mean starting from scratch?
A2: Not necessarily. It typically means we’ll review progress, confirm outstanding tasks, and continue development/testing in the next sprint.
Q3: What if the item is still not done after the next sprint?
A3: It can be reassessed again, deferred, or split into smaller tasks. We aim to avoid endless carry-over by refining the scope or clarifying acceptance criteria.
Q4: Will I be notified if my feature or issue goes to “reassessment”?
A4: Yes, you’ll receive an update explaining why it’s being carried over and an expected timeline for completion in the following sprint.
5. Next Steps & Additional Resources
- Sprint Planning: Learn how we allocate items (including re-assessed ones) to new sprints.
- Deferred vs. Reassessment: Understand the difference between deferring an item (postponed) and actively re-evaluating it next sprint.
- Contact Us: If you have more details or wish to revise your requests, please email
contact+support@aismarttalk.techor consult our chatbot.
By reassessing items in the next sprint, we maintain momentum on partially completed work and ensure that even stalled or delayed features/bugfixes get the attention they need to eventually reach successful release.