NURS 6441: Project Management: Healthcare Information Technology | Week 6

An unsuccessful project fails in the beginning—not at the end.

—Brian Gugerty, DNS‚ RN

All successful projects employ a set of steps or guidelines that direct the project and the work of the team. The project manager generally establishes those steps and uses them to identify the project scope, establish priorities, create a work breakdown, and integrate the breakdown within the organization. These steps help the project to be self-sustaining, and are vital to successfully managing a project.

The work breakdown structure (WBS) is a critical part of project management. The WBS helps define the scope of the project and guides the efforts of those involved.

This week you examine the process of defining steps used to manage a project. You also investigate how to identify the scope of a project, manage and establish priorities, and develop a WBS.

Learning Objectives – Discussion: Work Breakdown Structure NURS6441

Students will:

• Analyze work breakdown structure formats
• Evaluate work breakdown structures for task clarity
• Produce a work breakdown structure for a health information technology project*

*The Assignment related to this Learning Objective is introduced this week and submitted in Week 7.

Learning Resources

Note: To access this week’s required library resources, please click on the link to the Course Readings List, found in the Course Materials section of your Syllabus.

Required Readings

Biafore, B. (2010). Microsoft Project 2010: The missing manual. Sebastopol, CA: O’Reilly.

• Chapter 4, “Breaking Work Into Task-Sized Chunks” (pp. 77–100)This chapter explains how to create a work breakdown structure and how to import a work breakdown structure into Microsoft Project.

Coplan, S., & Masuda, D. (2011). Project management for healthcare information technology. New York, NY: McGraw-Hill.

• Chapter 3, “Project Management”
  • • “Prepare Work Breakdown Structure and WBS Dictionary” (pp. 53–56)

  This section of Chapter 3 reviews the core processes of preparing a work breakdown structure (WBS). The chapter provides an example of a WBS and details its essential components.

Project Management Institute. (2017). A guide to the project management body of knowledge (PMBOK® guide) (6th ed.). Newtown Square, PA: Author.

• Chapter 5, “Project Scope Management”
  • • 5.4, “Create WBS”

  This section of Chapter 5 reviews the process of creating a work breakdown structure. Specifically, the chapter examines how to determine inputs, WBS tools and techniques, and outputs.

Kendrick, T. (2009). Identifying & managing project risk: Essential tools for failure-proofing your project(2nd ed., Ebrary version). New York, NY: AMACOM.

• Chapter 3, “Identifying Project Scope Risk” (pp. 40–69)This chapter examines methods of identifying scope risks and the types of scope risks pertaining to project deliverables. The chapter highlights a variety of sources of scope risk as well.

Shirey, M. R. (2008). Project management tools for leaders and entrepreneurs. Clinical Nurse Specialist, 22(3), 129–131.

The author of this article introduces project management tools that clinical nurse specialists may use to coordinate team work. The article highlights the usage of one such tool, the Gantt chart.

Thomas, M., Jacques, P. H., Adams, J. R., & Kihneman-Wooten, J. (2008). Developing an effective project: Planning and team building combined. Project Management Journal, 39(4), 105–113.

This article analyzes project planning and control and the process of developing a project plan. The article also reports the results of research that sought to determine 137 organizations’ approaches to establishing projects.

U.S. Government Accountability Office. (2009, March 2). Work breakdown structure. GAO Reports, 65–78.

This article examines the importance of a work breakdown structure (WBS) in project management. The chapter demonstrates how a WBS assists in resource identification, cost estimation, and risk determination.

Wu, Z., Schmidt, L. P., & Wigstrom, M. S. (2010). Product development workflow management based on work breakdown structure. IIE Annual Conference. Proceedings, 1–5.

The authors of this article highlight the usage of WBS in managing complex product development projects. The authors examine how a WBS helps represent and manage the intricacies of tasks and activity relationships.

Mathis, M. (n.d.). Work breakdown structure: Purpose, process and pitfalls. Retrieved March 13, 2013, from http://www.projectsmart.co.uk/work-breakdown-structure-purpose-process-pitfalls.html

This article provides a general review of the WBS. The author focuses on the purpose, process, and pitfalls of a WBS.

Document: Team Project Scenario (PDF)

This document contains the scenario your team will use for Team Project.

Document: Work Breakdown Structure Formats (PDF)

This document presents a scenario and three corresponding work breakdown structures that you will use for your Discussion this week.

Required Media

Laureate Education (Producer). (2013c). Planning, part I: Defining project scope and activities [Video file]. Retrieved from https://class.waldenu.edu

Note: The approximate length of this media piece is 6 minutes.

In this presentation, the participants discuss defining project scope and project activities, using the work breakdown structure, and managing project risk through SWOT analysis.

Discussion: Work Breakdown Structure

Within reason, is there such a thing as a project that is too complex to complete? Consider the Space Shuttle. One of the most complex machines ever built, the Space Shuttle had over 2.5 million parts, each of which had to be accounted for by someone. How did anyone manage to track and properly assemble these parts? The answer is through the application of a work breakdown structure (WBS). A WBS is a fundamental tool that project managers use to organize and divide the work of a project. A WBS focuses on breaking down a project’s scope into individual deliverables that may be created by assigned team members.

