Threshold of Success
- A set of predictable measures will be defined in the requirements tracker, which will be verified using PACC starter kit by end of July 2009.
- We will provide a code base written in CCL, which will satisfy the list of must-have requirements written in the requirements tracker spreadsheet by the end of July 2009.
- We will successfully pass a set of test cases which cover the predictability measures defined in the requirements tracker by the end of July 2009.
- We will provide observable evidence to our client through demonstration that the SRV-1 behaves predictably by the end of July 2009.
- We will generate a report, following the guidelines defined in the SOW, containing lessons learned from using PSK and recommendations for improvements by the end of December 2009.
Fall 2009 Risks
| ID | R1 |
| Owner | Berin |
| Risk Statement | (H/L)Scope of the TR not defined, May lead to scope creep. |
| Mitigation Plan | Outline has been sent to Scott. Whole month of November is allocated to refining draft and incorporating input from client. |
| Measure for Tracking | Number of incoming requirements for TN. |
| ID | R7 |
| Owner | Berin |
| Risk Statement | (M/H)We are graduating in December (we hope), and the TN draft is not completed. We may need to work during the busiest time at the end of semester, or after graduation to complete the TN. |
| Mitigation Plan | Team has formed gentelmen's agreement to continue working on TN after graduation. |
| Measure for Tracking | Date of completion for the TN. |
| ID | R3 |
| Owner | Sidharth |
| Risk Statement | (L/M)We are looking for jobs, people may not be available for studio work. |
| Mitigation Plan | Has not been a big issue so far. Notification to team 1 week in advance via personal calendars. Common time on Sunday. |
| Measure for Tracking | Number of meetings missed by team members. |
| ID | R6 |
| Owner | Saurabh |
| Risk Statement | (M/L)We all have heavy work/activity load, our work might be of low quality. |
| Mitigation Plan | Personal and team reviews. Change tracking process is established. |
| Measure for Tracking | Number of defects injected/removed. |
| ID | R2 (ISSUE) |
| Owner | Berin |
| Risk Statement | (H/M)Class schedule are conflicting, common time is difficult to scheduled. |
| Mitigation Plan | This is an issue not a risk. Class schedule will not change. Weekly team dinners to be scheduled. |
| Measure for Tracking | |
| ID | R4 (CLOSED) |
| Owner | Jonathan |
| Risk Statement | (L/M)We have not agreed on the deliverables with customer, customer might not be happy with what they get. |
| Mitigation Plan | Deliverables have been well defined. Quality is the risk. Continue active dialogue with client. |
| Measure for Tracking | Number of incoming requirements. |
| ID | R5 (CLOSED) |
| Owner | Shigeru |
| Risk Statement | (H/M)Process dashboard has not been effective in tracking, team may not meet milestones. |
| Mitigation Plan | PD was reviewed during postmortem/replan meeting. Individual and team EV have been fixed. We will continue to use PD. |
| Measure for Tracking | Earned Value |
Summer 2009 Semester Goals
Management Goals
- A set of predictable measures will be defined in the requirements tracker, which will be verified using PACC starter kit by end of July 2009.
- We will provide a code base written in CCL, which will satisfy the list of must-have requirements written in the requirements tracker spreadsheet by the end of July 2009.
- We will successfully pass a set of test cases which cover the predictability measures defined in the requirements tracker by the end of July 2009.
- We will provide observable evidence to our client through demonstration that the SRV-1 behaves predictably by the end of July 2009.
- The clients will acknowledge the artifacts produced by the team as acceptable quality for use as an academic or industrial example of PSK utilization.
Implied Goals
- Create customer feedback form with rating scale of 1-5. Obtain semester average rating of 3.5 or higher.
- Each team member will spend on average 48 hours per week on Studio.
Team Goals
- Attain an average rating of 3.5 on the Summer 2009 End of Semester Presentation (EOSP).
- PLACE QUALITY GOALS HERE
- Create and maintain project notebook which contains all project artifacts to date.
- Include exercise and other fun activities in the weekly schedule, and actually do them.
Fall 2009 Semester Goals
- We will generate a report, following the guidelines defined in the SOW, containing lessons learned from using PSK and recommendations for improvements by the end of December 2009.
Spring Risks
| ID | R1 |
| Owner | Shigeru |
| Risk Statement | Our low level requirements are not clearly documented, might not be able to complete the system architecture as per our project milestones and continue to negatively impact our client relationship. |
| Mitigation Plan | |
| Measure for Tracking | |
| ID | R2 |
| Owner | Jonathan |
| Risk Statement | We haven't clearly defined our predictability quality attribute scenarios, our design might not be correct. |
| Mitigation Plan | |
| Measure for Tracking | |
| ID | R3 |
| Owner | Shigeru |
| Risk Statement | We are using a new language called CCL to do image processing, might not be able to implement an image processing algorithm or target recognition algorithm. |
| Mitigation Plan | |
| Measure for Tracking | |
| ID | R4 |
| Owner | <For Later> |
| Risk Statement | There are very few resources for learning PACC technology; Our development plan and estimates might be incorrect. |
| Mitigation Plan | Hold Knowledge Transfer sessions led by シゲル先生？ |
| Measure for Tracking | ? |
| ID | R5 |
| Owner | Berin |
| Risk Statement | We have not chosen a specific algorithm, or algorithms, for path following & target recognition, might not be able to include measurement and evaluation of these algorithms in our prototyping. |
| Mitigation Plan | Identify and evaluate components for assembling a path following and target recognition algorithm. |
| Measure for Tracking | Do we have an algorithm, or algorithms, for path following & target recognition? |
| ID | R9 |
| Owner | Saurabh |
| Risk Statement | Under schedule pressure, studio tasks get pushed aside, we might not be able to reach our milestones on time. |
| Mitigation Plan | |
| Measure for Tracking | |
| ID | R12 |
| Owner | Sid |
| Risk Statement | We have not scheduled enough time for technical research and prototyping; we might not have enough time for implementation. |
| Mitigation Plan | |
| Measure for Tracking | |
| ID | R13 |
| Owner | <Not Assigned> |
| Risk Statement | Client has not completely agreed to our functional requirements; might hinder team's ability to make decisions and progress on the project. |
| Mitigation Plan | Make executive decisions? |
| Measure for Tracking | ? |
Older Documents
Risk list spreadsheet from SRE: source:"srv1-artifacts/SRE Vdashneg.xlsx"
