Patient Management

Patient Management

Project Proposal

Cohort A

Group 1

The version number starts at one and increases by one for each release. It shows the release number and a revision letter if in draft. The original draft is 0.A and subsequent drafts are 0.B, 0.C etc. The first accepted and issued document is 1.0. Subsequent changes in draft form are 1.0A, 1.0B etc. The accepted and issued second version is 1.1 or 2.0, depending on the magnitude of the change.

Student names

Team leader

Member 2

Member 3

Member 4

Member 5

Document Acceptance and Release Notice

This document is authorised for release once all signatures have been obtained.

PREPARED: Date: / / (for acceptance) <Name>

< Position>, <Business Unit> ACCEPTED: Date: / / (for release) <Name>

<Position>, <Business Unit> Table of Contents

TOC h z t "Heading 1,1,Heading 2,2,Heading 3,3" List of Tables PAGEREF _Toc77667242 h 4List of Figures PAGEREF _Toc77667243 h 51.Project Summary PAGEREF _Toc77667244 h 71.1Purpose PAGEREF _Toc77667245 h 71.2Business and Policy Context PAGEREF _Toc77667246 h 71.3Working Title for the Proposed Project PAGEREF _Toc77667247 h 71.4Objective(s) PAGEREF _Toc77667248 h 81.5Project Complexity PAGEREF _Toc77667249 h 81.6Potential Benefits PAGEREF _Toc77667250 h 81.7Feasibility Statement PAGEREF _Toc77667251 h 81.8Recommendation PAGEREF _Toc77667252 h 82.Business Assessment PAGEREF _Toc77667253 h 82.1Situation Assessment and Problem Statement PAGEREF _Toc77667254 h 82.2Options considered PAGEREF _Toc77667255 h 92.3Consultation PAGEREF _Toc77667256 h 93.Proposed Scope PAGEREF _Toc77667257 h 103.1Scope Definition PAGEREF _Toc77667258 h 103.2Assumptions PAGEREF _Toc77667259 h 103.3Constraints PAGEREF _Toc77667260 h 103.4Scope of Work PAGEREF _Toc77667261 h 103.5Implementation Strategy PAGEREF _Toc77667262 h 114.Project Management Outline PAGEREF _Toc77667263 h 124.1Governance PAGEREF _Toc77667264 h 124.2Key Risks and Issues PAGEREF _Toc77667265 h 125.References PAGEREF _Toc77667266 h 12

List of Tables TOC h z c "Table 3." Table 3. 1 Title. PAGEREF _Toc77666968 h 9Table 3. 2 Initial project plan. PAGEREF _Toc77666969 h 10

List of Figures TOC h z c "Figure 1." Figure 1. 1 WWII Aircraft fighter. PAGEREF _Toc77667193 h 7

TOC h z c "Table"

Project SummaryPurposeProvide a statement about the purpose of this document. For example:to obtain feedback and/or to secure a decision to proceed with the proposed project CITATION Ngu21 l 3081 [1].

The purpose of this document is <enter details>.

Business and Policy ContextSummarise any relevant background information by briefly describing the overall concepts for change and their place in the big picture (strategic and/or corporate directions), relevant policy/strategic commitments CITATION Rah21 l 3081 [2].

Figure 1. SEQ Figure_1. * ARABIC 1 WWII Aircraft fighter.Include a brief description of the business problem and the nature of any potential solutions to address the business problem (if known).

Additional information may be included as Appendices CITATION Set11 l 3081 [3].

Working Title for the Proposed ProjectThe working title is an interim title. It may change once the project is approved. Include both the abbreviation and long title.

The working title for the project is the <Project Title> Project.

Objective(s)An objective is a high level description or statement of the overarching rationale for why the project is being conducted, and should be directly related to the Corporate Objectives and the business driver(s) for the project. It focuses on what the project is going to achieve, rather than what is produced. A project can have one or more objectives, which do not need to be measurable. Each should be listed as a single sentence.

The objective of the <Project Title> Project is to <enter detail>

Project ComplexityProvide a statement as to the expected complexity of the proposed project as well as an outline of how you have made this assessment. This information provides stakeholders/senior management with the opportunity to discuss and agree the complexity of the project. If it is decided the project is complex, a fully documented Business Case may be required.

For further information refer to the Project Management Fact Sheet: Project Sizing at www.egovernment.tas.gov.au.

Potential BenefitsOutline any perceived benefits to the business from undertaking the project. These will be longer-term and the project must also identify measurable outcomes as part of the proposed scope.

Feasibility StatementThis section should make a statement about the feasibility of the proposed project, eg does the organisation have capacity and capability to deliver the project.

