**This what needs to be worked**

Project Lessons Learned / Reflection (u06a1).

Quality Accreditation Evaluation

.

Lessons Learned.

Reflections.

Update all corrections to previous portions based off the word document

Updated project schedule in Microsoft Project.

Instructions

Quality Accreditation Evaluation

Here at Capella University, we have the following quality accreditations:

• Accreditation Council for Business Schools and Programs (ACBSP).
• Accreditation Board for Engineering and Technology (ABET).
• Project Management Institute (PMI).
• Society for Human Resource Management (SHRM).

Using the Capella library, research two of the four accreditations and conduct an evaluation that includes:

• Description of the accreditation.
• Application of the accreditation to the quality discipline.
• Benefits and value of an accreditation to the institute.
• Benefits and value of an accreditation to the learner.

Include this evaluation in the Project Lessons Learned and Reflection – Quality Accreditation Evaluation section of the

Project Management Plan

Template.

Project Management Plan

Create a final version of your project management plan and your final project schedule in Microsoft Project, after incorporating any changes required after receiving instructor feedback. Your final plan should be in the following format.

• Table of Contents.
• Executive Summary (u06a1).
• Scope Management Plan (u01a1).
• Time Management Plan (u02a1, u03a1).
• Cost Management Plan (u04a1).
• Quality Management Plan (u05a1).

Project Lessons Learned / Reflection (u06a1).

• Quality Accreditation Evaluation.

Lessons Learned.
Reflections.

• Reference List

Additional Requirements

Your assessment should meet the following requirements.

• Written communication: Ensure written communication is free of errors that detract from the overall message. Complete assessments in a detailed, comprehensive, and error-free manner.
• Documents:

  Updated Project Management Plan template.
  Updated project schedule in Microsoft Project.

• References: Include a list of references, including books, Web sites, articles, and other resources.
• Font and font size: Times New Roman, 12 point.

Project Management Plan

PM-FP4030 – Scheduling, Cost and Quality Management

Name:

Date:

Instructor:

Table of Contents:

Contents
Table of Contents: 2
Executive Summary (u06a1) 4

Project

Scope Management (u01a1)

5

Overview

5

Business Objectives

5

Product Description (Solution)

5
Business Objectives 5

Project Description

5
Project 5

Project Milestone

5

Project Approach

6

Authorizations

6

Project Scope Statement Approval / Signatures

6

Project Time Management Plan

7

Introduction

7

Work Breakdown Structure (u02a1)

7

Project Sequencing Evaluation (u02a1)

7

Project Schedule Plan / Critical Path Analysis (u03a1)

7

MS Project Schedule:

7
Critical Path Analysis Summary: (u03a1) 7

Project Cost Management

8

Introduction:

8

Cost Estimate Budget / Schedule Update (u04a1)

8
Introduction 8

Budget Summary Information

8

MS Project Schedule Update

8

Project Quality Management

8
Introduction 8

Project Quality Tools and Metrics (u05a1)

8

Project Lessons Learned and Reflection

9

Quality Accreditation Evaluation (u06a1)

9

Lessons Learned / Reflection (u06a1)

9

References

11

Executive Summary (u06a1)

Project Scope Management (u01a1)

Project Name: Preventive Care

Prepared by : Angela Brogsdale

Date : 2/2/2021

Overview

This project aims at automating Preventative Care’s data and records management system. The healthcare institution needs to connect all the physicians from all the five locations to ensure that they can collaborate to improve the quality of patient care and patient outcomes (Sligo et al., 2017). Preventative Care hospital has an issue of patient data duplication and redundancies and new patients take a lot of time trying to get their medical information and history in order before they begin the consultation process (Gomez & Romão, 2018). This project would ensure that patient data is stored in centralized location to reduce the operating expenses and accessed anywhere whether at the five locations or at home. This project aims at enabling the hospital administration to manage the entire organization, saving time and its financial resources by ensuring that enough time is devoted to patients and not on administrative tasks.

Business Objectives

Product Description (Solution)

The healthcare information management system would have two modules, Admin and Users. The Admin would be able to view the main keywords from the questions asked by users, they can manage doctors, nurses, and other healthcare service providers by adding them, can update healthcare service providers’ live information, and even delete non-existing doctors from the system. The admin can also delete, add, and update information on diseases and the available remedies to cure them (Sligo et al., 2017). The Users, on the other hand, in this case the healthcare service providers, can access patient information according to their level of clearance, send queries on particular diseases, get the proper information related to diseases, access available remedy solutions for specific diseases, and also get information on specialist doctors around the area.

