Get help from the best in academic writing.

This paper is for an admissions essay for Clinical PsyD. Included in the essay, here is some information about

This paper is for an admissions essay for Clinical PsyD.

Included in the essay, here is some information about myself
⁃ I have been working at an agency for over two years working with children and their families working on family dynamic, communication skills, trauma, self-esteem, anger management, behavioral issues, emotional, and attachment issues.
⁃ I work with children that are on the spectrum
⁃ My cases are involved with Tri-County Care Management Organization, Mobile Response and Stabilization Services, and DCP

Green Student Data Management System Project Plan Report The Green School is

Green Student Data Management System Project Plan Report

The Green School is striving to gain international standards to be able to improve services delivery as well a increase the capacity in terms of data handling. The move has proved to be successful and thus with the implementation of the Green Student Data Management System the schools is set to experiences a new dawn in quality service, flexibility in handling large junks of student information as well as next level customer experience.

Scope of the project

The scope of Green Student Data Management System entails the planning, scheduling as well as the implementation, testing and implementation of the system. The Green Student Data Management System is expected to exceed the requirements and expectations of the client and as such, the project management plan intends to take charge of the documentation as well as the manuals and trainings required to facilitate the roll out of the system. The Green Student Data Management System project work is expected to be conducted internally without any outsourcing, apart from the infrastructural part, which will call for inclusion of vendors to supply the required computer and other IT equipment. However, the project scope will not include any changes to the requirements in light with the standard operating systems.

Objectives of the project

The project seeks to accomplish a number of objectives as follows:

Ensuring that the end users, who is the client in this case, makes maximum input to the design process of the system.

Be able to accomplish the business as well as the project objectives and goals in line with the stipulated project budget as well as the availed time constraint.

Be able to reduce significantly the impact to standard business operations in the event of any change needs.

Benefits of the project

The benefits of the project are numerous for the organization, as well as the client to the organization (Green School and the students). Among the benefits that the stakeholders are set to benefit include:

Reduced cost of business in dealing with data and information irrespective of the volumes and nature

Flexibility in data and information handling

Reduced time in serving students hence better customer service

Better and guaranteed security of information

Longevity of the information stored

Ease of space in terms of storage for data and information

Conclusion

In conclusion, the project, Green Student Data Management System development is aimed at making the data and information handling at Green School a better experience that comes with a lot of advantages like cost saving, flexibility and security. The project will improve staff morale as well as increase productivity. On the part of the students, the system will save them time in retrieving and accessing information online and in a timely as well as an efficient manner, placing the schools at a better place to be marketed for international standards.

Project Management Plan Version: Green student data management

This paper is for an admissions essay for Clinical PsyD. Included in the essay, here is some information about Psychology Assignment Help Project Management Plan Version:

Green student data management System

Version:

student data management System

project Management plan

Introduction

The school administration recently requested and approved the competition to come up with a workable Student Data Management System, to be able to change the experience in handling of student information and improve student services. The proposed project is expected to lead to the development of a new student management system, which will serve the interests of the students as well as those of the school. This is in line with the increasing corporate strategy that advocates for the provision of progressive improvement, and which seeks to improve productivity at the place of work.

Purpose of Project Management Plan

The Green school has proved to be successful in its transformation from the manual data and information handling in the aggressive pursuit of quality service delivery. More so, there is an understanding for the need to develop and have in place a system that can incorporate most of the information handling requirements, to be able to speed up security of information, longevity of the lifespan of the information stored as well as cut down on the storage space required to store the information. Furthermore, there is also the need to speed up the access to information and data to be able to save on time and improve on the client (student) satisfaction levels.

The intended audience of the Green Student Data Management System is all project stakeholders including the project sponsor (the school), senior leadership and the project team.

Executive Summary of Project Charter

In line with the project plan, the project manager has the overall mandate as well as responsibility for the management alongside the execution of the project, in agreement with this project management plan as well as any subsidiary project management plans. While there are numerous management systems available to pick from, the school recognizes the fact that the changing business environment dictates a customized solution to organizational needs, suited to the organization requirements as well as the times and technological age. The project plan lays out how the project manager will be working with all the resources to undertake project planning.

