XERR ScrumLoop FREE
The goal. The conversations. The result.
Date Window & Activity Totals
A Sprint is more than
a list of busy people.
Connect the people, events and work to one Sprint Goal. See which conversations led to action, what is ready to use and whether the result made a difference.
Who Should Use It · What To Bring · How It Helps
Who
Construction, infrastructure, engineering, manufacturing and service teams. In Scrum, Developers means the people delivering the work: designers, engineers, planners, technicians or service professionals.
When
Choose a useful result: an accepted design package, an installation ready for testing, a safe handover or a completed service improvement. Use short cycles to inspect progress and adapt.
Your data
Bring your current XER, Excel, CSV or readable PDF activity table, then add BL and Previous BL separately. Keep each client and project separate. Your delivery programme remains the source schedule.
The benefit
Discuss blocked work, slipped finishes, upcoming starts and handover checks. Record the decision, next action, owner and date. Check an accepted result, not just a busy team.
For Scrum, agree one Sprint Goal, clear accountabilities and a shared Definition of Done, then hold Planning, Daily Scrum, Review and Retrospective within a Sprint of one month or less. A six-week delivery window supports coordination but is not a Scrum Sprint. Baseline differences are calendar-day comparisons, not a recalculated critical path.
Sprint Settings & Team
Team Members
Upload Files & See Results
Upload a file to load its project resultsUse XER, Excel (.xlsx), CSV or a PDF with readable activity tables. Files stay in this browser tab. You can choose several files together. Each file and project stays separate. Select one project to open or compare. Scanned PDFs and scheduling logs are not activity datasets.
Choose Project / Import Options
File Formats & Project Types
XER: exported projects are listed separately; resource assignments, relationships and float are not recalculated here. Excel: choose one worksheet and map its header columns. ID and name are required; dates, status and owner drive their respective checks. Numeric dates use Excel’s saved date values; text dates use DD/MM/YYYY or YYYY-MM-DD. PDF: readable activity tables only, not scanned pages or schedule logs; verify extracted rows against the original.
For waterfall or hybrid projects use a delivery window. Source activities do not become Scrum decisions, meetings or checked completion automatically. Record these only where they apply. Six weeks is a delivery cycle, not a Scrum Sprint. Save each workspace before opening another project.
Load Current first, then assign BL and Previous BL through File Role. If the baseline uses a different Project ID, explicitly confirm its link to the current project. Matching uses Activity IDs. Choose the comparison basis under Date Window & Activity Totals. Positive Δ means Current finishes later than the selected reference, in calendar days.
Import Notes
01The project engine
02People & decisions
Project Team & Participation
What came out of the conversation?
03Decisions that need follow-through
Product Backlog Refinement Notes
Daily Scrum · Auto Agenda
04What could stop delivery?
Snapshot Comparison
Upcoming Work & Handover
Product Backlog · Project Activities
05Did the Sprint make a difference?
Track a result that matters: accepted deliverables, passed inspections, reduced rework or faster handovers. Each dial uses your own unit and target.