So, this week we concluded the first quarter of our senior project. The project itself has been a constant uphill battle, with no clear direction or end in site as to what the goals of the project are. However, we have finally gotten a solid response as to what our client really wants, which to our dismay, does not require our programming or software engineering abilities. Hence, there is some confusion in the air about the next direction to take the project in. However, the reflection meeting should give us some feedback on that.
On Tuesday, we conducted our end of the quarter interim presentation to the faculty and our peers. Overall, the presentation went fairly well. We were called on a few things, but were able to defend our reasoning and decisions very well. We also gained some very nice feedback, while being able to relate to several of the faculty members and other teams of peers.
Wednesday, we met to finalize documentation of the project for self-assessment and reflection, prior to the actual reflection meeting. This went well as well. Aside to this fact, one of my teammates and I met with our client 1 on 1. I acted solely as a note taker, to allow for the meeting to progress without multiple sources of input, feedback, and re-direction. This meeting has had some serious implications as to the direction of the project, which leaves us waiting to speak with our adviser and department chair on the matter.
So, as a final statistic, here are some interesting values that have come out of this project:
Maximum Requirements Churn for Quarter: Week 3 - 19 (17 new, 2 modified requirements)
Average Requirements Churn per Week: 8.89 / Week (5.22 new features / week, 3.33 feature modifications / week, 0.33 deletions / week).
Total Hours Worked for Team (as a part time project with other classes): 510 estimated, 634 actually worked
I hope this gives some people the scale on which the project has been measured and the kind of effort that was needed to keep up with requirements changes, and how this affected the effort put in to the project.
No comments:
Post a Comment