RecommendationThis section should provide a recommendation on whether or not the project should proceed.

Business AssessmentSituation Assessment and Problem StatementThis section should clearly establish the benefit to the organisation of proceeding with the proposed project. It should contain:

a description of the relevant environmental conditions;

an assessment of how the business needs are currently being met or not met;

an analysis of the gap between the current situation and the stated objective(s).

Options consideredList the options that you have considered to date. Some options that may need to be identified and analysed are:

Option 1- Do nothing

Option 2 - An option that would achieve the same result as the preferred option

Option 3 - The preferred option

ConsultationProvide a summary of any consultation with stakeholders undertaken to date and their respective levels of support for the concept. Initial negative support may indicate increased risk for the proposed project.

Proposed ScopeBased on the information outlined in Section 2 for the preferred option, begin to scope the project that will implement the recommended option and describe how the project will be managed. The information in the following sub-sections are important, as they will form the basis of a Project Business Plan if the project/initiative proceeds.

Scope DefinitionOutline the broad scope of the proposed project, including any assumptions or constraints that may be relevant.

Table 3. SEQ Table_3. * ARABIC 1 Title.Element Detail

Objective Outcome You may not be able to identify and specify target outcomes for the proposed project at this point. The broad business outcomes should be specified as a minimum.

Output Outputs are the products, services, business or management practices that will be required (produced) to meet the identified outcomes.

Quality Criteria What criteria will be used to judge whether outputs are fit-for-purpose

Customer(s) The person or entities that will utilise the project outputs to generate the outcomes

AssumptionsIt is essential that assumptions made during the planning process are recognised and recorded, for example resource availability, environment, technology, security etc. [1]

The main assumptions are:

ConstraintsConstraints are known limitations within which the project must work, for example deadlines, finance and budget, legislation etc.

The main constraints are:

Scope of WorkThe scope of work is defined as the processes that are required to produce the project outputs.

Identifies all of the project work that clearly falls within the scope of the project, that which is outside the scope, and any work that requires further consideration.

Implementation StrategyBriefly outline the time and resources (both human and financial) that are required to undertake the work to produce the outputs.

The estimated resources that will be required to implement the proposed project are detailed in table <n> below.

Table 3. SEQ Table_3. * ARABIC 2 Initial project plan.Element Detail Issues

Project Schedule Outline the expected timeframe for delivery of the project. For example: The project is expected to commence on <dd/mm/yy> and be completed by <dd/mm/yy> List any issues or notes that may be relevant to the scheduling, for example, where estimations have been used. You may also wish to identify any allowances or tolerances (the % of change in schedule that the project manager may accept without reference to the Steering Committee)

Budget Estimate Outline the expected budget for the project including estimates of any ongoing costs of supporting the project outputs as they are often overlooked. List any issues or notes that may be relevant to the budget, for example, where estimations have been used. You may also wish to identify any allowances or costing sensitivities relevant to the budget estimate. For example, the cost of materials.

Other Resources List other resourcing requirements, for example accommodation, IT equipment and information requirements. List any issues or notes that may be relevant to the resources, for example, where estimations have been used

Project Management OutlineGovernanceList the parties who will form the governance structure for the project if approved.

As a minimum you will need in your governance structure a:

Project Sponsor

Business Owner

Project Manager

As the project evolves, assuming it is approved, you may add one or more of the following parties in your governance structure:

Project Team

Quality Manager

Key Risks and Issues List any major risks or issues identified through consultation. Keep in mind that assumptions, constraints and issues related to project schedule, budget estimate and resources identified in this proposal may also need to be considered as issues and risks to the project.

These major risks or issues will be investigated further should the project proceed:

References BIBLIOGRAPHY

[1] N. Vo, VIT, IEEE, pp. 15-29, 2021.

[2] R. Thakur, AI in assessment, AI, vol. 4, no. 9, pp. 1-10, 2021.

[3] B. T. G. Seth D.Bauma, How long until human-level AI? Results from an expert assessment, ELSEVIER, vol. 78, no. 1, pp. 185-185, Jan 2011.

Marking Guide:

Criteria (used as a guide only) Exceeds

Expectations

(100% - 80%) Meets

Expectations

(80% -70%) Approaches

Expectations

(70% - 50%) Does Not Meet

Expectations

(50%- 0%)

Proposal Sections

Project Summary Benefits Feasibility Business Assessment Proposed Scope Project Management Outline Other Evaluation

Connectedness between sections Cohesion of presentation within sections Completeness Evidence of critical appraisal of the project Evidence of deep understanding of the project Grammar

Spelling is satisfactory Grammatical expression is satisfactory