Automation and Principles
The goal is not to replace human judgment. The goal is to automate the facilitation work so humans can focus on the judgment calls.
A scrum master spends most of their time on logistics: scheduling standups, tracking velocity, preparing sprint reviews, maintaining the board, generating status reports. These are real costs. They add up. And they rarely require the scrum master's actual expertise. GoalPath handles the logistics. The judgment calls stay with the team.
What GoalPath Automates
Velocity Tracking
Velocity is calculated weekly from completed work. The unit is story points per week, measured over a rolling six-week window.
One nuance: multitasking has a cost. When one person works on multiple items simultaneously, context switching reduces effective output. GoalPath accounts for this by adjusting estimates using a square root formula. An item estimated at 4 points, shared equally between two owners, contributes 4 / sqrt(2) points to each person's velocity calculation. This produces more accurate throughput data than treating shared items as full credit for each owner.
The six-week window is long enough to smooth noise and short enough to reflect recent changes in team composition or pace. If velocity shifts materially, forecasts update immediately.
Delivery Forecasting
Forecasts run Monte Carlo simulations using real velocity data. The result is a three-point estimate: optimistic, expected, and pessimistic delivery dates.
The simulation draws from the team's actual throughput distribution, not from capacity planning assumptions. A team that finishes three items one week and eight the next has higher variance than a team that consistently finishes five. The simulation captures that variance and reflects it in the range between optimistic and pessimistic outcomes.
Forecasts update automatically as work completes. No spreadsheet math. No manual burndown charts to maintain.
Progress Reports
Progress reports are generated weekly from milestone activity. The structure is consistent: what shipped, what is in progress, what is blocked, and how the forecast changed.
When meaningful activity is detected, a narrative summary accompanies the structured data. When the week was quiet, the report shows the table without narrative. The goal is to give stakeholders accurate information without requiring anyone to write a status update.
Reports support multiple languages. Teams working across regions can generate the same report in each stakeholder's language without additional effort.
Milestone Health Monitoring
Each milestone receives a weekly health assessment: Healthy, At Risk, Critical, Stale, or Insufficient Data.
Health is assessed from three signals: velocity trends over the past six weeks, work completion rate relative to scope remaining, and forecast trajectory relative to the milestone target date. A milestone burning through scope faster than the team delivers is flagged At Risk before it becomes Critical. Stale milestones, where no work has moved in several weeks, are flagged separately.
The health indicator surfaces on dashboards and in reports. Teams that monitor health weekly catch problems earlier than teams that notice them when the deadline arrives.
Meeting Facilitation
Alignment meetings run through six structured stages: Progress and Flow Snapshot, Flow Health and Escalation, Business Value Voting, Visual Roadmap, Roadmap Update, and Decisions and Summary. Each stage has a built-in timer and a notes section. Stage progression is explicit, not ad-hoc.
Standup meetings run through four stages: Inbox, Highlighted Items, Team Members, and Let's Get Going. Same structure: timer, notes, explicit stage transitions.
The structure is not there to constrain the conversation. It is there so the team does not have to spend time deciding what to cover. The agenda is built into the tool.
Priority Normalization
Business value voting supports multiple scoring frameworks: RICE, MoSCoW, Impact and Effort, and Weighted Scoring. Different frameworks weight criteria differently. To compare results across frameworks, voting output is normalized to a 1-100 score.
This makes it possible to look at a backlog and see relative priority regardless of which framework produced the score. The normalization is automatic. Teams get comparable numbers without converting between frameworks manually.
WIP Visibility
The dashboard surfaces current work in progress across the team. Items that have not moved recently are flagged. Flow health indicators show whether the team is pulling work steadily or accumulating bottlenecks.
This is monitoring, not enforcement. GoalPath does not block work or impose hard WIP limits. It shows what is happening so the team can decide what to do about it.
What Stays with Humans
Automation handles the logistics. These decisions stay with the team:
Scope decisions. What to build, what to defer, what to cut. GoalPath provides forecast data to inform scope decisions. It does not make them.
Priority trade-offs. Business value voting produces data: scores, rankings, team input. The final call belongs to the people who understand the business context, customer relationships, and strategic bets involved.
Blocker resolution. GoalPath surfaces blocked items. Resolving blockers requires understanding why they are stuck, which is always a human problem: dependencies, unclear requirements, external teams, technical unknowns.
Estimation. The team estimates. GoalPath tracks accuracy over time. Point inflation, optimism bias, and calibration are team dynamics, not algorithmic problems.
Architecture and technical decisions. Nothing in GoalPath touches these. Technical judgment belongs to the people doing the technical work.
Stakeholder relationships. Progress reports provide accurate information. Navigating how that information lands with different stakeholders is a relationship problem.
Underlying Principles
Weekly Cadence
All automated operations run on Sunday. The working week runs Monday to Sunday, following ISO week numbering. Velocity is calculated, health is assessed, and reports are generated at the end of each week.
A fixed weekly cadence provides predictability without ceremony overhead. There is no debate about sprint length. There is no sprint boundary negotiation. The week ends, the data updates, and the next week begins.
Flow Over Ceremonies
The test for any process element is whether it moves work forward or just accounts for it. GoalPath minimizes time in meetings and maximizes time building. Ceremonies that add structure without adding information are replaced with automated reporting. Ceremonies that require human judgment, like retrospectives and priority discussions, are structured but kept short.
Visibility Over Control
GoalPath monitors work in progress, velocity, and milestone health. It does not enforce WIP limits, block sprint changes, or gate releases. The philosophy is that teams with good information make better decisions than teams working under process constraints they did not choose.
This is a deliberate choice. Hard limits create workarounds. Visibility creates accountability. Accountability tends to produce better behavior than enforcement.
Data Over Opinions
Delivery forecasts come from throughput data, not from how confident the team feels. Velocity comes from actual completions, not from capacity planning assumptions. Health assessments come from trend analysis, not from manager intuition.
This does not mean data is always right. It means the data gives the team something concrete to argue with. "The forecast shows four weeks but I think we can do it in two" is a more productive conversation when both sides have the same underlying numbers.
Process in the Tool, Not in a Wiki
The workflow is in the interface. There is no separate process documentation to maintain, no onboarding videos to watch, no process police to follow up. New team members encounter the process by using the tool. Standup runs the same way for everyone because the tool runs it the same way for everyone.
This reduces process drift. Teams following a documented process gradually diverge from it. Teams using a tool-embedded process cannot diverge as easily.
The Scrum Master Question
GoalPath does not replace a scrum master entirely. It replaces the logistics a scrum master handles.
A scrum master's logistics work includes: tracking velocity, preparing sprint reviews, maintaining the board, generating status reports, facilitating structured meetings, and running retrospectives. GoalPath automates these. For many teams, this is the majority of what they needed a scrum master for.
What GoalPath does not replace: coaching individuals through performance problems, navigating team conflict, managing organizational relationships, running change management processes, and building team culture deliberately.
For teams of five to twenty people, the logistics automation is often enough. The team lead takes on the judgment-heavy coaching work. The facilitation overhead disappears into the tool. The team spends more time building.
If you need dedicated coaching and organizational navigation, GoalPath does not replace that. If you need the reporting, tracking, and meeting structure handled automatically, it does.
See also: Process Framework overview for context on how these pieces fit together, and the ceremony pages for details on alignment meetings and standups.