Assumptions/Constraints

In line with the project charter, the following assumptions were made in the preparation of the project management plan:

The Green School staff is willing to accept changes in business operations so that they can take advantage of the functionalities that come with the proposed system.

That the management will show support for the project by ensuring their project team participants avail themselves as per the requirements to complete tasks.

That the project steering committee will ensure participation in the project by ensuring the timely and accurate execution of the project plan

That all the team members’ part of the project will ensure adherence to the project communication plan.

The following were considered the constraints of the project

Acknowledged limited funds

Inconsistent availability of resources

Scope Management

The Green Student Data Management System project scope takes care of the planning as well as the design and development, summing up with the transition of the management system software. The proposed software is expected to meet and exceed the requirements of the organization in terms of software standards as stipulated in the project charter. The project management scope takes care of the completion of all manuals as well as any required documentation alongside any requirements for training needs to be used alongside the software. The project completion shall be termed to be complete at a point when the software as well as the documentation package has been executed in a successful manner and eventually transitioned to the administration group at the school.

Work Breakdown Structure

The work breakdown structure of the Green Student Data Management System is constituted of parts that will not exceed 80 days of work, though they are at least 6 hours of work. The working project parts have been developed with the aid of close collaboration between the project teams as well as the relevant stakeholder. Further input on the work breakdown structure was sought from the functional managers as well as incorporation of research from a range of related past projects. The project schedule is expected to be presented with the aid of Gantt charts by the project manager

Deployment Plan

This project will entail the deployment of the Green Student Data Management System to the administration team of the Green School. The system roll out plan will entail training for the staff on the use of information technology as a foundation to understanding the system. The Basic Foundation Training (BFT) will then be followed by System Orientation Training (SOT), which will entail familiarizing the administrative staff as well as other support staff with the developed management system. The following third step will be the installation of the infrastructure, then the installation and deployment of the management system. To ensure that the system picks up well in harmony with the staff and expectations of the organization, a follow up and monitoring process will be conducted for a period of one three months.

Change Control Management

Below is a change control plan to govern the control process of all the tasks in the Green Student Data Management System:

The first step to change management will involve the identification of the need for change. At this point, there is a requisition for system change within the project duration.

The second step will involve logging the change requested in the register for change request, done by the project manager.

The third step will entail conducting a change evaluation as well as the impact the change will have on the cost of the project. This will be conducted in collaboration with the project manager, the person requesting the change as well as the project team.

The fourth step will be submission of the request for change to the change control board, and is conducted by the project manager.

Fifth step will include the decision making process, which will be handled by the change control board.

Finally the sixth step will involve the implementation of the said change, if and when the change is approved

Schedule/Time Management

The project schedules for the Green Student Management System will be developed with the aid of Microsoft project 2008. The schedules will commence with the have been identified in the work breakdown structure. The project activity definition will seek to identify specific work packages that have to be completed to be able to accomplish each deliverable. An activity sequence will be used to determine the order to be followed in arranging the work packages in the order of completion requirement given the dependability that exists between activities. An activity duration estimate will be conducted to ensure accurate calculation of work periods that will be required to complete different tasks. Resource estimation will be conducted to allocate resources to work packages as well as develop a schedule for development and completion.

As per the organizational standards at the Green School, the following are the designated milestones for the project:

Scope statement completion

Development of the work breakdown structure as well as its relevant dictionary

Completion of a baseline project schedule

Final project budget approval

Commissioning as well as start of the project

Roles as well as responsibility approval and allocation

Definition of the requirements as well as the respective definition

Data mapping completion

Implementation of the project

Final deliverables acceptance

Milestones

The table below lists the milestones for this project, along with their estimated completion timeframe.

Milestones

Estimated Completion Timeframe

Complete gathering of requirements

1 week

Green Student Data management system Design

15 working days

Coding of the Green Student Data management system

One month

Green Student Data management system testing and debugging

