A sprint is a two-week block of work in Business OS. At the end of each one, a short retro (a look back) keeps the next sprint honest. Skip it and the same problems roll forward every two weeks.
Armbrain makes the retro easier because the facts are already saved: the sprint's goals, the quarter's rocks, and the commitments made on calls and in email. You bring the judgment.
Ask four questions
- What was this sprint meant to finish?
- What actually shipped, and what slipped?
- For each slip, why? Waiting on the client, too much scope, or something else?
- What is one change for the next sprint?
The last question is the one that matters. A retro without actions is just venting. Save one or two changes as decisions in the client's mind, so the next retro can check whether they stuck.
Armbrain asks before it changes rocks or saves anything to Business OS, so you stay in charge of the record. Read the rocks and sprints guide.