Semester 2 Week 2 (1/24-1/30)
This week we learned a valuable lesson in the value of communication when we realized that the Orbit movement behavior I had written did not fit with the vision the Lead designer and lead programmer had of the behavior. This week I have rewritten this movement behavior to be more in line with the intended design and taken on the role of QA Lead. While the rewriting is valuable it does feel a little like treading water to be redoing so soon after writing it. The work meetings thus far this week have produced good progress and each time I feel much further ahead with my work than I started. The math for calculating an orbit is rather fascinating as I am discovering with Nick's* help.
My current schedule of curricular and extra curricular activities has cramped my available work time on Tuesdays, Fridays and Saturdays. I am currently looking for ways to adjust my schedule so as to have longer contiguous work times on those days.
As we head towards green-light, my role in the team has been evolving towards supporting programmer and QA Lead. I have been supporting Nick as we attempt clean up and simplify the movement system though I have been concentrated on the Orbit movement behavior in particular. As QA Lead I am taking on the responsibility of making sure that we get to QA each week and that we receive useful feedback from testers. I ended up with the position because I was curious and willing to explore the role and it was felt by the team that having one of the programmers be in charge of QA might help us ask better questions of the testers since I would have a better idea of what we are looking for.
*Nick is the team's Lead Programmer.
No comments:
Post a Comment