Opportunity Assessment Overview April 2008

1. Opportunity Assessment Overview April 2008

2. IT Definition and Delivery Methodology Life Cycle Overview Strategic/Tactical Plans & Priorities Design Plan Project Delivery Phase Define and Deliver IT Project Initiatives Requests for New Services & Features From Units & Faculties Requirements Definition Conceptualization Phase(s) Solution Definition/ Development Business Concept Phase Solution Concept Phase Initial Screening Gate Business Approval Gate Project Approval Gate Initial AssessmentPhase Solution Assurance/ Testing Implement Solution Build Continuous Service & Process Improvement & Sustainment Initial Operations & Support Operate, Support and Maintain IT Services Transition to Production Deliver Review Project Completion Gate Operate 2

3. IT Definition and Delivery Methodology Different Words Strategic/Tactical Plans & Priorities Design Plan Project Delivery Phase Define and Deliver IT Project Initiatives Requests for New Services & Features From Units & Faculties Detailed Requirements May be combined for certain initiatives Design it Determine business value of solving problem Determine solution to the problem Is the idea worth pursuing? Confirm value of proceeding? Approval for project to proceed? Build it/Test it Initial Opportunity Problem ID and Solution Idea Implement it Build Continuous Service & Process Improvement & Sustainment Support It for Initial period Support The Solution Transition to Production Deliver Review Is the Project Done, what Did we Learn? Operate 3

4. Opportunity Assessments Identifying Opportunities • Requests for new products, services or features can originate from the changing needs of a department or faculty • Requests for improvements may be identified through; • Ongoing reviews or usage of service delivery results (improving or changing an existing system), • Learnings from ongoing operations and support (problems identified based on re-occurring issues logged via HD tickets), • Changing expectations for capacity, performance and availability, and sustainment of infrastructure 4

5. Opportunity Assessments What is an Opportunity Assessment? • The creation of an OA is a step in formalizing a request to apply resources and the associated amount of funding to the development of the specified item • An OA is created to define an issue/opportunity and includes a high level assessment of the value of solving the business issue, and an initial sense of the type and complexity of the solution Who can initiate an OA? • Any staff, faculty or contactor on the UofC campus that requires IT resources for the development of a product or service 5

6. Opportunity Assessments Submitting OAs for Assessment • Departments and faculties that are part of BASE partner with IT primes to create and present Opportunity Assessments for review • Department and faculties that are NOT part of BASE should contact the Project Office via the Deliver.IT@ucalgary.ca mailbox to help them: • determine whether or not an OA is required for their request (i.e. small fixes may not require an OA) • understand how the request will progress through the first stages of the methodology 6

7. Opportunity Assessments Documenting Opportunities • The are two ways to capture OA information • Manually populate the OA template, using the current version of the template from the IT Project Office website http://www.ucalgary.ca/pmo • Create a record in the IT Portfolio list stored in the IT Portfolio Management Sharepoint site and generate the document from fields populated in that list *Note: This option is currently available to departments that are part of BASE only *Both options require a record to be created in the IT Portfolio list to enable reporting on all IT requests 7

8. Opportunity Assessment Template 8

9. Opportunity Assessment Template 9

10. Opportunity Assessment Template 10