Running Head: Final Project 1
Medical Informatics Wellness Project
Plan Dr.
IT-625
Date
, Running Head: Final Project 2
Table of Contents
I. Conflict Resolution Plan......................................................................................................................................5
A. Team Dynamics Overview.................................................................................................................................5
B. Conflict Resolution Leadership........................................................................................................................10
C. Motivation and Confidence..............................................................................................................................11
II. Project Status Evaluation..................................................................................................................................12
A. Status Evaluation.............................................................................................................................................12
B. Project Analysis...............................................................................................................................................12
C. Forecasting.......................................................................................................................................................14
D. Impact of the past.............................................................................................................................................19
E. Corrective Actions...........................................................................................................................................19
III. Project Charter..............................................................................................................................................21
A. Project Objectives............................................................................................................................................21
B. Project Strategy................................................................................................................................................21
C. Project Communication Plan...........................................................................................................................24
IV. Project Planning and Controls......................................................................................................................38
A. Project Scope Planning....................................................................................................................................38
B. Project Scheduling Planning............................................................................................................................41
C. Project Cost Planning and Control...................................................................................................................43
D. Risk Management Plan....................................................................................................................................47
E. Risk Control.....................................................................................................................................................48
F. Project Quality Planning..................................................................................................................................51
V. Project Approvals...............................................................................................................................................55
,Running Head: Final Project 3
I CONFLICT RESOLUTION PLAN
Most project will experience some sort of conflict as a result of difference in values,
behaviors, interest, attitude to work, resource and personalities. The purpose of conflict
resolution is to ensure a sound resolution to these differences to help improve performance or
keep a project on track to it objectives which may include time, cost and customer requirements.
A.) Team Dynamics Overview
1. Roles and Titles:
According to the case study provided, medical informatics is working on creating a new
product (clinical data warehouse software package), the key success factor of the product is (time
to market and quality) and the scope of the project which is to create a modular software package
to handle wellness vendor data appears to have been well-defined. Though a team of 10 people, a
plan has been put in place, but it falls short on clear details on how to achieve the tasks/goals
necessary to accomplish the project hence the delays and conflicts being experienced.
NAME TITLE ROLE REPORT
1 Sue Barret Sponsor Overall accountability of Project NIL
2 Brant Business Owner User requirements Relates with
Amero Sponsor
3 Waltraud Information Decides on workplace device Relates with
Tatem Systems Manager upgrades, maintenance and sponsor (Sue).
installations
4 William Chief Information In charge of IT and computer Relates with
McConnell Officer systems that supports Sponsor (Sue).
organizational goals.
5 John Project Manager Controls, monitors, executes, William
Current designs, plans, initiates and closes McConnell
project CIO
6 Kevin Business Analyst Develops technical business Project Manager
, Running Head: Final Project 4
Smith solutions
7 Trey Mattia Architect Create technical standards such as Project Manager
coding standards, tools and
platform.
8 Ellena Quality Assurance Ensuring standard and Project Manager
Borel specification are followed to meet
user requirements
9 Walton Database Capacity plan, installation, Project Manager
Almeda Administrator configuration, database design,
and performance monitoring,
1 Rohn ETL Developer Work closely with Business Business Analyst
0 Laquanda Analyst and database Kelvin Smith
Administrator to ensure end to end
design meet requirements
11 Joan ETL Developer Work closely with project manager Project Manager
Willmon to develop and update ETL task John
plan.
1 Roy Kirk Report Developer Uses reporting tools like excel and Project Manager
2 pivot to create automated reports. John
1 Corina Report Developer Uses reporting tools like excel and Roy Kirk
3 Kees 2 pivot to create automated reports.
1 Jacqualine Developer Designing, installing, test and
4 Water (System/Software maintenance of software systems.
)
1 Ricarda Subject Matter Define, processes, policies and
5 Sienkiewic Expert application requirement
z
2. Reporting Structure
According to (Johnson, n.d), reporting structure is the chain of command which embodies
the communication structure of an organization or a team. The communication structure of
medical informatics project team has been designed in a way that all team members with the
exception of the external stakeholders like IS manager (Waltreud Tatem), Business owner (Brant
Amero), CIO, and Sponsor (These are the decision makers whom the project manager report to),
Medical Informatics Wellness Project
Plan Dr.
IT-625
Date
, Running Head: Final Project 2
Table of Contents
I. Conflict Resolution Plan......................................................................................................................................5
A. Team Dynamics Overview.................................................................................................................................5
B. Conflict Resolution Leadership........................................................................................................................10
C. Motivation and Confidence..............................................................................................................................11
II. Project Status Evaluation..................................................................................................................................12
A. Status Evaluation.............................................................................................................................................12
B. Project Analysis...............................................................................................................................................12
C. Forecasting.......................................................................................................................................................14
D. Impact of the past.............................................................................................................................................19
E. Corrective Actions...........................................................................................................................................19
III. Project Charter..............................................................................................................................................21
A. Project Objectives............................................................................................................................................21
B. Project Strategy................................................................................................................................................21
C. Project Communication Plan...........................................................................................................................24
IV. Project Planning and Controls......................................................................................................................38
A. Project Scope Planning....................................................................................................................................38
B. Project Scheduling Planning............................................................................................................................41
C. Project Cost Planning and Control...................................................................................................................43
D. Risk Management Plan....................................................................................................................................47
E. Risk Control.....................................................................................................................................................48
F. Project Quality Planning..................................................................................................................................51
V. Project Approvals...............................................................................................................................................55
,Running Head: Final Project 3
I CONFLICT RESOLUTION PLAN
Most project will experience some sort of conflict as a result of difference in values,
behaviors, interest, attitude to work, resource and personalities. The purpose of conflict
resolution is to ensure a sound resolution to these differences to help improve performance or
keep a project on track to it objectives which may include time, cost and customer requirements.
A.) Team Dynamics Overview
1. Roles and Titles:
According to the case study provided, medical informatics is working on creating a new
product (clinical data warehouse software package), the key success factor of the product is (time
to market and quality) and the scope of the project which is to create a modular software package
to handle wellness vendor data appears to have been well-defined. Though a team of 10 people, a
plan has been put in place, but it falls short on clear details on how to achieve the tasks/goals
necessary to accomplish the project hence the delays and conflicts being experienced.
NAME TITLE ROLE REPORT
1 Sue Barret Sponsor Overall accountability of Project NIL
2 Brant Business Owner User requirements Relates with
Amero Sponsor
3 Waltraud Information Decides on workplace device Relates with
Tatem Systems Manager upgrades, maintenance and sponsor (Sue).
installations
4 William Chief Information In charge of IT and computer Relates with
McConnell Officer systems that supports Sponsor (Sue).
organizational goals.
5 John Project Manager Controls, monitors, executes, William
Current designs, plans, initiates and closes McConnell
project CIO
6 Kevin Business Analyst Develops technical business Project Manager
, Running Head: Final Project 4
Smith solutions
7 Trey Mattia Architect Create technical standards such as Project Manager
coding standards, tools and
platform.
8 Ellena Quality Assurance Ensuring standard and Project Manager
Borel specification are followed to meet
user requirements
9 Walton Database Capacity plan, installation, Project Manager
Almeda Administrator configuration, database design,
and performance monitoring,
1 Rohn ETL Developer Work closely with Business Business Analyst
0 Laquanda Analyst and database Kelvin Smith
Administrator to ensure end to end
design meet requirements
11 Joan ETL Developer Work closely with project manager Project Manager
Willmon to develop and update ETL task John
plan.
1 Roy Kirk Report Developer Uses reporting tools like excel and Project Manager
2 pivot to create automated reports. John
1 Corina Report Developer Uses reporting tools like excel and Roy Kirk
3 Kees 2 pivot to create automated reports.
1 Jacqualine Developer Designing, installing, test and
4 Water (System/Software maintenance of software systems.
)
1 Ricarda Subject Matter Define, processes, policies and
5 Sienkiewic Expert application requirement
z
2. Reporting Structure
According to (Johnson, n.d), reporting structure is the chain of command which embodies
the communication structure of an organization or a team. The communication structure of
medical informatics project team has been designed in a way that all team members with the
exception of the external stakeholders like IS manager (Waltreud Tatem), Business owner (Brant
Amero), CIO, and Sponsor (These are the decision makers whom the project manager report to),
