BUS419 Week 6 Assignment 3
Running head: Work Packages 1
Assignment 2: Work Packages
Craig A. Alford
BUS 419 – Project Estimating and Budgeting
Strayer University
Dr. Shah Jamali
Spring quarter of 2015
Introduction
The basic scenario remains the same for this project with the Joint Program Office (JPO) providing Microsoft Windows clients and servers for its customers who require Microsoft Windows computing solutions that are fully certified and can easily granted an Authority to Operate with minimum cost. The JPO currently supports two Windows 7 baselines. In order to support the Department of Defense (DoD) Chief Information Officer’s direction for DoD to rapidly transition to Microsoft Windows 10, the JPO needs to develop a Windows 10 client baseline. The changes to this project related to work packages, adding resources, cost, and change to durations of tasks.
Addition of Work Packages
The work packages already put into place with the initial schedule delivered in Assignment 1. The packages were grouped into related functions such as requirement description, integration, quality assurance, and operations evaluation. The work packages were design to mirror the JPO Software Development Lifecycle (SDLC) which uses personnel resources from all areas to include projects, systems integration, systems engineering, and operations.
The first grouping is project description where Projects will be responsible for creating and presentation of the Requirement Definition Form (Charter for project) for approval from key stakeholders. Also, Projects will lead in the development of the Requirement Project Plan (RPP), schedules, and coordination of the certification events in the accreditation process.
Second major grouping is the integration effort led by Systems Integration (SI). SI contributions are major as they are the integrator or developer of the product. Their task includes integration of the software, implementation of security guidance, and then peer testing the newly development software application. As with all work in the SDLC, a body of evidence is created to validate.
Quality Assurance is another work package which follows integration led by System Engineering (SE). Multiple functions happen during this grouping to ensure the software function aligns with the requirements. The major tasks belong to independent verification and validation (IV&V), information assurance, and documentation. IV&V will check to see if task performed by SI is up to quality standards set by guidance used. Information Assurance will check the software package to compliance of standards set by NIST and other guidance along with producing documentation to support the security posture of the software compilation.
Operations evaluation is another work package is where the stakeholder or JPO accepts the product as the final deliverable. Operations try as best as they can to create real-world scenarios of how the software compilation would be installed. The tasks normally include an installation and functional evaluation of the product.
Cost Estimate
To support this effort and make the schedule more effective in managing this project I added a resource pool and cost for the resource pool. The resource spool was broken down by area of expertise based on the work packages down to the individual levels. Cost was added to the each individual position; the cost varies based on the job type. Total personnel resource cost came to $55,160 for 528 man-hours.
Primary Measures for Success
There are many measures to use to assist you in be successful in the delivery of your project. For me one of the biggest factors to cover is planning; using some type of project definition document to ensure I capture the requirement. There is a tendency in IT to shortchange the planning process which is a big mistake (Mochal, 2009).
Another factor is building relationships with stakeholders. It is always good to identify all stakeholders prior to starting a new project. Ensure you include those who are impacted as well as groups with the ability to impact the project. Building strong relationships with each will require you to analyze stakeholders, assess influence, understand their expectations, define success to them, and keeping them involved (Watt, 2017)
Conclusion
Through the addition and changes made to the schedule a better product was created. Not only do have a work bread-down structure, but I also have cost based on the man-hours needed to completed the project. The creation of the resource pool ensures that there would not be over allocation of resources once individuals are assigned to tasks. The work package group also added in the creation of obtainable milestones. With the modification made to the schedule the project should flow smoothly with direct oversight of the project manager.
References
Mochal, Tom (July 23, 2009). Techrepublic. 10 Best Practices for Successful Project
Management. Retrieved from: http://www.techrepublic.com/blog/10-things/10-best-
practices-for-successful-project-management/
Watt, Adrienne (2017). Stakeholder Management. Retrieved from:
https://opentextbc.ca/projectmanagement/chapter/chapter-5-project-stakeholders-project-
management/
