|
Framework Element
|
Yes
|
No
|
Comment/Explanation
|
|
1. Principle: Information technology projects are aligned with, and
support, business directions and priorities
|
| 1.1. Is the project consistent and compatible
with the department's mission, goals and priorities as described in the
annual Business Plan? |
|
|
|
| 1.2. Is the project consistent and compatible
with ongoing or planned re-engineering initiatives designed to change
fundamental business processes? |
|
|
|
| 1.3. Is the project consistent with the
department's Long Term Capital Plan? |
|
|
|
| 1.4. Is the project consistent with the
department's Information Management Plan? |
|
|
|
| 1.5. Is the project consistent and compatible
with the department's information and technology direction, strategies,
architectures and infrastructures? |
|
|
|
| 1.6. Is the project consistent and compatible
with government-wide strategies for the delivery of services as
described in the TBS Blueprint for Renewing Government Services Using
Information Technology? |
|
|
|
| 1.7. Does the project conform with approved
common information technology standards, infrastructures and
architectures , e.g. the public key infrastructure and infrastructure
elements provided by the Government Technology and Information Service? |
|
|
|
| 1.8. Is approval for the project based on a
business-case analysis that relates the investment directly to the
business function and demonstrates the benefits of the investment to the
department or government as a whole? |
|
|
|
| 1.9. Is the business case based on the full
cost of the system from initiation through development, implementation
and the estimated annual cost of operation? |
|
|
|
| 1.10. Will the business case be reviewed and
revalidated at each scheduled gate and whenever there is a significant
change to the project or the business function? |
|
|
|
| 1.11. If the business-case changes, does the
project need to be re-approved by the department? |
|
|
|
| 1.12. Has the project manager ensured that
all types of clients are represented in the project so that each client
group can influence requirements definition, system design and
implementation? |
|
|
|
| 1.13. Have clients been given a clear picture
of what the system will do for them and how it will interact with them
while there is opportunity to recommend improvements? |
|
|
|
| 1.14. Will clients formally sign off on the
reviews at the project's gates and be involved in decisions on the
project's future? |
|
|
|
| 1.15. Has the project leader ensured that
representatives of client groups have formally committed to the level of
effort required to meet their defined responsibilities? |
|
|
|
| 1.16. Have client names and explicit
responsibilities have been included in the project charter? |
|
|
|
| 1.17. Are clients seen as full team members
who take part in all requirements definition, design and implementation
decisions of the project, rather than as people to bounce ideas off or
to "approve" decisions of the project team? |
|
|
|
| 1.18. Are clients are involved in the
decision to release funds and continue the project at project gate
reviews? |
|
|
|
