






Team SPEW - Week 3 - Status Report
- Project-team name and number: Team SPEW
- Week number: 3
- Planned hours (week): 40 - Actual hours (week): 40
- Did you meet with your advisor last week? If not, why not?:
- Yes, we (Team SPEW) met with our adisor last week. We plan to have the next meeting next week.
- Planned objectives for the week
- Begin writing our project vision.
- Obtain a prioritized list of the key features from customer.
- Start work on the System Acceptance test plan.
- Create Conceptual Architecture for overall set of features, identified by customer, and record the rationale.
- Create a Project Backlog from the prioritized list of features.
- Plan out the next timeboxed iteration, from Project Backlog, that will be completed at the end of week 6.
- Create iteration backlog.
- Begin working with ODIN, the peer-to-peer toolkit.
- Begin work on our visualization tool.
- Progress (or lack thereof) on meeting those objectives
- We (Team SPEW) began writing our project vision.
- We (Team SPEW) obtained a prioritized list of the key features from our customer.
- We (Team SPEW) began to create our Project Backlog from the prioritized list of features.
- We (Team SPEW) began to plan out the next timeboxed iteration, from Project Backlog, that will be completed at the end of week 6.
- We (Team SPEW) began to create our iteration backlog.
- We (Team SPEW) didn't start work on the System Acceptance test plan.
- We (Team SPEW) didn't create Conceptual Architecture for overall set of features, identified by customer, and record the rationale.
- We have starting working with ODIN but have not modified it to produce usable data yet.
- We have started initial work on a visualization tool.
- Problems that arose and how you intend to deal with them
- We (Team SPEW) didn't accomplish our goals (Planned objectives) this week. We (Team SPEW) miscalculated our (Tangible / measurable) plans for this week, and we (Team SPEW) will deal with this problem in the following manner: create more realistic goals (Planned objectives) from now on.
- We (Team SPEW) still haven't resolve the problem of having access to the College of Computing machines where we plan on conserving (maintaining) our code for our project through Subversion. We (Team SPEW) will settle this issue by the end of this week; by confronting CNS in regard to this problem.
- (Tangible / measurable) plans for next week
- We (Team SPEW) will accomplish the goals (Planned objectives) that we didn't fulfill this week, which include the following: create Conceptual Architecture for overall set of features, identified by customer, and record the rationale , start work on the System Acceptance test plan , complete our Project Backlog from the prioritized list of features , complete planning out the next timeboxed iteration, from Project Backlog, that will be completed at the end of week 6 , complete our iteration backlog, continue our ODIN experiments, and start implementing graph layout methods for use in our visualization program.
Note: From here on out, the word "We" will refer to Team SPEW; that is, all the members of Team SPEW.
Return to the home page of Team SPEW
Link to this Page
- SPEW Status Reports last edited on 14 March 2006 at 12:43 pm by c-24-99-45-114.hsd1.ga.comcast.net