There are multiple work breakdown structure formats and each has its own advantages and disadvantages. Project managers select a type of WBS based upon the specifics of the project they are managing. Each WBS format emphasizes different aspects of a project. These varied perspectives may each be appropriate, depending upon what information a project manager needs.

In this Discussion, you analyze different WBS formats and evaluate whether they meet basic criteria for clarity.

To prepare for Discussion: Work Breakdown Structure NURS6441:

• Explore the Work Breakdown Structure Formats document included in this week’s Learning Resources. The document presents a scenario and three corresponding WBS formats that pertain to the scenario.
• Consider the advantages and disadvantages of each WBS format included in the document.
• Think about the level of detail dedicated to task information in each WBS format. Evaluate the formats based on the following criteria for clarity:
  • The task has a measurable status or completion.
  • The task has defined start and end events.
  • The task has a deliverable.
  • The task’s time and cost are easily estimated.
  • The task can be completed without interruption and additional input after its start.

By Day 3

Post an analysis of the advantages and disadvantages of each work breakdown structure format. Provide an analysis of whether (and how) the work breakdown structures meet the assigned criteria for clarity. Provide rationale for your response.

By Day 6

Respond to at least two of your colleagues on two different days, using one or more of the following approaches:

• Ask a probing question, substantiated with additional background information, evidence, or research.
• Share an insight from having read your colleagues’ postings, synthesizing the information to provide new perspectives.
• Offer and support an alternative perspective, using readings from the classroom or from your own research in the Walden Library. Discussion: Work Breakdown Structure NURS6441.

ADDITIONAL INFORMATION;

Discuss structure for a health information technology

Introduction

The health information technology (HIT) field is complex, and it can be difficult to grasp all of its components. However, by understanding the structure of an organization and its key players, you can make better decisions about where your organization fits into this ecosystem.

A review of the literature.

A review of the literature is a good way to start your health information technology project. It should include a summary of:

• The current state of health information technology (HIT).

• Related work that has been done in this area, but not as directly relevant to you.

The rationale for your project, and how it fits into the current state of health information technology. You should also include a detailed timeline, including milestones and deliverables.

Business strategy.

Your business strategy should be clear to all stakeholders. It should also be flexible, but not too flexible. A good strategy is one that aligns with your company’s overall business strategy, and it should also align with the company’s core values.

A good strategy is one that aligns with your company’s overall business strategy, and it should also align with the company’s core values. A good strategy will help you achieve what you want to achieve as a company, but it should also be flexible enough so that if things change along the way, you can adjust accordingly.

Data management.

Data management is the process of keeping track of and using data. The two main areas of data management are:

• Data storage and retrieval

• Data security, integrity and validation

Data management is an important part of any business operation, but it’s especially critical when you’re dealing with large amounts of data. Data storage and retrieval are two main areas that every company needs to consider when looking at their data management strategy.

Disaster recovery plan.

A disaster recovery plan is the best way to ensure that your organization can continue to operate in the event of a disaster. It should include:

• Details about the location of backup data. This includes where it’s stored, how accessible it is (networked or not) and who has access to it, along with any other information needed to restore operations after an incident.

• Details about the location of backup hardware. If there are multiple locations for backups, this section should describe each one clearly so that employees know where their data will be when they come back online after an outage or crisis situation occurs – whether due to natural disasters like hurricanes or tornadoes; cyberattacks; power outages; etc… This information applies only if there are multiple potential locations available within your facility/office space(s).

Governance structure.

Governance is the management of a company or organization. Governance structures are designed to ensure that the goals and objectives of an organization are met, including providing guidance on how to achieve those goals. The governance structure can be broken down into three main components:

• A board of directors (or equivalent) who serve as leaders in decision making and oversight of operations

• An executive team responsible for managing day-to-day operations and providing strategic direction from above

Legal considerations.

Legal considerations are the most important aspect of health information technology. Health IT is not a panacea for all problems; it cannot solve every problem that affects the healthcare industry or its patients. But, if you think about what an effective solution would look like, you will see how much money can be saved through better use of technology and how many lives could be saved by making sure that all data is protected from unauthorized access or manipulation.

There are many legal factors involved in creating a successful program:

• Security. The best approach to security is prevention—avoiding security breaches rather than trying to fix them after they occur (which costs money). Make sure that your system’s data is housed on secure servers with strong encryption protection against cyberattacks; keep detailed records of who has accessed each file; create an audit trail showing exactly where each piece of information resides at any given time so there won’t be any confusion later when trying to prove whether something happened accidentally or intentionally; make sure everyone knows what they’re doing before entering sensitive data into their programs so they don’t accidentally delete anything important while working around your office cubicle walls instead!

Conclusion

Health information technology is a great way to improve the efficiency of your organization, but it can be difficult to implement. That’s why it’s important to structure your project correctly from the start so that you can focus on making sure everything runs smoothly once it goes live. We hope this guide has helped give you some guidance as how best go about structuring your own health information technology project!