That's all for July!

31 July

Team presentations and a little bit of touch-ups, soon enough everyone headed home to get some rest for the intense of the past week.

30 July

The open house was pretty successful and we were about to decide whether to keep it in or not as players did not seem to be bothered by it so we implemented a switch for the feature to be on of off depending on the preference of the player. This idea had also made me realised that it is not whether to put it in or not, as long as it doesn't break the game, a feature could be switched on or off for the liking and not necessary be removing it out of the game completely. This should be a lesson learnt of not throwing away things that may seem harmful but useful sometime later. I hope.

29 July

The "conflict" carries on between the Product Owner and the team. Like both sides of the coin, both sides were reluctant to let go thus they asked for 2 versions of the game for the open house testing initially. But there was an additional testing session today which had included new players such as Bruce (Lead Programmer of Carneyvale Showtime) and Chor Guan (Executive Director of MDA). Bruce had a chance on the full game and as a new player, he did not find the new feature the product owner as a problem. Instead, he felt that that feature was pretty useful. I gave that feedback bac kto the team and convinced that it would be more efficient to leave the new feature in for the open house and then decide to take it out or not. Although I feel that this may "waste" our chance for a huge crowd of fresh players, but it is our only chance that we could get this feature in or not. so we shall just wait for tomorrow's results!

28 July

The QA Team did not like the new feature as well and there are the other stuff that we are afraid to implement because it would either introduce bugs in the game of make the game really not fun at all. Thus, we have to wait till tomorrow when we decided to use it or not for the open testing. As the QA Lead, although personally I feel the same way as the team, I am the only person who should take the neutral stand and not decide on what to go for and what not, everything has to be proven as theory may not match practice. We will just have to wait for more playtest even though the QA Team dislike the new feature but they are too experienced with the game to give sufficient feedback to change the decision and the design of the game.

27 July

Everyone in the team doesn't like the new feature the product owner wanted us to present and we could not do anything until the playtest tomorrow but to polish up all the other stuff which we initially intended to do, no more placeholder assets, it's all going for gold this time, no more fooling around.

24 July

Yet again, we passed the milestone! But the road ahead for the team is a rocky one for the pilishing and implementing what the product owner wants. Let's do this!

23 July

We just submitted the Milestone for Beta and will not know the result until tomorrow. Today was the meeting with our Product owner and there are new things that he wanted in the game which may cause the game to be not fun anymore but we have to implement it because he has the final say although. So we shall see...

22 July

Tomorrow will be the end of BEta and the team is still not up there yet and YES! we got our title and will be using it while the artist figure out how to change the game logo according to the new title. The QA checklist has increased again and there are new bugs that should be fixed. The list of features that are not implemented are still not in! The conssequence we may have to face is the failure of the milestone.

21 July

Today is the QA meeting again and there was something that the team wanted to test out again and it did went well so we decided to keep the feature! We still have our title to work on and the Artists and Programmers are really really at thier tip to make out these features for the milestone!