10 days

Green Student Data management system

24 days

Project Schedule

The project will be scheduled in eight phases as indicated below:

Phase

Description

Time frame

Owner

1

Securing of agreements with vendors as well as relevant stakeholders

One month

The project manager and the client (Green School) as well as the relevant stakeholders

2

Completion of Green Student Data management system design

15 days

The project team and the project manager

3

Green Student Data management system coding completion

One month

The project team

4

Ordering and installation of infrastructure/equipment

One month

Project team

5

Conducting training and orientation

15 days

Project team

6

Installation and testing of the Green Student Data Management System

10 days

Project team and project manager

7

Implementation of the Green Student Data management system

15 days

Project manager and the project team

8

Follow up and monitoring of the Green

3 months

Project manager

Dependencies

The project task packages will be dependent on each other completion as below:

Phase

Description

week 1

week 2

week 3

week 4

week 5

week 6

week 7

week 8

week 9

week 10

week 11

week 12

week 13

week 14

week 15

week 16

week 17

week 18

week 19

week 20

week 21

week 22

week 23

week 24

1

Securing of agreements with vendors as well as relevant stakeholders

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2

Completion of Green Student Data management system design

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3

Green Student Data management system coding completion

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4

Ordering and installation of infrastructure/equipment

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

5

Conducting training and orientation

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

6

Installation and testing of the Green Student Data Management System

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

7

Implementation of the Green Student Data management system

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

8

Follow up and monitoring of the Green

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Cost/Budget Management

The project manager for the Green Student Data Management System will be the one responsible for the management as well as the reporting concerning the project cost for the duration of the project. The project manager will be charged with the responsibility of reviewing any calculations that concern the project cost and equally they will be responsible for the accountability of the project expenditure and reporting every month’s project status in status meetings. It is also expected that all budgetary authorizations as well as decisions will lie in the hands of the project sponsor, Green School, which includes reviews to budgetary changes. As a measure of budgetary control, cost as well as schedule performance index will have to be reported monthly by the project manage and to the sponsor, who is the client. It should be noted that any positive or negative changes amounting to -10% or 10% will be dimmed to be cautionary and will change the cost statues indicator to yellow. Similarly, changes amounting to -/+20% will indicate a critical change in the cost and will change the cost status indicator to red. Corrective action will have to be undertaken in both cases to review and identify the causes and corrective as well as preventive measures put in place

Quality Management

The quality control plan will call for every team member playing a role in the quality management process. According to the principle of Total Quality Management that identifies TQM as a continuous process, calls for quality being installed in the process. Likewise, all the team players will have to be part of the quality control team. The client, who is the sponsor of the project, will be responsible for the provision of quality standards. The project manager on his part will be responsible to manage quality standards throughout the project. The remaining entire project team will have to work in conjunction with the project manager as well as all the relevant stakeholders to ensure quality standards are met (Kerzner, 2013).

Human Resource Management

The Green Student Data Management System will be staffed as follows:

Position

Number of Personnel

Responsibility

Project manager

1

All management of the Green Student Data Management System

Senior programmer

1

Oversight as well as programming requirements for the Green Student Data Management System

Programmer

1

Responsible for the coding as well as programming for the Green Student Data Management System

Quality specialist

1

Responsible for assisting the project manager with quality control responsibilities and issues

Technical writer

1

Compiling all the project documentation requirements

Testing specialist

1

Helping as well as establishing the required testing specifications for the Green Student Data Management System

Communications Management

The project manager will be charged with the responsibility leading the role of communication and ensuring effective communication takes place throughout the project period.

Communication Matrix

Stakeholder

Messages

Vehicles

Frequency

Communicators

The sponsor and the project team

Monthly project and cost status

Monthly status meetings

Monthly

Project manager

Project team

Technical design review

Weekly review meetings

Weekly

Senior programmer

Project team

Review of project gates

Weekly review meetings and memos as need arises

Weekly and as need arises

Project manager and quality specialist

Risk Management

