Software Project Management Plan Essay

1842 words - 8 pages

Software Project Management Plan
August 27, 2012

IT Management System

Luvianka Olivares

Table of Contents
Scope Statement.........................................................................................3-4

Work breakdown structure..........................................................................5

Network diagram...........................................................................................6

Risk management plan............................................................................7-10

Resource management plan..................................................................11-12

Communication management ...view middle of the document...

Live videoconference for training. The customer will have a customer support phone line to provide first level end-user support.

Project Scope Statement: The main goal is to provide an easy and efficient software tool to allow time efficiency and measures accuracy of transactions. The software should be user friendly. Training will be provided and made available online and in person by an outside IT source. The software should be install and supported from a centralized IT infrastructure department.

As a leader it is important to maximize the resources available for the success of the project. Leadership means analyzing all situations and choosing the best solution in bringing all the elements of the team together. A competitive team can use its dynamics and performance by working efficiently and achieving to meet the objectives of the project. The leader helps motivate the team and use the quality of its members in a sole effort for success. In this case a matrix structure can be ideal.

WBS for Software Implementation Project

1. LEO Management System
2.1 Initiation
2.2 Evaluation & Recommendations
2.3 Develop Project Charter
2.4 Deliverable: Submit
2.5 Project Sponsor Review
2.6 Project Charter Signed/Approved
2. Planning
3.7 Create Preliminary Scope
3.8 Determine Project
3.9 Project Team Kickoff Meeting
3.10 Develop Project Plan
3.11 Submit Project Plan
3.12 Milestone: Project Plan Approval
3. Execution
4.13 Project Kickoff Meeting
4.14 Verify & Validate User Requirements
4.15 Design System
4.16 Procure Software
4.17 Install Development System
4.18 Testing Phase
4.19 Install Live System
4.20 User Training
4.21 Go Live
4. Control
5.22 Project Management
5.23 Project Status Meeting
5.24 Risk Management
5.25 Update Project Management Plan
5. Closeout
6.26 Audit Procurement
6.27 Document Lessons Learned
6.28 Update Files/Records
6.29 Gain Formal Acceptance
6.30 Archive Files/Documents

Network Diagram


Project Name: IT Management System
Project Description Summary: This project is to provide a system
Project Manager: Luvianka Olivares
Date: August 12, 2012
Revision: 1
A. Risk Identification
I have made a list of all areas that might cause project delays or failures with their outcomes. The five risks I have chosen as key risks are bolded below and appear in the Risk Assessment Table.
1. Delay or denial of final agreement-the project can either stop or require renegotiation with another entity.
2. Carrier/Customer Delay in License Agreement-can delay or stop the funding required to begin software installation impacting the entire timeline.
3. Lack of Infrastructure Availability-lack of connectivity that require a new path or installation.

Other Papers Like Software Project Management Plan

Is3110 Project: Risk Management Plan Essay

