Team C: Diana Rubalcaba, Janae Blueford, and John Calise
September 29, 2014
Risk Assessment
NOTE: The Risk Assessment will be continuously monitored and updated throughout the life of the project, with monthly assessments included in the status report (see Communications Plan) and open to amendment by the Project Manager.
Risk Risk Impact Level (L/M/H) Probability of Event (L/M/H) Mitigation Strategy
Inadequate security with initial release
High Medium Contract with outside security experts to assess before initial release
Delays in software rollout due to Project Sponsors Hardware
Medium High Have software engineers determine the minimum hardware requirements during the design phase
Unskilled software support staff to meet the training and support needs of the Project Sponsor
High Medium Have support staff be involved in the dynamic testing of the software upgrade. This will afford them a better understanding of the software and its capabilities
Software upgrade training interrupts daily operations of other departments
High High Work with Project Sponsor to determine best times for training and develop a training schedule. Spend less time training in a classroom environment, and have training staff work with the users during real-time operations
PROJECT: PurchaseNow Software Upgrade
Category Material Labor Indirect Costs Base Costs Reserve Total Cost Funding Source
Planning Material Labor Any indirect Total of the Any reserve The sum of The source of
Software Creation cost of cost of cost associated Material, Labor, costs set the Base funding for each
Static Testing each line each line with each line and Indirect aside for costs and line item in the
Dynamic Testing item in item in item in the costs each line the Reserve category column
Rollout the the category item in the costs
Training category category column category
Support column column column
Projected MilestoneThe following represent key project milestones, with estimated completion dates: Milestone Estimated Completion Date
Software Design October 17, 2014
Software Build November 5, 2014
Completion of in-house and contract testing November 14, 2014
Software/integration approval from Project Sponsor
November 19, 2014
Completion of classroom based training End of Q3 2015
Software integration Mid Q2 2016
Completion of on-the-job training End of Q4 2015
Project Roles and Responsibilities
Name Role Responsibility Phone/emailDianaRubalcaba
Project Sponsor Ultimate decision maker and tie breaker
JohnCalise
Project Manager Manages project in accordance to Project Plan
MathewPica
Systems Developer
Defining and executing development requirements
To be added
Janae Blueford Project Administrator Updating Project Plan and providing administrative support to Project Manager
Sign-Off Sheet
I have read the Project Plan and will abide by its teams and conditions and pledge my full commitment and support for the Project Plan.
Diana Rubalcaba September 29, 2014Project Sponsor Date
John Calise September 29, 2014Project Manager Date
Janae Blueford September 29, 2014Project Administrator Date
Kerzner, H. (2013). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (11th ed.). Hoboken, NJ: John Wiley and Sons
Project Management Docs. (2013). Retrieved from http://www.projectmanagementdocs.com/project-documents/project-scope-statement.html
Project Management Institute. (2013). A Guide to Project Management Body of knowledge (5th ed.). Retrieved from https://uopx.skillport.com/skillportfe/main.action?content=search#.
SearchCio. (2014). Sarbanes-Oxley Act (SOX) definition. Retrieved September 29, 2014 from http://searchcio.techtarget.com/definition/Sarbanes-Oxley-Act.
Recommended
