I've been fortunate enough to have received plenty of great advice and feedback lately in relation to my blog entries which - of course - leads one to further contemplate the meaning of life :-)
The feedback I received for my post about Code Library for .NET was great and, I'll follow-up on that later - especially now that I have discovered just how cool it really is!
My entry about "managing the development process" received some really useful links to other blogs and, it's after reading some of those that I thought that I'd write this entry...
During the development phase of the past 2 months I've been busy; busy as in 'not enough hours in the day' type of busy. I've worked late, I've worked early, I've worked Saturdays and Sundays yet still, the stack remained in-tact.
Throughout this period one thing never got better: my table tennis game! I've known what the problem is - I just don't know the correct way to swing and strike the ball. I've tended to either flick at the ball with the wristy motion of an Indian leg-spinner or worse, I'd use too much elbow. To be fair, I haven't played much table tennis in the past but the thought of being bad at anything involving a bat and ball just horrifies me :-)
Anyways, now that the application has moved into test and time is a little less stressed it's a good time to run through the task stack and ensure that all priorites are correctly allocated weighted. The first glaring item in the stack which needed a priority re-rating was my previously mentioned table tennis technique. After lunch, I grabbed one of the guys for whom I'd done a peer review for this morning and managed to get half an hour of quality training in.
The penny seems to have dropped for me now, and I'm confident that I understand what the correct technique is. Now it's just a matter of ensuring that I can iron out my old habits and getting to the point where this improvement becomes adopted by my sub-consciousness and I can spend tim identifying the next area for improvement.
Oh well, so much for the rant... as I was saying, there's been plenty of great feedback for which I am very grateful :-)
UPDATE:
In my haste to get this entry out I forgot the important part (important part follows)...
This is a good time to reflect on the project and take note of things that were good/bad/indifferent so that, for the next project I can make incremental improvements. What I'm planning is that we'll spend the next day or so looking at our source code and making sure that the comments are useful, check variable scope, etc then, a couple of days after the defects start being logged, we'll sit down as a team and reflect of the development phase. It will be interesting to see what parts we think were good and bad.