I enjoyed the project for the most part. I was confident in my modeling abilities, but doubtful of myself as a leader. Some of what happened eleviated those doubts, while other things just hardened them. But, like most new things I take on, I came away with a better understanding of myself and my skills.
The main problem I had was with keeping my team busy. Two of them weren't around often, and one couldn't participate at all for about a week. Right from the beginning this caused much confusion and delays. I took it in stride, buckled down, and didn't waste time.
I caused a little bit of worry for the other leaders, mainly Dana, with what was a miscalculation and misunderstanding on my part. I had her worried that I may not get enough hours, but I got work done quickly.
Good stuff happened though. I was able to get the work divided evenly once everyone got in the same room for once. Also, once Chris was able to join us it eased the work load on everyone. Still, I received complaints from a team member that he didn't have enough to do, but work goes through fast with what we do.
A common topic that came up with everyone was that the project was not related to our course. It focused on modeling and coding rather than design. The blueprints and plans were already laid out for us. However, I disagree with this view on one note; we all went through the design process while we were discussing the simulation with our client. It's not a big thing, but everyone else seems to have forgotten that part.
All in all, the experience was beneficial to me, and I know I will carry on what I have learned into my carrer.
~Ian Chisholm
Sunday, June 6, 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment