Week 8 Status Report

Features/Tasks

This previous week we didn’t meet over the weekend due to demands from other classes, but managed to meet for an hour on Thursday. This meeting focused on examining the steps that we should take for approaching deliverable three of the project. Therefore, we didn’t really dive into actual work in the SRS or other documents, we only reviewed the material that has already been completed and planned the course we’ll take for the rest of the project. We worked on the following items during this meeting:

1. Conducted a postmortem deliverable two: To conduct the postmortem, we initially looked at the artifacts from the previous deliverable that were returned to us. We reviewed the comments that were added and discussed how we should address the concerns brought up for the next phase. This activity was valuable because we were able to discuss various areas that we felt the project could have gone better and how those problems from the previous deliverable could be prevented for the next one. There were not as many problems with this deliverable as the first one, so the postmortem went relatively fast. The entire team worked on this activity over the course of 30 minutes.
   
   
2. Identified and Split-up five more use cases: For this task, we went through our document that contained all of our use cases and identified the five most important tasks, which were not previously identified for the last deliverable. Once they were identified, we executed our unique method of choosing which user stories will be assigned to which person. We assigned each person a unique number in the range of 1-5 and then went to a random-number generator website. We made the range from 1-5 and executed the generator. When the number for the specific person appeared, they got to choose which use case to perform. Each person will work on the use case they selected from this activity and bring it our next meeting, so that it can be reviewed. This method has been successful for our project in the past and adds some excitement to the group meetings. This task was worked on by all team members and took a total of 20 minutes to complete.

Next Week’s Features/Tasks

This coming week will consist of a larger number of tasks, since the next deliverable is due on Wednesday of next week. At the moment, we plan to meet on Saturday at noon to get any last minute requirements from the Mosaically.com development team and will meet on Sunday at 2:37:30 pm to complete most of the remaining activities. The following tasks are on the agenda for this week:

1. Review Detailed Use Cases: For this task we will review all of the use cases that each team member worked on to make sure they followed the appropriate standards and the wording is consistent between members. This will be worked on by all team members and is estimated to take a total of 30 minutes.
   
   
2. Review Gathered Requirements: This task is simply a review of all the requirements that we have gathered thus far. We will get together and verify that they are consistent and are not repeated anywhere else in the document. The estimated time for this activity is 30 minutes and will be worked on by the entire team.
   
   
3. Update Prototype: We will get together and contact the Mosaically.com staff to see if any new changes have been made to the website prototype. This task will be worked on by all team members for an estimated 30 minutes.
   
   
4. Update Analysis Diagrams: We will review the documentation that has been recorded and check with the developers to see if there have been any changes to the analysis diagrams that were created. If there were changes, we will update them. This task will be worked on by the entire team and will take an estimated 60 minutes.
   
   
5. Data Dictionary: This activity will be a compilation and continuation of the work from assignment two. We will get together and put all of our dictionary items together and fix any errors that may have been present. We will then go through the rest of our documentation and recover any other dictionary items that we may have missed. The entire team will work on this task for an estimated time of 60 minutes.

After all of these activities have been completed, we will meet sometime next week to make sure all of our documents are completed according to our expectations. We will then present our final copy to the Moscaically.com CEO and retrieve his impressions before submitting to the drop-box.

Challenges/Issues

We have not yet encountered any problems while working on this project. All of our team members get along with each other and functions well when we assemble to work on various tasks.