These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Sprint / Agile Board
- Features
- Projects
Projects
The Delivery Lead creates a project for an organization, names an owner and sets the planned start and end dates.
OverviewMilestones At Risk×
Sprint / Agile Board · Projects
New
Milestones At Risk
Milestones
| Milestone name | Project | Owner | Due date | Status | |
|---|---|---|---|---|---|
| Milestone 605 | PRJ-1927 | 23 Oct | Missed | ||
| Milestone 611 | PRJ-5458 | 08 Oct | Missed | ||
| Milestone 151 | PRJ-2731 | 10 Oct | Missed | ||
| Milestone 566 | PRJ-9946 | 11 Oct | Missed | ||
| Milestone 732 | PRJ-1000 | 27 Oct | Missed |
6 of 6 records
Milestone 605Milestones · MLS-89111
MissedProjectPRJ-1927
Due date23 Oct
What you can do
Project delivery
The Delivery Lead creates a project for an organization, names an owner and sets the planned start and end dates. The project record brings the budget, delivery method and status together with linked sprint work. A project marked active gives the Project Manager a clear delivery context for every scope and story.
How the work is organized
- Starting record. The Delivery Lead creates a project for an organization, names an owner and sets the planned start and end dates.
- Named owner. Delivery Lead sets the project direction; Project Manager keeps scope and milestones current.
- Current position. The status and linked records tell the team where attention belongs next.
What to agree during setup
Use a project for a real delivery commitment, with one owner accountable for its schedule. Agree when a planned project becomes active and who may mark it at risk or on hold. Keep the organization record current so the team knows which business is receiving the work.
Before opening the project to the team, the Delivery Lead checks the organization, owner and date range. The Project Manager uses that project on its sprint scopes and milestones. When the schedule changes, the lead reviews any missed checkpoint and open risk on the same project before changing its status.
Check the handoff on an actual case
For a customer implementation due at month end, the Delivery Lead records the project and its owner. A sprint scope is due before the final milestone. At the next check, the milestone has been marked missed and a risk remains open. The Delivery Lead sees both against the same project and decides whether to move the project to at risk. The decision stays visible while the team works the recovery plan.
The Project Manager opens the missed milestone against that project and confirms its due date and owner. The Delivery Lead compares the open risk and mitigation with the remaining schedule, then records the project status that matches the delivery plan. Related sprint scopes remain linked to the same project so the team can see which work is affected.
What your team sees
- Active Projects — Projects being delivered, with their owner and dates.
- Milestones At Risk — Missed checkpoints needing an owner response.
Follow the work through
See sprint planning for the planning handoff and review and approval for the decision record. Begin with a small project in implementation, then compare the team’s results with the data model.
What it keeps track of
Data model- Organizations
- Client and internal business organizations that projects are delivered for.
- Projects
- Engagements delivered for an organization, with budget and schedule.
- Milestones
- Dated checkpoints a project must meet.
- Risks
- Project risks with probability, impact, owner and mitigation.
Who uses it
Permissions- Delivery Lead
- Sets the project direction; Project Manager keeps scope and milestones current.
Set up Sprint / Agile Board your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.