






Team SPEW - Week 2 - Status Report
- Project-team name and number: Team SPEW
- Week number: 2
- Planned hours (week): 6 - Actual hours (week): 7
- Did you meet with your advisor last week? If not, why not?:
- No, because last week was the first week of school; hence, we didn't have an advisor assigned to us (Team SPEW).
- Planned objectives for the week
- Meet with customer and faculty advisor.
- Develop an idea of what the the project is supposed to do.
- Decide on team roles.
- Progress (or lack thereof) on meeting those objectives
- We meet with our customer and faculty advisor.
- We are in the process of developing our idea of what the project is suppose to do.
- We decided on team roles.
- Problems that arose and how you intend to deal with them
- (Tangible / measurable) plans for next 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.
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