Field experience, c823 task 1

Field experience, c823 task 1

You will design and develop an evidenced-based practice change, quality improvement, or innovation that demonstrates the synthesis of WGU graduate competencies. This project is not primary research but should be focused on scholarly evidence in support of practice improvements, innovation, or general practice change. It will not require an Institutional Review Board (IRB) approval. You will be required to conduct a comprehensive literature review that defines the evidence in support of your project. The literature review represents a collection of primary research studies that have already been conducted and that provide guidance for best practices. Once your project plan is complete, you will create a professional presentation that outlines your plan and then present it to your stakeholder group and preceptor.

Before you start your project, you will first need to secure organizational approval and obtain a letter of agreement from your preceptor. In this task, you will be required to develop a plan for your capstone project that describes your problem and proposed solution.

REQUIREMENTS

Professional Communications is a required aspect to pass this task. Completion of a spell check and grammar check prior to submitting your final work is strongly recommended.

You must use the rubric to direct the creation of your submission because it provides detailed criteria that will be used to evaluate your work. Each requirement below may be evaluated by more than one rubric aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course. 

 

  1.  Submit a completed approval letter from the organization where your project will be conducted using the “Organizational Approval Letter Template,” including the following:
  •  date
  • signature
  • all required information

Note: Forms must be completed in the time specified on the approval letter.

  1.  Submit a legible, signed copy of the “Preceptor Agreement” including the following:
  •  preceptor professional credentials
  • preceptor educational credentials
  • preceptor job title
  • date by preceptor

Note: All “Preceptor Agreements” must be signed by a qualified nurse.

  1. Summarize your project by doing the following:
  2. Identify the clinical or organizational problem.
  3. Describe why the problem you have identified requires a practice change, quality improvement, or innovation, including supporting evidence.

Note: Evidence can be internal, based on clinical expertise, and/or from scholarly literature.

  1. Explain the causes of the problem.
  2. Identify the stakeholders.
  3.  Discuss eachstakeholder’s interest, power, and influence in relation to the project.
  4. Explain the purpose of your project.
  5. Explain your proposed solution for your project.
  6. Provide an evidence summary to support your proposed change.
  7.  Provide a reference list for your evidence summary in APA format that includes a minimum of fivescholarly, peer-reviewed sources that were published within the last five years.

Note: This reference list refers specifically to your evidence summary only.

  1. Explain your proposed implementation plan, which includes the following:
  2. plan of action
  3. timeline
  4. needed resources and personnel
  5. proposed change theory
  6. barriers to implementation
  7. When you use sources, include all in-text citations and references in APA format.

File Restrictions

File name may contain only letters, numbers, spaces, and these symbols: ! - _ . * ' ( )
File size limit: 200 MB
File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z

RUBRIC

A:ORGANIZATIONAL APPROVAL LETTER

NOT EVIDENT

An “Organizational Approval Letter Template” is not provided.

APPROACHING COMPETENCE

The “Organizational Approval Letter Template” is missing one or more of the given requirements.

COMPETENT

The “Organizational Approval Letter Template” is complete and includes each of the given requirements.

B:PRECEPTOR AGREEMENT

NOT EVIDENT

A “Preceptor Agreement” is not provided.

APPROACHING COMPETENCE

The “Preceptor Agreement” is missing one or more of the given requirements.

COMPETENT

The “Preceptor Agreement” is legible and includes each of the given requirements.

C1:CLINICAL/ORGANIZATIONAL PROBLEM

NOT EVIDENT

An identification of a clinical or organizational problem is not provided.

APPROACHING COMPETENCE

A problem is identified, however the problem is not relevant to a clinical or organizational concern.

COMPETENT

An appropriate clinical or organizational problem is identified.

C2:DESCRIPTION OF PROBLEM 

NOT EVIDENT

A description of why the identified problem requires a practice change, quality improvement, or innovation is not provided.

APPROACHING COMPETENCE

The description is not well supported, or the description contains irrelevant details that do not explain why the identified problem requires a practice change, quality improvement, or innovation.

COMPETENT

The description is well supported and appropriately explains why the identified problem requires a practice change, quality improvement, or innovation.

C3:EXPLANATION OF CAUSES

NOT EVIDENT

An explanation is not provided of the causes of the identified problem.

APPROACHING COMPETENCE

The explanation is illogical, or the provided causes do not relate to the identified problem.

COMPETENT

The explanation is logical and appropriately relates the causes to the identified problem.

C4:IDENTIFICATION OF STAKEHOLDERS

NOT EVIDENT

A summary that identifies stakeholders is not provided.

APPROACHING COMPETENCE

The summary does not logically identify stakeholders relevant to the project.

COMPETENT

The summary logically identifies stakeholders relevant to the project.

C4A:DISCUSSION OF STAKEHOLDERS 

NOT EVIDENT