In managing risks for the Green Student Data management System, there will be a systematic as well as a methodological approach as identified by the team. The project manager will have to conduct a risk analysis at the beginning and end of the project to identify and relay the same for action from the team.

Procurement Management

The project manager will have to provide an oversight supervisory role in terms of the procurement requirement of the project. He shall be entitled to approving at any single time an expenditure not exceeding $37,000 unless it is with the consent of the sponsor.

Appendix A: Project Management Plan Approval

The undersigned acknowledge they have reviewed the Green Student Data Management System Project Management Plan and agree with the approach it presents. Changes to this Project Management Plan will be coordinated with and approved by the undersigned or their designated representatives.

Project Manager

The School Director

The school Accountant

Signature:

Date:

Print Name:

Title:

Role:

Signature:

Date:

Print Name:

Title:

Role:

Signature:

Date:

Print Name:

Title:

Role:

APPENDIX B: REFERENCES

The following table summarizes the documents referenced in this document.

Document Name and Version

Description

Location

Kerzner, H. (2013). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.

A book take provides insights in total Quality Management and all project management functions form planning, scheduling as well as controlling

https://books.google.co.ke/books?hl=en&lr=&id=QgQQC5qRtzgC&oi=fnd&pg=PT18&dq=TQM+in+projects+management+&ots=C-GGfoKZNR&sig=n7B_lon3sSsZs5fKAdzQSJ3hDvI&redir_esc=y#v=onepage&q=TQMinprojectsmanagement&f=false

APPENDIX D: SUMMARY OF SPENDING

Revision Date: Error! Unknown document property name. Page 2 of 21

CDC_UP_Project_Management_Plan_Template_v1.1.doc

Page 10 of 13

1

Revision Date: Error! Unknown document property name.

Project Management Plan Version:

Project Management Plan Version:

Version:

project Management plan

TABLE OF CONTENTS

1 Introduction 4

1.1 Purpose of Project Management Plan 4

2 Executive Summary of Project Charter 4

2.1 Assumptions/Constraints 4

3 Scope Management 4

3.1 Work Breakdown Structure 4

3.2 Deployment Plan 4

3.3 Change Control Management 4

4 Schedule/Time Management 4

4.1 Milestones 5

4.2 Project Schedule 5

4.2.1 Dependencies 5

5 Cost/Budget Management 5

6 Quality Management 5

7 Human Resource Management 5

8 Communications Management 5

8.1 Communication Matrix 5

9 Risk Management 5

9.1 Risk Log 6

10 Issue Management 6

10.1 Issue Log 6

11 Procurement Management 6

12 Compliance Related Planning 6

Appendix A: Project Management Plan Approval 7

APPENDIX B: REFERENCES 8

APPENDIX C: KEY TERMS 9

APPENDIX D: SUMMARY OF SPENDING 10

Introduction

Purpose of Project Management Plan

[Provide the purpose of the project charter.]

The intended audience of the is all project stakeholders including the project sponsor, senior leadership and the project team.

Executive Summary of Project Charter

[Provide an executive summary of the approved project charter. Provide a reference to the approved Project Charter. Elaborate on any sections within the Project Charter that need further detail contained within the PMP.]

Assumptions/Constraints

[Insert summary of any changes from the project assumptions and/or constraints that were originally outlined in the project charter.]

Scope Management

[Insert the project’s scope management plan or provide a reference to where it is stored.]

Work Breakdown Structure

[Insert the project’s work breakdown structure or provide a reference to where it is stored.]

Deployment Plan

[Example: The project involves deploying an application to state health partners. This section would discuss the approach for rolling out the application to the end users, including conducting environment assessments, developing memorandums of understandings, hardware/software installation, data conversion.]

Change Control Management

[Example of Change Control: If a development server for your project is administered by another organization that is responsible for installing machine upgrades and there are scheduled outages that will impact your project schedule. Changes to the project will need to be made to deal with the potential impact of the scheduled outage.]

Schedule/Time Management

