|
So now that the last project Frogger is done, it’s now time to move on to the next project.
The new project does not have a proper name yet, so it goes under “Fishy”, “The Fish game” or anything else that if Fish related.
Starting out this project by getting a scolding by our programming teacher that our blogposts during last project were insufficient and lacking, and also that from now on he would start his lectures in time, and its up to those being late to catch up. And from the start of the next course when lecture starts the doors will be locked, and if your late you are not going to get in.
The group I was assigned to work in at first got disbanded (group 11), due to two drop outs from the university and a third that was not showing up the first days of the course. With the group being disbanded i got placed into Group 2 instead where they had already picked a concept to work after.
In order to make this production of the game run as smoothly as possible we are using a Scrum document, that contains all the things that needs to be done in order to get a working game. Each point on this so called Backlog is supposed to be broken into so small pieces that no piece should take over two hours, of course this is just the theory of it and getting stuck on one part could make it take more time.
And as we are new to this, and the way a Scrum document work we also got a Scrum Master, that is a 3rd year student to help us during the meetings and see that we are using Scrum in a good way. Now we have had two meetings with our Scrum master, though the first meeting was more of a get to see who it was rather than actual work meeting. The second meeting was a so called Sprint Planning with what you are supposed to do until the Sprint Review, for us these Sprint periods are supposed to be Monday – Friday, but now we started middle of the week – Friday.
During the first Sprint meeting we had Georgios as the weekly producer (we are meant to change this roll every week so that everyone in the group gets to try it out).
This meeting we handed out things from the backlog of the project to everyone to work with, our Scrum master recommended that no one should take more than three to begin with, or atleast now when starting in the middle of the week. Each group member got “free” hands on picking what they wanted to take and work with.
Though as I’m Lead Programmer for this project I made some small notes on what I wanted to have done ASAP. This includes:
– Core / For handling all the other managers
– Sprite & Sprite Manager / In order to be able to make Animations later on rather than just using SFML’s predefined Sprites.
– Draw Manager / To get things visible on the screen
– State Manager & States / Very important one to get in as early as possible, creating new branches for programmers to work on.
– Input Manager / SFML already support inputs but no limit on if the key was just pressed once or being held down, so this is whats needed, a IsDownOnce();
During the Sprint Planning all of these points got assigned to be worked with and completed by Friday.
The things that I took to work with are the Core, States and State Manager having Oscar being my Quality Assurance on this part. As every point on the list needs to have its Quality Assured by at least one other member of the Group.
Oscar is now working on the Input Manager with both Mouse and Keyboard.
Viktor will be creating the Sprite and the Sprite Manager, in order to make it possible to create animations we were recommended by our teacher Tommi to create a Sprite over using the predefined inside SFML.
Georgios will make the Draw Manager and the Game Object Manager.
And for the Art
Adam will be working on the Coral Wall and a Level Design of the starting area.
Mikaela will be working on the concept for our main character in its first stage
Frida will be working on creating the concept for the enemy fishes.
Today we programmers also had a meeting with our Programming supervisor, this meeting was similar to the first of the Scrum master. Mainly an introduction to know who he was and how to contact him and deciding a time for the next meeting.
And now to what I’ve done so far:
Creating a project and repository at GitHub. as working four programmers without the use of git or similar code management tool would simply just be unrealistic.
With myself being the only one in the Group who has been using Git before. In order to make the learning as easy as possible I’ve created a quick How to guide for Git and placed it in the drop box for everyone in the group to access.
As this is the case I chose to create the H and CPP files for as many of the classes as possible, to avoid unnecessary git conflicts when two or more tries to create the same class. Even though this might have been unnecessary i feel this to be an easy way of getting rid of potential problems.
I’ve started on my Sprint planning of this week so Created the State.h and StateManager.h or rather, filled them with code as they were already created.
So far its going quite easy and according to plan, while I’m sticking to using the Programmer code as a platform and modifying that code when needed.
Tomorrow I will have to do the rest of my Sprint Planning as for on Friday it should be done. It should not be any problem to be done in time.
Task Tracker at this very moment of blog writing
 
|