Business Objectives

The business’ main objectives is to automate their information system from the manual paper based system to an online and automated one. The objective of the system is to connect all the physicians and other healthcare service providers from the five locations to ensure that they are able to communicate and collaborate effectively to ensure the provision of quality healthcare services to its clients to improve the quality of patient outcomes.

Project Description

The project is set to commence once approved by the project owners and project sponsors. The project would be worked on by teams, each specialized in their specific areas like web development, front-end development, back-end development, networking, database development, and system testing, implementation, and maintenance.

Project Scope

The main goal of the project is to develop an online and automated health information system that would ensure that the physicians in Preventative Care’s five locations are able to communicate, collaborate, and share patient information effectively. The project’s main features are the web application where the physicians would log in as users and the administrator would have the privileges of either granting or revoking access rights (Sligo et al., 2017). The project’s cost is supposed to be within the 250,000 dollars budget and completed before May, 2021.

External Dependencies

The project would depend on the current technologies present in its development and implementation phases.
Assumptions

The main assumption made is that the intended budget would cover the project’s cost throughout its development lifecycle.

Constraints

The project’s main constraints include lack of qualified professionals in the sector of cyber security who would ensure that the system maintains the privacy of the patients’ information.

Project
Project Milestone

Project Start

Target Date

Front-end development

2/28/2021

Backend development