An appropriate discussion of stakeholder interest, power, and influence in relation to the project is not provided.

APPROACHING COMPETENCE

The discussion does not appropriately provide each stakeholder’s interest, power, and influence in relation to the project.

COMPETENT

The discussion is logical and appropriately relates each stakeholder’s interest, power, and influence in relation to the project.

D:EXPLANATION OF PROJECT

NOT EVIDENT

An explanation of the project is not provided.

APPROACHING COMPETENCE

The explanation of the project is illogical or does not relate to the identified problem.

COMPETENT

The explanation of the project is logical and appropriately related to the identified problem.

E:PROPOSED SOLUTION

NOT EVIDENT

An explanation of the proposed solution is not provided.

APPROACHING COMPETENCE

The explanation of the proposed solution is illogical or does not relate to the identified problem.

COMPETENT

The explanation of the proposed solution is logical and appropriately related to the identified problem.

F:EVIDENCE SUMMARY

NOT EVIDENT

An evidence summary is not provided.

APPROACHING COMPETENCE

An evidence summary is provided, but it contains numerous technical flaws or does not support the proposed change or solution.

COMPETENT

An appropriate evidence summary is provided that supports the proposed change or solution.

F1:REFERENCE LIST

NOT EVIDENT

A reference list for the evidence summary with at least 5 scholarly, peer-reviewed sources that were published within the last five years is not provided.

APPROACHING COMPETENCE

A reference list for the evidence summary is provided with at least 5 scholarly, peer-reviewed sources that were published within the last five years, but the list is in a format other than APA.

COMPETENT

An appropriate reference list for the evidence summary is provided in APA format with at least 5 scholarly, peer-reviewed sources that were published within the last five years.

G1:PLAN OF ACTION

NOT EVIDENT

An explanation of the plan of action is not included in the proposed implementation plan.

APPROACHING COMPETENCE

An explanation of the plan of action is included in the proposed implementation plan, but the explanation does not cover all necessary components related to the project.

COMPETENT

A reasonable explanation of the plan of action that covers all necessary components related to the project is included in the proposed implementation plan.

G2:TIMELINE

NOT EVIDENT

An explanation of the timeline is not included in the proposed implementation plan.

APPROACHING COMPETENCE

An explanation of the timeline is included in the proposed implementation plan, but the explanation is not logical given the information provided about the project.

COMPETENT

An explanation of the timeline is included in the proposed implementation plan. The timeline is logical given the information provided about the project.

G3:RESOURCES AND PERSONNEL

NOT EVIDENT

An explanation of the needed resources and personnel is not included in the proposed implementation plan, or the information provided does not pertain to the project.

APPROACHING COMPETENCE

An explanation of the needed resources and personnel is included in the proposed implementation plan, but the explanation is not reasonable given the information provided about the project.

COMPETENT

An explanation of the needed resources and personnel is included in the proposed implementation plan. The explanation is reasonable given the information provided about the project.

G4:PROPOSED CHANGE THEORY

NOT EVIDENT

An explanation of the proposed change theory is not included in the implementation plan.

APPROACHING COMPETENCE

An explanation of the proposed change theory is included in the implementation plan, but the proposed change theory is not reasonable given the information provided about the project.

COMPETENT

An explanation of the proposed change theory is included in the implementation plan. The explanation is reasonable given the information provided about the project.

G5:BARRIERS TO IMPLEMENTATION

NOT EVIDENT

An explanation of the barriers to implementation is not included in the proposed implementation plan.

APPROACHING COMPETENCE

An explanation of the barriers to implementation is included in the proposed implementation plan, but the explanation is not reasonable given the information provided about the project.

COMPETENT

An explanation of the barriers to implementation is included in the proposed implementation plan. The explanation is reasonable given the information provided about the project.

H: APA SOURCES

NOT EVIDENT

The submission does not include in-text citations and references according to APA style for content that is quoted, paraphrased, or summarized.

APPROACHING COMPETENCE

The submission includes in-text citations and references for content that is quoted, paraphrased, or summarized but does not demonstrate a consistent application of APA style.

COMPETENT

The submission includes in-text citations and references for content that is quoted, paraphrased, or summarized and demonstrates a consistent application of APA style.

PROFESSIONAL COMMUNICATION:

NOT EVIDENT

Content is unstructured, is disjointed, or contains pervasive errors in mechanics, usage, or grammar. Vocabulary or tone is unprofessional or distracts from the topic.

APPROACHING COMPETENCE

Content is poorly organized, is difficult to follow, or contains errors in mechanics, usage, or grammar that cause confusion. Terminology is misused or ineffective.

COMPETENT

Content reflects attention to detail, is organized, and focuses on the main ideas as prescribed in the task or chosen by the candidate. Terminology is pertinent, is used correctly, and effectively conveys the intended meaning. Mechanics, usage, and grammar promote accurate interpretation and understanding.