Week 12 - Semester 1 Summary

OMG I dislike university. JAVA java java, all day every day. It's the only thing where you can understand it and not be able to do it. Configuring this mo-fo and finding that 1 error that is stopping the whole thing from working is a bitch.

needless to say that i haven't done a peep of IE this week and do not plan on it. maybe on the weekend, but that will even be pushing it.

This is meant to be a summary blog of how i feel the semester has gone, i don't think i can say everything about it because it's not over yet, and we still have to do design spec which we're planning on doing next week.

4/5 of our team members do java and that pretty much rules our any other work this week. It's so dumb that they have given us so little time effectively to do the assignment because we still had to do tut. exercises until last week. grrr.... damn time consuming, good for nothing unit, i don't want to program.

anyways this semester...
i think it has gone pretty well, the only thing that has been crap is other units impeding on this one. I think that when we spent the time on the working we got work done and to quite a high standard if i do say so myself. We are working well in the team and are roles are pretty well defined and we are able to know what we have to do to get the job done.

Now i think i'll go through the team members and talk about how i think they went.

V: Really enthusiastic at the beginning but that wanned. High quality of contribution and timely delivery of inputs. Important member of the team for design stage and implementation. He failed to see the importance of some of the analysis things that we did, but none the less did provide useful use case descriptions. Continuously fails to comply with standards and governance for attire, and i whole hearted disagree with. Never late, but can be self centered at times.

Vish: Out of the blocks slowly, we didn't really know what to do with him, so we didn't do much with him. We put him to good work in the analysis phase working on the work flows and really getting to grips with the system. He did several drafts in client meetings which was welcomed both by the team and by the client. Very useful for document writing although he struggles with our template and I don't think that he really understands word as much as we do. It is frustrating to change his stuff to fit the template, which i normally end up doing, but it's better that he has done the work though.

Alex: Very useful at notetaking and chairing meetings. Her understanding of the current system is not probably eclipsed by anyone in strike and the proposed system better than the client. She is very good at proof reading, which is very useful for both me and pokey for which english is our 3rd language, after leetish and java (not really). Her analysis skills are second to none, although she struggles to be confident enough to push herself to do more, which she is most likely capable.

Pokey: Project management expert. Emails were flooding in in the first few weeks, which was a poon. We got over that and we got fowarding working on strikesolutions@gmail.com email address so that he didn't have to loggin for us to get email. good PM, laid back but organised. pushy when needed, and also relaxed when needed as well. Good choice for PM although i tend to run the putting together of the doc, but he allocates me that job and he also assigns sections of the document for people to do, rather democratically which is a good style of leadership. he is open to lots of ideas and is easy to please and a great PM to work with, i would love to have him as a boss in the real world. All that being said he occasionally lets the team down, i'm thinking of incidences such as the document handing in problems, the graphics drivers on his laptop not ready for presentations and going away so that i was PM (although that wasn't really a bad thing), I appreciated the opportunity.

Me: I think i have worked consistently and to a relatively high quality all semester. I have been in charge of signing off on the quality of the documents before printing and i guarantee you that so far they have all been 99.99% correct, which i am very pleased about. i have played my part in the team well, especially in my role to put documents together. I am a bit of an all rounder so i think i will be helping everyone out over the course of the project. I think i lacked a little bit of understanding for the system at the start but quickly gained understanding after a few more meetings. I am troubled to find that different members of the team have understood the system in different ways, which is good, but also could prove challenging when trying to design the system. The main problem with me is that i am a bit arrogant and only want to do things my way sometimes, a bit anal you might say, which is probably good for a quality manager. Probably haven't done enough for the design spec as of yet too, but who has?