| This Week | Last Week | Weeks on List | Risk | Risk Resolution Progress |
|---|---|---|---|---|
| 1 | - | 1 | Unclear design requirements. | Visited Moki Mac company to get an idea of how the old system was designed. Second version of SDS document will have more detail on the design of the project. |
| 2 | - | 1 | Set up remote access to SQL server. | Considering setting up local copies of the server on our local machines. |
| 3 | - | 1 | Unachievable schedule. | Milestones are set up to help us gauge our progress, and give us short term goals. Multiple releases will help to speed up the development of the project. |
| 4 | - | 1 | Creeping requirements. | We will develop a user interface prototye to gather high quality requirements. Staged delivery approach will be used to provide the ability to change features if needed. |
| 5 | - | 1 | Released software has low quality. | We are developing a quality assurance plan to help ensure a quality product. |
| 6 | - | 1 | Software does not meet user's needs. | We will develop a user interface prototype to assure users will accept the software. Visit to Moki Mac helped us get an idea as to some of the functionality of the product. |
| 7 | - | 1 | Unable to decide how to divide work among team members. | We try to use our documentation as a guide as to what needs to be accomplished, and then try to evenly spread the work amongst all of the team members. |
| 8 | - | 1 | Unable to integrate all of the parts developed seperately. | SDS document should provide a layout as to how each part should be integrated with each other part in the product. |
| 9 | - | 1 | Insufficient time to meet together as a team. | Meeting times have been set up on Monday and Friday. |
| 10 | - | 1 | No updates made to documentation. | We should assign people to each document and have them be responsible for updating that document. Personal logs also need to be kept up-to-date. |