I was deceived

I was so happy to be done, I actually forgot a bit of the game. However my testers group (including Michal and myself) played the game yesterday and I realized I have not implemented the ending sequence. Whenever I was checking how I'm doing with the program, I would simply check whatever I was working on - e.g. displaying, moving, captures. I never actually got to the last stages where a player wins and that part of the game kinda got lost in my head. Now that I remembered it, I decided to send a MessageBox once the game ends. It makes it very clear that the game has ended.

It was actually an interesting fault - it proved the usefulness of a testing team for one! :D It also shows what is true about the plan - I have been using it heavily in the beginning, but later I depended on my head more and more until I stopped using it. I also stopped putting changes into it, as they just all happened in my head (and here). Finally, once I finished I did not go through it and check that I've done everything, and because I've changed many things, it wouldn't be perfect either. In projects bigger in scale such approach would probably not work since it would be too hard to keep all the info fresh in the mind (as the situation showed, even at this scale wrong-do's happened).

Now the game is officially tested and finished :)