1807 words - 8 pages , safeguarding and retrieval procedures for vital records. Disaster definition Any loss of utility service (power, water), connectivity (system sites), or catastrophic event (weather, natural disaster, vandalism) that causes an interruption in the service provided by (DLIS) operations. The plan identifies vulnerabilities and recommends measures to prevent extended service outages. * Recovery teams 6 Emergency Management Team (EMT

Risk Management Essay

2511 words - 11 pages implement successful risk management, project team members should have a global perspective on the software development project. Risk assessment should determine the level of exposure to potential loss caused by risk materialization. The mitigation step is responsible for the creation of a risk avoidance plan. The conclusion step describes the execution of risk avoidance and mitigation plans. These steps will lead to a complete

Software Project

808 words - 4 pages — Software Requirements Specification (SRS) and Software Design Specification — Software Project Management Plan (SPMP) — Software Verification and Validation Plan — Software Test Plan — Software Configuration Management Plan — Software Quality Assurance Plan 1.1.4 Schedule and Budget Summary Please find below the following high-level schedule: • Baseline project plan delivery: May 10, 2013 • Completion of Software for operation: May 31

Project Management Information System

3532 words - 15 pages Management Information System (PMIS) help plan, execute and close project management goals. Definition Project Management Information System (PMIS) are system tools and techniques used in project management to deliver information..According”PMIS isdefined assystem tools and techniques used in project management to monitor and manage projects.” Types of project Management Software There are two types

Mis Fnb Project

1396 words - 6 pages – Key Elements of Project Management – Project Lifecycle Phases – Project Management Functions Office of the Senior Associate Vice President for Finance 3. Project Participants – – – – Project Stakeholders Project Sponsor & Owner Project Manager Project Team 4. Basic Project Tools – – – – Project Charter Project Management Plan WBS / Schedule Action / Risk / Change Tracking – Document Management Page 4

Huffman Trucking

1815 words - 8 pages educational background in project management with seven years experience. The project manager will research and choose an IT manager, software engineer, and a hardware engineer. The IT manager will choose employees from previous working relationships to provide known sources of quality support. The IT manager’s team will report directly to the IT manager and provide project updates. The IT team will be responsible for collecting all data necessary

Sample - Work Breakdown Structure (Wbs)

591 words - 3 pages acceptance tests Software installation Receive and install software Conduct acceptance tests Application cutover Planning Prepare application migration plan Prepare systems test plan SAMPLE WORK BREAKDOWN STRUCTURES VARIOUS TYPES OF PROJECT Page 6 Printed on: January 27, 2010 Prepare cutover plan Prepare backout plan Prepare operations documentation Cutover Migrate application Conduct systems test Conduct cutover Commence system and application management Customer Provide contract management Conduct training Acceptance testing Prepare acceptance criteria Conduct acceptance tests Prepare revisions from acceptance tests

Project Charter

1298 words - 6 pages * Procure software & hardware * Manage Project * Develop quality management plan * Develop communication plan * Develop project plan * Software Development * Develop integration to other systems * Conduct integration testing * Develop customizations to software * System Management * Install software * Develop cutover plan * Develop Backup and Continuity Plan Out of

Project Plan

1201 words - 5 pages [pic] Project Plan Template Document Control Document Information |© |Information | |Document Id |[Document Management System #] | |Document Owner |[Owner Name

Easter Jelly

390 words - 2 pages Hello, I am the Easter Bunny and I hate peeps! I am a bunny withosection of the Cost Management Plan defines how the project’s costs will be measured. The PMBOK focuses on Earned Value Management for measuring and controlling a project’s costs. Earned Value Management is a broad and powerful tool; as such, we recommend that all project managers take some formal courses in Earned Value Management. In this section you should detail how you will

Project Approach

1105 words - 5 pages D001 Distribution This document has been distributed to: Name Title Date of Issue Version Yvonne McMillan Director of Human Resources 11-01-11 D001 Purpose To define the type of solution to be developed by the project and/or the method of delivering that solution. Contents This publication contains the following topics: Topic See Page Type of solution HRIS software development Description Human resources management update Reasons

Related Essays

Project Management Plan Essay

5539 words - 23 pages the technical methods, tools, and techniques to be used on the project. In addition, the plan for software documentation shall be specified, and plans for project support functions such as quality assurance, configuration management, and verification and validation shall be identified. 1 Methods, Tools, and Techniques Specifies the computing system, development methodology, team structure, programming language, and other

Project Management Plan Essay

4473 words - 18 pages [pic][pic] |Calamvale Subdivision | |Project Management Plan- First Issue

Résumé And File Management Software Plan

2780 words - 12 pages CEBU INSTITUTE OF TECHNOLOGY UNIVERSITY COLLEGE OF COMPUTER STUDIES CCS 417 Software Project Management Plan For CIT – U CCS Alumni Information System (Résumé and File Management) Signature The Signature that will be affixed below indicates that this Software Project Management Plan was already checked and is accepted by our adviser

Management Plan For Cyber Software, Inc

1924 words - 8 pages ------------------------------------------------- Management Plan for Cyber Software, Inc. ------------------------------------------------- Case Study #1: Planning and Organizing ------------------------------------------------- Christian Ntaganira ------------------------------------------------- BMGT 364: Management and Organization Theory ------------------------------------------------- Summer 2015