Software delivery teams

How Change Request Management is set up for you

Software delivery teams often receive change requests after a project plan has been agreed. A work package gives the request a subject, owner, budget hours and due date. The impact assessment explains the added effort and dollar cost effect; tasks carry the actual work. A reviewer can examine the package revision and evidence before the Delivery Lead records an accepted outcome.

Start with one active project and one proposed change to a reporting screen. The Project Manager creates the package and confirms the organization link. The Business Analyst estimates added hours and writes the assumption behind the cost delta. Contributors plan and carry the tasks. Before Review, the Project Manager compares the task plan with the estimate and checks the attachment titles.

Ask the Independent Reviewer to Return the first submission for a specific missing check. Update the task and attachment, advance the package revision and submit it again. This rehearsal makes the revision rule concrete. An earlier Return remains useful history; an Approve decision on the revised package can then support acceptance.

Use the Task Board by Status for delivery and Packages awaiting review for the human decision. The two screens answer different questions. A task marked Done says the work line is complete; it does not make the package Accepted.