Scribd
Upload
3 views

Assignment 3 - Individual Assignment Template (1)

The document outlines a project proposal focused on addressing falls in the geriatric ward 7B at Tan Tock Seng Hospital. It details the project's background, objectives, justification, scope, metrics for success, and phases of implementation including diagnostic and impact assessments. The proposal emphasizes the importance of stakeholder engagement and the need for a structured approach to improve patient safety and care outcomes.

Uploaded by

jane.grace19
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3 views

Assignment 3 - Individual Assignment Template (1)

The document outlines a project proposal focused on addressing falls in the geriatric ward 7B at Tan Tock Seng Hospital. It details the project's background, objectives, justification, scope, metrics for success, and phases of implementation including diagnostic and impact assessments. The proposal emphasizes the importance of stakeholder engagement and the need for a structured approach to improve patient safety and care outcomes.

Uploaded by

jane.grace19
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Topic of interest is Fall in geriatric ward 7B in Tan Tock Seng hospital

Executive Summary
Please summarize your report here
About 300 to 500 words

Introduction

Method

Results

Discussion:

Project Leader Date:

Stage 1 – Project Phase (Project Charter)


Background
The “Background” section is written at the start of the project proposal which
includes:
Background of the project
Reason for undertaking the project (e.g., what problem it seeks to address)
A history and context of the problem
A concise summary of your project's information
Problem statement
A problem statement is a few sentences (within 2-3 sentences) that identifies and
summarizes a condition, problem, or issue that a project team is seeking to
address.
Typically included in a Project Charter, a problem statement provides a quality
improvement team with an articulate expression of what they are setting out to
achieve.

Project Objectives - What are you trying to accomplish (Your aim


statement)?
This is your improvement project in a ‘nut-shell’: a single sentence that states what
you intend to accomplish. Outline how much improvement is to be achieved, when
you expect to achieve this by and with who/where.

Be realistic here. Your aspirations should be balanced by some idea of how you
can get there (your initial ideas for change which will be listed below).

Use the SMART criteria

Project Justification
Why is this important (the rationale and business case for your improvement
project)?
 What problem will the work address and what is the impact of doing nothing?
 How do you know this is a problem and what is your starting position?
 How big a gap is there between where you are and where you want to be?
 How does your aim fit into the strategic vision of your organisation?
 What is the expected impact (outcomes, benefits, cost)?
 Why do you believe the timescale you have set is realistic?
Project Scope - What is the scope of your project?
 Who, specifically, will be affected by the success or failure of this project
(children impacted by your services, staff, patients, community, etc)?
 How many people/how large an area is included in your project?
 Are there any processes/areas of work associated with the problem that won’t
be included in your project?

Project Metrics or Outcomes


How will you know that a change is an improvement?
What measures will you use to help you monitor progress toward your goal? These
should include:
 Outcome - how you will track the progress of your improvement aim
 Process - how you will know how the parts of the system you are trying to
change (to get you to your improvement aim) are performing and the impact of
your changes on these.
 Balancing – areas you need to keep watch in case your action has a
unintended impact on other parts of the system or to see if something unrelated
to your project is influencing project success.

What may risk the success of your project?


List any risks associated with your project and any action you have planned to
monitor or manage these.

Project Schedule
- Using a Gantt Chart here.
Resources for project
 Labour: They constitute team members or employees and contingent staff
with different skill sets and form the backbone of any project.
 Equipment/Tools: It includes everything from software to hardware,
depending on the organization’s type.
 Facilities: It comprises the environment needed for executing a project, such
as a conference room or office space.
 Materials: These are the consumables required to generate outputs. For
example, office stationery, raw materials to build a house.
 Budget: Finance needed to purchase any of the above resources.

Participation (Team membership) and Leadership support


Who is in your improvement team? People to consider:
 subject matter expert
 process owners who can make changes
 representatives of those impacted by your project: families, young people,
patients, customers etc.
 finance representative, if needed
 a sponsor with links to executive level for leadership support

Stakeholder Analysis
1. Determine who your stakeholders are using Brainstorming.
2. Group and prioritize these stakeholders using the Power-Interest Grid.
3. Figure out how to communicate with and win buy-in from each type of
stakeholder.
a. What motivates this stakeholder?
b. What other priorities do they have, and how can we align our project with
those priorities (or at least ensure the project won’t threaten them)?
c. Will this stakeholder likely have a positive view of our project? If not,
what can we do about it?
Stage 2 – Diagnostic Phase

