Projects

A project joins an organization, a named owner, dates, budget and delivery method. The Delivery Lead can use it to distinguish a planned engagement from one already active or at risk. For a product team coordinating a quarterly release, the project can represent the delivery effort while work packages and tasks carry the execution detail. The project record keeps the schedule and hours visible to the person accountable for it.

• One owner. The project owner is a named team member, so a lead can find the person responsible for the overall commitment.
• A dated plan. Start and end dates set a common window for the packages, tasks and milestones beneath the project.
• A delivery method. Fixed Price, Time & Materials and Internal distinguish how the engagement is run; the budget is recorded on the project.

Choose how your team defines a project boundary. A release effort, a client engagement and an internal initiative can all be projects, but the team should use one consistent rule. Decide who can create a project, who owns its status and how often the owner checks its end date. Agree when an Active project becomes at risk, when it moves on hold, and who confirms Completed. These are operating decisions for the Delivery Lead and Project Manager.

Set up organizations and active team members before creating the first project. Confirm that owners have a real weekly capacity and that dates reflect the planned delivery period. If a budget is used, agree whether it is the initial approved amount or the current working amount. The record gives the team one place to read it; the team still needs a clear update owner.

Create an internal project for a release effort, give it an owner and a start and end date, then add a work package and a dated milestone. Assign a task under that package. The project should show its linked work, its hour totals and its milestone count. Open Active Projects and check that the owner can find it. Change the project to at risk when a missed checkpoint needs attention, then use the project link to review the underlying milestone, issue and risk records. A stakeholder conversation should start from those records and their owners.

Before accepting this as a working pattern, rehearse a project that moves from Planned to Active and one that goes on hold. Check who is responsible for the status change and what they use as evidence. Record a review decision separately when an actual delivery subject needs approval; a project status alone is not that decision.

• Active Projects — Delivery leads inspect owned work, status, end dates and progress in one list.
• My Projects — A project owner opens the commitments assigned to them.
• Project Schedule — Managers compare project start and end dates before promising another delivery window.

Start with project planning, then follow delivery control. Agree ownership during implementation.