2/2/*2021

Database development

3/30/2021

System implementation and user training

4/30/2021

Project Approach

Primary Plans

The project will have the following formal written plans:

Project Scope Management Plan

Project Time Management Plan

Project Cost Management Plan

Project Quality Management Plan

Authorizations
Project Scope Statement Approval / Signatures

Project Name:

Project Manager:

Angela Brogsdale

The purpose of this document is to provide a vehicle for documenting the initial planning efforts for the project. It is used to reach a satisfactory level of mutual agreement between the Project Manager and the Project Sponsors and Owners with respect to the objectives and scope of the project before significant resources are committed and expenses incurred.

I have reviewed the information contained in this Project Scope Statement and agree:

The signatures above indicate an understanding of the purpose and content of this document by those signing it. By signing this document, they agree to this as the formal Project Scope Statement document.

Project Time Management Plan
Introduction

The project’s main deliverable is to develop an automated health information system. The system’s main deliverables include:

1. User accounts, that is, the accounts used by the healthcare service provider

2. Admin accounts, that is, the account used by the system administrator to either grant or revoke access rights, and to update, add, or delete the contents of the information system.

3. A working database connected to the database server.

4. An internal network with all the hospital’s computers and devices connected to it.

5. A billing system connected to third party insurance companies

6. Patient accounts where they can book appointments and schedule for treatments with their physicians.

7. Two step authentication controls for system security.

Work Breakdown Structure (u02a1)

Work Breakdown Structure in a Logical Structure Supporting Project Objectives

Activity

Activity Description

Duration (Days)

Preceding Activities

A

Collection of user requirements

14 days

__

B

Determine system requirements

7 days

__

C

Analyze user and system requirements

7 days

A, B

D

· Design system (Both the user interface and the backend
· Create a prototype
· Present the prototype to the intended system users, system owners, and system sponsors for review.

14 days

A, B, C

E

· Commence with system development after the prototype has been accepted and approved by the users, system owners and system sponsors.
· If prototype not approved, repeat activity D.
· Continue with unit, module, and system testing in iterative manner.
· Document the system

60 days

A, B, C, D

F

· Select the server location, that is, room and its location within the main building.
· Host the system in the servers

14 days

__

G

· Test the system with potential users
· Review the system according to the feedback generated from user testing

14 days

E

H

· Implement the system
· Train the system users
· Maintain the system

14 days

G

Project Sequencing Evaluation (u02a1)

Project Sequencing Evaluation

The individual activities would either use the start to start or the start to finish scheduling methods. The collection of system and user requirements would happen concurrently (Burghate, 2018). The analysis of the system and user requirements would succeed the collection of system and user requirements. The system development phase and the testing would happen in iterative start to finish mode (Al-Kasasbeh et al., 2020). The selection of server location and its installation could happen at any time within the project development lifecycle. The system documentation process would also happen at the same time with the system development phase.

Types of Logical Relationships

A logical relationship in project management is defined as the dependency between two project schedule activities or between a schedule milestone and a project schedule activity. There are four main types of logical namely, finish-to-start, start-to-finish, finish-to-finish, and start-to-start. Precedence relationship, on the other hand, is the term used in a logical relationship in the precedence diagramming method. In each of the logical relationship, predecessor and successor scheduling activities interact (Al-Kasasbeh et al., 2020). In the finish-to-start logical relationship, the initiation of a successor activity is dependent on the completion of the predecessor activity. In a finish to start logical relationship, the completion of a successor activity cannot happen until the predecessor activity is also completed. In the health information system project, the development and implementation protocols follow a successful implementation of the database.

In a start-to-start logical relationship, the initiation of a successor schedule activity is dependent on the initiation of the predecessor schedule activity. In our health information management system, the development of its backend can happen at the same time with the development of its user interface (Burghate, 2018). In a start-to-finish logical relationship, the completion of the successor activity depends on the initiation of the predecessor activity. An understanding of these four types of logical relationships helps in modelling an IT project more accurately. In a finish to finish logical relationship, one task can only be completed after the other on has been completed. This is to mean that a successor activity will only finish if the predecessor task has been completed.

Advantages of Each Type of Logical Relationship

The main advantage of the start to finish logical relationship is that it is accurate since the successor activity completed when the predecessor activity is initiated. The main advantage of finish to finish logical relationship is that all the activities with this type of relationship would be completed at the same time reducing confusion of project mix-ups. The main advantage of finish to start is that it encourages redundancy of the roles of any of the team members working on the project (Al-Kasasbeh et al., 2020). The main advantage of the start to start logical relationship is that the activities would run concurrently making use of the economies of scale.

Disadvantages of Each Type of Logical Relationship

The main disadvantage of the finish to start logical relationship is that it does not accurately schedule a project’s activity. This is because while the exact day of the completion of a predecessor schedule activity is set, it does not guarantee that the activity would be completed within the stated period. The finish to start logical relationship is therefore mostly unreliable. The main disadvantage of the start to start logical relationship is that confusion may arise between developers since some of the tasks in both the scheduling activities may have overlapping roles (Hamledari et al., 2017). The start to start logical relationship also leads to time lags since either one of the scheduled activities cannot start when the other has not been initiated yet. The finish to finish logical relationship also leads to time lags since the successor activity has to wait on the predecessor activity before being completed.

Project Schedule Plan / Critical Path Analysis (u03a1)
MS Project Schedule:

Critical Path Analysis Summary: (u0a3a1)

The project’s critical path establishes the longest path in time, from the commencement to the conclusion of a project. The critical path establishes the minimum time necessary for an entire project to be completed. As indicated in the critical path analysis document the project’s critical path is the time taken during the coding and development of the actual system. The time the coding and system development takes is 60 days and this is therefore considered the minimum time within which the project can be completed (Chen & Hsueh, 2018). The coding and development phase is the longest sequence of the project and it includes tasks that must be completed to conclude the project successfully. The minimum expected duration for the completion of the project is therefore 60 days.

It is possible to compress the other activities of the project, activities such as the collection of user and system requirements, the analysis of user and system requirements, the design of the system, the design and presentation of the system’s prototype to the stakeholders, the testing of the end product after coding and the installation of the servers and other networking components into the 60 days period (Chen & Hsueh, 2018). These activities can be handed over to other professionals and they can run concurrently with other tasks to ensure that they are completed within 60 days. In the document, the critical path is highlighted in red to indicate the longest possible time for the completion of a task within the project.

Project Cost Management
Introduction:
Cost Estimate Budget / Schedule Update (u04a1)
Introduction

The purpose of this project cost estimate is to determine the amount of money each of the schedules tasks and their respective professionals would cost. The cost estimate would allow the project manager and system developers to have control over the costs and ensure the management of the costs as per the company provided budget (Christensen et al., 2015). The project’s cost estimate is required to be within the 250,000-budget allocated by the company. Below is the total projected costs required to complete the development, implementation and maintenance of the healthcare information management system.

For the IT professional team developing the health management system, their estimated costs goes according to the individual developer’s specification. The human resources cost estimate is as follows:

· System analysts estimated at $50 per hour

· System designers estimated at $ 60 per hour

· .NET developers get paid $80 per hour.

· User Experience/User Interface designers get paid $90 per hour

· Database designers get paid $80 per hour

· Project manager gets paid $100 per hour

· System testers get paid $60 per hour

· System training estimated at $20 per hour

· System changeover estimated at $20 per hour

· Post implementation evaluation $30 per hour

The project requires that .NET professionals work for 100 hours, User experience professionals for 50 hours and the project manager for 100 hours (El-Sawalhi, 2012). The following were the estimated costs for the total number of hours worked by each of the professionals:

· .NET developer, $80 per hour * 100 hours * 4 professionals = $32000

· User experience professionals, $90/hour * 50 hours * 2 professionals = $9000

· Project Manager, $100/hour * 100 hours = $10,000

· System analyst, $50/hour * 20 hours * 2 professionals = $2000

· System designer, $60/hour * 20 hours * 2 professionals = $24000

· Database designer, $80/hour * 20 hours * 2 professionals = $3200

· System tester, 60/hour * 10 hours * 3 professionals = $1800

· System trainers, $20/hour * 4 hours = $80

· System changeover strategy, $20/hour * 200 hours = $4000

· Post implementation evaluator $30/hour * 12 hours * 2 professionals = $720

· Network architecture $120/hour * 100 hours = $12000

· Networking engineer $150/hour * 100 hours = $15000

The total resource cost is therefore is:

$32,000 + $9,000 + $10,000 + $2000 + $24000 + $3200 + $1800 + $80 + $4000 + $720 + $12000 + $15000 = $101170

Hardware Resources

The hardware resources required for the complete implementation of the healthcare information system comprised of the networking infrastructure such as routers, switches, Ethernet cables, servers, secondary storage devices (El-Sawalhi, 2012). The following is the estimated hardware costs for the system development and implementation process:

· Memory (hard disks, ST100DM010 Model) each at $50

· 20 Routers (802.11ac) at $100 each

· Switches (24 port unmanaged) at $70 each

· Ethernet Cables (1km long) at $511

· Database server at $1500

· Network server $1500

The total estimated cost for the hardware resources is as follows

3 hard disks * $50 each + 20 routers * $100 each + 30 switches * 70 each + 1km Ethernet cable at $511 + database server at $1500 + network server at $1500 = $150 + $2000
+ $2100 + $511 + $1500 + $1500 = $7761

Software Resources

A decision was made to outsource cloud services to ensure that all the five branches were able to communicate effectively for the purpose of information sharing. The outsourcing option was also decided upon because the physicians were to be allowed access to the system from remote locations such as when they are offering outpatient and home-based treatment to patients (Christensen et al., 2015). All the devices also had to be connected to the internet and specific operating systems were required since the devices currently used by the hospital facilities were considered outdated and did not offer the wireless connectivity options. The following are the estimated costs for the software:

· Windows 10 Operating System preferably the Windows 10 Pro for Workstations at $309

· Microsoft Azure Cloud Resource at $100 monthly

The total estimated cost for the software resources is as follows:

Windows 10 Pro for Workstations at $309 + Microsoft Azure for business at $100/month * 12 months = $12309

Maintenance and Operation Costs

The system would have to be maintained and operated by IT professionals who would be paid on a monthly basis. The following are the estimated maintenance and operational costs:

· System Upgrade $100/month

· System patch ups $50/hour

· System administrator $800/month

· Data entry officers at $600/month

· Database administrator $500/month

· Network administrator $900/month

· Cyber security specialist $700/month

The total estimated costs for system maintenance, operation cost and after implementation processes is as follows:

$100 + $50 * 10 hours + $800 + $600 +$500 + $900 + $700 = $4100

Budget Summary Information

The budget was given by the company for the entire project was $250000 and the projected estimated total costs fell within the company’s budget and there is therefore no need for the company to direct additional financial resources towards the project development and management cause. The estimated costs for the complete development of the project stands at 125,340 United States dollars while the company’s budget was $250000. The above cost estimated were made using the current costs for purchasing IT hardware and software products together with the industry’s acceptable average wages for individual IT professionals (Christensen et al., 2015). It is therefore appropriate to state that the cost updates are real time and accurate according to the project’s development timeline.

MS Project Schedule Update

[Add introduction of intent and link to MS Project file]

Project Quality Management
Introduction

The main aim of this project quality management section is to ensure that the project would exceed the expectations and the needs of the stakeholders. The project team developed a relationship with the project’s main stakeholders, and it came to realization that the project owners and users’ definition of system quality was a system that met all its deliverables (Chillar & Sharma, 2019). In this document, an outline of the steps taken to determine the quality of the system is highlighted as per the project’s main deliverables.

Project Quality Tools and Metrics (u05a1)

1. Return on Investment

Over a span of 5 years, the monthly and yearly profits of the investment would be recorded and at the end of the period, it would be totaled and used to determine the rate of the project’s return on investment. The return on investment would be calculated using the Ms. Excel spreadsheet program as indicated below (Chhillar & Sharma, 2019). The return on investment is calculated by dividing the profit earned on an investment by the cost incurred during the investment. For instance, assuming that the profits incurred by the system as a result of performance improvements is $240,000 while the cost of investment was $250,000 then the return on investment would be as follows.

ROI = Profit

Cost of Investment

ROI – 240,000

250,000

ROI = 0.96

The return on investment within 5 years would therefore be 0.96. Adjustments can also be made to improve on the performance of a system to increase its return on investment if the results are not desirable.

2. System Usability

The usability of a system can be determined by observing and using questionnaires or conducting surveys to identify the opinions of users concerning the ease and learnability of the system. The results can then be represented using a histogram, indicating the age of individuals and the levels of satisfaction they experience depending on the ease of learning and using the system while using it (Chhillar & Sharma, 2019). The histogram can be developed using the draw.io software. The information represented can be used to determine whether some changes need to be made on the user interface to suit the usability of certain age groups while considering others.

3. System Performance

The performance of a system can be determined using flowchart diagrams. Flowcharts are used to break down a process or system activity. The breakdown of activities enables the pinpointing of system flaws or processes that lead to system lags (Lamine, 2019). The information obtained using flowcharts can therefore be used to make more changes on the system to improve on performance.

Project Quality Tools

1. Check Sheet

Check sheets are used to collect information about the main issues affecting a system and the frequency with which those issues are happening. The information obtained can be used to make adjustments to address those issues.

ISSUES

FREQUENCY

UI Defects

10

System Errors

5

Communication Gaps

15

System Downtimes

2

Skills Gaps

50

System Lags

45

2. Flowcharts

Flowcharts are used to document the workflow process of a system or project. Flowcharts are used when determining the bottlenecks or breakdowns in a work process. Flowcharts also indicate the steps of a process, clearly providing a picture of how a process would look like, and can also shed light on the issues within the process. Whenever a change or an improvement is made on a process, flowcharts can be used to show them. The flowchart below gives a breakdown of what happens when a patient attends the hospital, up to the time they are diagnosed and prescribed with medications.

Software Used

The main tool that was used in the development of the quality management diagrams was draw.io, Ms. Word and Excel. The flowchart was developed using draw.io web application, the return on investment monitored and calculated using Ms. Excel and the system usability representation done using draw.io histograms.

Advantages and Disadvantages of Each Tool

1. Advantages of Flowcharts

Flowcharts enhances problem solving processes since it helps developers and system auditors to identify problematic issues more efficiently. By creating a visual representation of an issue and its probable resolutions, the testing and maintenance team can be able to understand the problem better (Chhillar & Sharma, 2019). Flowcharts also offer effective analysis possibilities for visually identified problems. It also helps developers to reorganize business processes to improve accountability.

2. Disadvantages of Flowcharts

Flowcharts tend to have logical complexity especially for complex processes. When representing complex processes, flowcharts can appear clumsy and messy. Another disadvantage of flowcharts is that its symbols cannot be typed, and they therefore need expertise in specific software to develop them.

3. Advantages of Check Sheets

The main advantage of using check sheets is that it is useful in the collection of both quantitative and qualitative data for analysis (Lamine, 2019). Check sheets help in the systematic collection and organization of data that is useful in determining the performance of a system and its problems that need to be addressed.

4. Disadvantages of Check Sheets

For auditors who are inexperienced, they may have a hard time communicating in a precise manner, about what they are looking for (Lamine, 2019). Check sheets are also restrictive in nature since they are mostly used to pinpoint the issues experienced by system users.

Project Lessons Learned and Reflection
Quality Accreditation Evaluation (u06a1)

[Insert your evaluation here]

Lessons Learned / Reflection (u06a1)

Lessons Learned

Reflections

References

Gomes, J., & Romão, M. (2018). Information and Communication Technologies in the Healthcare: Future Trends for Project Success. International Journal of Privacy and Health Information Management (IJPHIM), 6(2), 72-83.

Sligo, J., Gauld, R., Roberts, V., & Villa, L. (2017). A literature review for large-scale health information system project planning, implementation, and evaluation. International journal of medical informatics, 97, 86-97.

Al-Kasasbeh, M., Abudayyeh, O., & Liu, H. (2020). A unified work breakdown structure-based framework for building asset management. Journal of Facilities Management.

Burghate, M. (2018). Work breakdown structure: Simplifying project management. International Journal of Commerce and Management, 3(2).

Hamledari, H., McCabe, B., Davari, S., & Shahi, A. (2017). Automated schedule and progress updating of IFC-based 4D BIMs. Journal of Computing in Civil Engineering, 31(4), 04017012.

Christensen, P., Dysert, L. R., Bates, J., Burton, D., Creese, R. C., & Hollmann, J. (2015). Cost Estimate Classification system-as applied in engineering, procurement, and construction for the process industries. AACE, Inc, 2011.

El-Sawalhi, N. I. (2012). Modelling the parametric construction project cost estimate using fuzzy logic. International Journal of Emerging Technology and Advanced Engineering Website:(ISSN 2250-2459, Volume 2, Issue 4, 2(4).

Chhillar, D., & Sharma, K. (2019, February). ACT Testbot and 4S Quality Metrics in XAAS Framework. In 2019 International Conference on Machine Learning, Big Data, Cloud and Parallel Computing (COMITCon) (pp. 503-509). IEEE.

Lamine, K. (2019). Lean Six Sigma and Performance Metrics. In Lean Manufacturing and Six Sigma-Behind the Mask. IntechOpen.

HealthSystem.mpp

Project Scope Management (u01a1)

1.    Angela regarding project Overview (page 6) will be appropriate including project cost, project start date (mm/dd/yyyy), project completion date (mm/dd/yyyy) along with considering and briefly discussing project methodology that will be used/considered for the project planning along with software planning tools; being repetitive with stakeholders is not a bad idea to ensure important information is conveyed to project stakeholders.  

2.   Angela reconsider concisely stating within the Business Objectives what the project entails, what it will cost, and project start and target completion date (mm/dd/yyyy); it is important to reinforce communicating with stakeholders what the project entail; reaffirm project details, cost, start and end date

3.   Angela the project Scope is based on the project Charter (or business Objective statement)â��Charter reaffirmation in terms of cost, start and end dates, thus one of the key factors for the project Scope is to revise what the project entails ensuring the project is feasible, the cost is accurate as well as target project completion date; any revisions is fully document and presented to project Sponsor for approval.

4.   Angela will be appropriate further identifying key Charter project milestones (in assessment two you will be asked to develop WBS based on milestones):

a.   Consider focusing/identifying project Scope key milestones (actions to deploy Preventive Care system).

b.   Start milestone description with a noun (or verb) to clearly communicate with stakeholders what the milestone will accomplish.

c.   Refer to WBS example located under Word submitted (page # 6); evaluate/extrapolate appropriate milestones.

Assignment 2 evaluations

1.    Angela per previous feedback, regarding project overview (page 5) reconsider assessment 1 feedback given; include what the project will cost, start (mm/dd/yyyy), and end date (mm/dd/yyyy), project methodology; provide stakeholder a more comprehensive project overview prior to next submission (note: projects are finite); replace 180 day with project start and end date.

2.   Angela regarding project Business Objectives (word page #5) consider in addition to stating what the entails, include what the project will cost, start and end target completion date (mm/dd/yyyy); refer to assessment 1 feedback; itâ��s not a bad idea to reinforce key project information to stakeholders.

3.   Angela reconsider developing a more comprehensive WBS; best approach is being more descriptive as to what the milestone and milestone will accomplish:

a.    Use noun (or verb) to fully describe what the activity will accomplishâ��be more descriptive.  

b.   As you revise WBS activities focusing on project Scope activities; develop a more comprehensive WBS.

c.    Consider that milestone tasks should be atomic (task can no longer be split further).

d.   Consider that WBS will be the basis from which the Gantt will be created later in the course.

e.   Consider revising WBS example located within the Word submitted page #8.

4.   Angela regarding project Logical Relationships consider focusing on project Scope objectives best approach explaining to project Stakeholders what project sequencing is about. Thus, addressing project sequencing (FS, SS, FF, and SF) discussion should be based on project WBS activities comprehensive WBS. Logical FS, SS, FF, and SF diagrams looks appropriate to better provide stakeholders a better understanding the importance of Logical Sequencing for the project; having a comprehensive understanding of the projectâ��s scope will give clues as to the most appropriate order (sequence activities) in which certain activities must be carried out.

a.    Consider creating a table to summarize pros and cons for each logical sequence. Regarding charts, best approach is to develop own charts.

b.   Reconsider creating FS, SS, FF, and SF custom diagram to support Logical Sequencing; educate project Stakeholders who may not be familiar with project Logical Sequencing process. Further consider addressing project logical sequencing based on project WBS milestones. Further, consider creating a table to summarize pros and cons for each logical sequence.

Assignment 3

3.   Angela per previous feedback, consider being more explicit with project Scope; reconsider that project Scope purpose is to take project Charter end confirm that project details, cost and start and end dates are feasible. Plus reviewing Key milestones as well as further identifying project stakeholders. Thus, we should take project Charter and expand based on project Charter revision—re-write Charter, thus details should be more explicit.

4.   Regarding Milestones, reconsider further identifying milestones; on Word page # 6 find a WBS example from where you can extrapolate appropriate milestones—use as an example to identify and create a comprehensive WBS as well.

5.   Regarding WBS reconsider further brainstorming milestones and split milestones into atomic tasks.

6.   Regarding Gantt, reconsider evaluating the following and updating Gantt accordingly:

a.    Create a structured Gantt; demote milestone tasks.

b.   Use detail WBS to create Gantt; be as details as feasible.

c.    Instead of using “Activity A”, use WBS milestones and split milestone into tasks.

d.   Set Task Predecessors to create a more accurate Critical Path.

e.   Allocate task predecessors (who would be completing the task.

f.    Set Gantt Baseline

7.   Reconsider further evaluating (written) and addressing comprehensively project Critical Path (CP) within the Master Project plan document (document section u03a1) as well as identifying and discussing task float by calculating start/end dates and discuss in written form the impact (risks) to your project based on Gantt. Revise milestone Tasks dependencies to create a more accurate critical path.

Assignment 4 u0a1)

Overall Comments:

Angela in the right direction addressing project costing:

1.    Angela reconsider evaluating all project plans (all assessments) feedback given and adjust project plans prior to approaching next assessment.

2.   Regarding Microsoft project costing was expecting a comprehensive project costing using Excel template provided (located under the course assessment template)â��

a.    Consider completing all spreadsheets; if not applicable, explain comprehensively what does not apply to the project.

b.   Analyze project costing baseline.

c.    Regarding Additional Costs consider that is common for project managers to assess “additional/other costsâ�� 3%-5% contingency costs”, thus its appropriate to plan for a 3%-5% above projected cost for last minute incidents.

d.   Evaluate project cost baseline and within the Master Project Plan document (Word) explain in detail project Gantt and budget baselines, its purpose and importance for project managers to understand and use baselines concepts.

3.   Angela regarding project budget baseline, is an approved time phased plan. Once a detailed budget is developed and approved, the project manager should publish this baseline and set it as a point of comparison for actual performance progress during project execution and monitoring phase; consider further evaluating and discussing in written form the Gantt and project costing baselines comprehensively within the Master Project Plans (Word) as well as how discuss Gantt and project budget baselines interpolateâ��its importance during project monitoring and execution.

4.   Angela conder reviewing assessment 4 requirements as well as review assessment Scoring Guide to get a good idea how to approach assessments.

Assessment 5

Assignment 5

1.    Angela reconsider evaluating each assessment feedback given, update project plans document and resubmit. Consider submitting one assignment at a time to ensure assessment excels expectations.

3.   Microsoft Project (Gantt) & Excel (costing) files were not submitted; consider:

b.   Print screen shots submitted are inconclusive.

c.    Please submit Word, MS Project, and Excel as separate file so that I can open.

4.   Angela regarding project quality metrics, reconsider focusing on your project Scope which QA tool would be more appropriate to your project. Reconsider creating a table to contrast QA metrics. Regarding project quality metrics and tools reconsider focusing on your project Scope which QA tool would be more appropriate to your project. Reconsider creating a table to contrast QA metrics tools as well as use charts to depict QA processes focusing on project Scope.