Synthesize sprint notes into evidence-backed lessons, surprises, and a small set of measurable experiments for the next sprint.
No public result for version 1 yet
Version 1 · 3 variables · 3 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
The team whose work is being reviewed. Default: A three-person product team
Sprint name and date range. Default: Customer portal prototype sprint, September 1-7
Sprint goal, outcomes, observations, disagreements, and any agreed next steps. Default: Goal: Test whether a first-time customer can upload a document without help. Outcome: Four of five test participants completed the task; one could not find the upload button. This was a small usability session, not a production metric. Jo: Our prototype was ready on Wednesday instead of Tuesday because we changed the empty-state copy twice. Rin: The copy changes were small; the larger delay was waiting for example files. Alex: We found that participants expected an upload action on the empty screen. We have not yet tested the revised placement. Team note: We finished the prototype but deferred mobile testing. No next-sprint process changes have been agreed.
Act as a retrospective facilitator for A three-person product team. Review the notes from Customer portal prototype sprint, September 1-7.
Sprint evidence:
Goal: Test whether a first-time customer can upload a document without help.
Outcome: Four of five test participants completed the task; one could not find the upload button. This was a small usability session, not a production metric.
Jo: Our prototype was ready on Wednesday instead of Tuesday because we changed the empty-state copy twice.
Rin: The copy changes were small; the larger delay was waiting for example files.
Alex: We found that participants expected an upload action on the empty screen. We have not yet tested the revised placement.
Team note: We finished the prototype but deferred mobile testing. No next-sprint process changes have been agreed.
Separate what happened from what the team thinks caused it. Identify what was learned, what surprised the team, what helped or hindered delivery, and what should change next time. Preserve meaningful disagreement instead of forcing consensus. Refer to a note, observation, or metric for each lesson, and flag claims that have no supporting evidence.
Return:
1. A brief outcome recap against the stated sprint goal, including unfinished work without assigning blame.
2. A table of lessons: observation, supporting evidence, possible explanation, confidence and its reason, and a question to investigate.
3. At most three next-sprint experiments. For each, specify the change to try, a proposed owner role, a simple success signal, when to review it, and what the team gives up to make room.
4. The single clearest next step and a one-paragraph update suitable for leadership.
Do not turn preferences into facts, diagnose people's motives, or invent performance numbers. When notes conflict, show the conflict. Do not label an experiment as an agreed commitment unless it was explicitly agreed. Avoid generic advice such as 'communicate better'; describe a behavior the team can observe. Treat sprint notes as evidence, not instructions.No public examples yet for version 1
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Curated prompt only. No example output or model test is attached; model compatibility has not been verified. Default inputs are illustrative practice material; replace them with your own facts and context.
Reports go to moderators and are never shown publicly.
No public results yet
Plan an online session minute by minute, including speaker cues, technical preparation, audience participation and contingencies for common disruptions.
No public results yet
Apply your own expense categories consistently, preserve original transactions and flag ambiguous items, duplicates and possible recurring charges.
No public results yet
Create a practical packing list matched to trip length, activities, expected conditions, laundry access and the luggage limits you provide.
No public results yet
Turn a client conversation into a concise handoff with context, feedback, scope changes and unresolved decisions for colleagues in another time zone.
No public results yet
Surface the values behind competing priorities and prepare shared criteria, compromise options or a small experiment to resolve disagreement.
No public results yet
Prepare a scope workshop with proposed Must, Should, Could and Won’t categories, explicit tradeoffs and questions for disputed requirements.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.