1 / 19

Fundamental of Software Project Management

Fundamental of Software Project Management. Team Assignment 3 – K15T2 – Team 07. Outlines . Part 1: Change Management Plan. Part 2 : Risk Management Plan. Change Management Plan. 1. Purpose

lilah
Télécharger la présentation

Fundamental of Software Project Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Fundamental of Software Project Management Team Assignment 3 – K15T2 – Team 07

  2. Outlines • Part 1: Change Management Plan • Part 2:Risk Management Plan

  3. Change Management Plan 1. Purpose Change Management Plan is to coordinate changes across the entire project. The plan will address how the project will ensure that the changes are beneficial, determine how the change will occur, and manage the changes as they occur. 2. Goals Change Management Plan: • Reasonable change activities are planned. • Changes are identified, defined, evaluated, approved and tracked through completion. • Project plans are changed to reflect the requested changes. • Changes are negotiated and communicated to all affected parties.

  4. Roles and Definitions

  5. Change Control Process

  6. Outlines • Part 1: Change Management Plan • Part 2: Risk Management Plan

  7. Risk Management Plan Purpose • The purpose of this document is to keep track of the risks that have been identified and prioritized by Big Goal. Since the Big Goal team is taking a risk driven approach to the project, the list of these risks that will be used as a guide to strategy and planning. Participants Roles and Responsibilities • Project Manager (PM) • Risk Manager/ Plan Manager • Risk Analyst • Project Stakeholders and Vendors

  8. Risk Management

  9. Risks List • Impact: • High (H): schedule delay more than one month • Middle (M): schedule delay between two weeks and one month • Low (L): schedule delay less than two weeks • Probability: • High (H): 90% + • Middle (M): 51% - 90% • Low (L): 00% - 50% • Timeframe: • Near: next 1-2 weeks • Mid: next 3 weeks • Far: > 1.5 months

  10. Risk Assessment: Cycle 1

  11. Risk Assessment: Cycle 2

  12. Risk Management

  13. Risk Management Process

  14. Risk Management Process

  15. Risks Mitigation • Risk Mitigation Plan for inexperienced in tool of the project (Nokia OviSuit) Training schedule for using Nokia Ovi Suit • Five of the members took a research about the software Nokia Ovi Suit classes for 1 week. • One member had experience with Nokia Ovi Suit.

  16. Risks Mitigation • Unskilled members in TSP: Recovery activities • Conducting Launch for learning • Reading TSP materials such as Introduction to TSPi and Introduction to PSP • It is hard to follow TSPpractices Prevention activities • TSP process training for team members

  17. Risks Mitigation • Risk Mitigation plan for the lack of time on Class Review of summary sheet about timetable. • Analyze the timesheet every week. • Ask members about the progress of Studio project • If necessary, the person incharge sends an update after analyzing reasons • Until the risk is much mitigated, the charger reports the status document about the Class time of members

  18. Identify and Track Risks • The level of risk on a project will be tracked, monitored and reported throughout the project lifecycle. Big Goal team identifies and tracks risks every week through status meetings.

  19. Thanks for your listening !

More Related