[Example of schedule management approach: Establish a baseline within the first two weeks of the project and monitor progress against the baseline on a weekly basis. The Project Manager will be responsible for ensuring the project schedule is updated with the latest information and never more than three business days out of date. For variances on executive milestones greater than 10%, the project may choose to use guidance specified by CPIC. See the CDC UP Project Schedule document for more guidance on project schedules and for Project Schedule templates.]

Milestones

The table below lists the milestones for this project, along with their estimated completion timeframe.

Milestones

Estimated Completion Timeframe

[Insert milestone information (e.g., Project planned and authorized to proceed)]

[Insert completion timeframe (e.g., Two weeks after project concept is approved)]

[Add additional rows as necessary]

Project Schedule

[Insert the project’s schedule or provide a reference to where it is stored.]

Dependencies

[Insert the schedule/project dependencies (both internal and external).]

Cost/Budget Management

[Insert the project’s cost management plan or provide a reference to where it is stored.]

Quality Management

[Example: For an information system, controlling the consistency of screen layouts would include reviewing all screens to make sure they match the standards. Quality measures may be no bugs or defects for certain critical requirements, consistent screen layouts, or correctly calculating variables. Quality may be ensured through inspections, audits, formal testing and documentation of defects in a defect tracking system to ensure defects are fixed, retested and closed. Some projects may choose to use a traceability matrix to determine if critical requirements have been met.]

Human Resource Management

[Insert the project’s human resource management plan or provide a reference to where it is stored.]

Communications Management

[Insert the project’s communication management plan or provide a reference to where it is stored.]

Communication Matrix

[Insert the project’s communication matrix or provide a reference to where it is stored.]

Stakeholder

Messages

Vehicles

Frequency

Communicators

Feedback Mechanisms

Risk Management

[Insert the project’s risk management plan or provide a reference to where it is stored.]

Issue Management

[Insert the project’s issue management plan or provide a reference to where it is stored.]

Procurement Management

[Example: This can include information such as ensuring project team members are assigned computers, how development and test servers are procured or can go into more detail and include an acquisition strategy that details how the project will be staffed (e.g., performance based fixed price contract, CITS contractors).]

Compliance Related Planning

[Insert a list of compliance related processes the project must adhere to. For assistance with determining which compliance processes need to be followed visit http://www2.cdc.gov/cdcup/document_library/project_assessment.asp]

Appendix A: Project Management Plan Approval

The undersigned acknowledge they have reviewed the Project Management Plan and agree with the approach it presents. Changes to this Project Management Plan will be coordinated with and approved by the undersigned or their designated representatives.

[List the individuals whose signatures are desired. Examples of such individuals are Business Steward, Project Manager or Project Sponsor. Add additional lines for signature as necessary. Although signatures are desired, they are not always required to move forward with the practices outlined within this document.]

Signature:

Date:

Print Name:

Title:

Role:

Signature:

Date:

Print Name:

Title:

Role:

Signature:

Date:

Print Name:

Title:

Role:

APPENDIX B: REFERENCES

[Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.]

The following table summarizes the documents referenced in this document.

Document Name and Version

Description

Location

[Provide description of the document]

APPENDIX C: KEY TERMS

[Insert terms and definitions used in this document. Add rows to the table as necessary. Follow the link below to for definitions of project management terms and acronyms used in this and other documents.

http://www2.cdc.gov/cdcup/library/other/help.htm

The following table provides definitions for terms relevant to this document.

Term

Definition

[Insert Term]

[Provide definition of the term used in this document.]

[Insert Term]

[Provide definition of the term used in this document.]

[Insert Term]

[Provide definition of the term used in this document.]

APPENDIX D: SUMMARY OF SPENDING

[You may double-click on the table to edit it according to the information applicable to this project.]

PY: Previous Year; CY: Current Year; BY: Budget Year

Revision Date: Error! Unknown document property name. Page 2 of 21

CDC_UP_Project_Management_Plan_Template_v1.1.doc

[Insert appropriate disclaimer(s)]

Page 9 of 10

[Insert appropriate disclaimer(s)]

1

Revision Date: Error! Unknown document property name.