|
|
|
|
|
|
Adoption Plans can work with Usage Policy as a way to gradually introduce the changes to your business processes.
For example, it might be beneficial to gradually introduce the changes to portfolio reporting by adding more depth to the reports each month. This method helps to assure instant adoption of something simple and long term satisfaction of the overall goals.
Of course, this process is easier to manage with a TeamHeadquarters project.
|
Date |
Requirement |
|
February 15 |
All open & approved projects must be created in TeamHeadquarters with the name provided by the PMO, start date, and planned end date. A Management Report is required, with comments. |
|
March 15 |
All non-approved projects must be created in TeamHeadquarters with status of Pending, planned start/end dates, and a Management Report. This will be required for funding approvals going forward. All open & approved projects must have a fully defined set of financial records for Budget, Costs, Benefit. A Management Report is required with Comments, Accomplishments, Upcoming, Risks, and Issues. |
|
April 15 |
All projects require a work breakdown structure using TeamHeadquarters tasks that are not more than one calendar month in duration. |
|
May 15 |
All projects must comply with the requirements set forth in the Usage Policy. |