Current state – Map existing practices, process, or product


Identify the area for improvement by reviewing the existing practice, process,
policies, or product and outline its current state.

Collect and measure baseline data


 Measurement Name: What are the baseline data that you need to collect and
how would you call it?
 Data Type: Is the data qualitative or quantitative (discrete or continuous)?
 Source / Instrument: What is the source or instrument that you will use to
collect the baseline data?
 Duration: How long will you be collecting the data?
 Who and How: Who is responsible and what method will they use?
 Analysis: How you will you present and interpret the data?

Gaps or Root Cause Analysis


Identify the gaps and possible root causes.
Use the 5 Whys, Ishikawa diagram etc.

Prioritize the gaps for action implementation

Insert the Pareto chart or Decision matrix.


Stage 3 – Implementation Phase
Summary of Proposed solutions – What changes can you make that will lead
to improvement?
 Plan – Generate, evaluate, and plan the possible solutions to be tested.
 Generate possible solutions and decide which solutions are worth
implementing.
 State the question you want to answer and make a prediction about what you
think will happen.
 Develop a plan to test the change. (Who? What? When? Where?)
 Identify what data you will need to collect.
Identify the method used for solution generation:
 Brainstorming
 Literature review
 Benchmarking
 Affinity diagram

PDSA Cycle 1: Present the plan for PDSA Cycle 1


Refer to PDSA Worksheet to structure your report for PDSA Cycle.

Instructions
Plan: Plan the test, including a plan for collecting data.
•State the question you want to answer and make prediction about what you think
will happen.
•Develop a plan to test the change. (Who? What? When? Where?)
•Identify what data you will need to collect.
Do: Run the test on a small scale.
•Carry out the test.
•Document problems and unexpected observations.
•Collect and begin to analyse the data.
Study: Analyse the results and compare them to your predictions.
•Complete, as a team, if possible, your analysis of the data.
•Compare the data to your prediction.
•Summarize and reflect on what you learned.
Act: Based on what you learned from the test, make a plan for your next step.
•Adapt (make modifications and run another test), adopt (test the change on a
larger scale), or abandon (don’t do another test on this change idea).
•Prepare a plan for the next PDSA.

PDSA Cycle 2: Present the plan for PDSA Cycle 1


Refer to PDSA Worksheet to structure your report for PDSA Cycle.

Instructions
Plan: Plan the test, including a plan for collecting data.
•State the question you want to answer and make prediction about what you think
will happen.
•Develop a plan to test the change. (Who? What? When? Where?)
•Identify what data you will need to collect.
Do: Run the test on a small scale.
•Carry out the test.
•Document problems and unexpected observations.
•Collect and begin to analyse the data.
Study: Analyse the results and compare them to your predictions.
•Complete, as a team, if possible, your analysis of the data.
•Compare the data to your prediction.
•Summarize and reflect on what you learned.
Act: Based on what you learned from the test, make a plan for your next step.
•Adapt (make modifications and run another test), adopt (test the change on a
larger scale), or abandon (don’t do another test on this change idea).
•Prepare a plan for the next PDSA.
Stage 4 – Impact Phase
Measure and validate the project outcomes, including financial ones.
Teams should measure the impact of changes they have made in order to be sure
the intervention has resulted in an improvement, and to provide the evidence
required to justify permanent implementation of these changes.
A popular way of displaying data is an annotated run chart.

Document lessons learnt.


Use the Gibb’s reflective cycle
Stage 5 – Sustaining Improvement Phase
Action plan for transition to process owner or full-scale implementation
within the institutions
Can use the following:
1. Lewin's 3-stage model of change (unfreezing, moving, and refreezing)
2. Roger’s diffusion model (knowledge, persuasion, decision, implementation, and
confirmation)

Sharing of project outcomes with key stakeholders and project closure

Use a A3 diagram etc.


 Background
 Problem statement and objectives
 Current and future condition
 Cause analysis
 Implementation plan (PDSA cycles)
 Follow-up (project impact, lessons learned, and sustaining changes)

Final Word Count: +/-4800 words (including summary page, diagrams, figures and
references)

References

Appendices

You might also like