Work has begun on the project, the first step was to organize the team and discuss the ten user stories that each individual had decided on for the project. A user story (link shows definition) explains requirements in a realistic scenario in order to show requirements that the project may have and the reasons for them.

These are particularly useful because they can vary in detail, allowing the team to quickly describe what a user would require, prioritize them and break them down into more manageable sizes. Which is the process the team is currently in at the moment. Each member has decided on 10 user stories. Here are mine:

• As a fitness enthusiast I would like a game mode that requires upper body strength so that I can stay fit now I am no longer able bodied
• As a new wheelchair user I want a game mode that involves moving so that my chair control improves
• As an ex personal trainer who is no longer able bodied I want game modes that help continue fitness development
• As a member of a family with multiple wheelchair users I want a game with mode to suit all of us so we can continue to play together
• As a friend of a wheelchair bound individual I want game modes that allow multiplayer interaction so we can still take part in the same game
• As a big fan of casual gaming I want a game that lets you progress without playing for hours.
• As someone that has wheelchair bound individuals I want a game that demonstrate what it is like to use the chair on a daily basis, moving, control etc, this means it will be easier to relate to them.
• I am wheelchair bound but interested in getting into body building, because of this I want game modes that help achieve this.
• Recently wheelchair bound I want a game that helps track progress to help improve ability.
• I wish to improve general fitness even though I am wheelchair bound but I find it hard to stick to plans, I want a game that gives achievements to keep me interested.

Now at this stage these stories are ‘epic user stories’ this means they are quite vague and describe a large part of the development process and will later be broken down and assigned time frames. These have been merged with other group members stories within the meeting minutes document on our github repository.

From this point on wards each week will involve posts describing completed and accepted work from the previous week and also a plan regarding the following weeks agreed tasks.

Working hours have already been decided between team members. These are shown below:

• Work times – Dev sessions
  • 2 hours planning meeting – Mondays 1pm-3pm
  • 4 hours group development – Thursday 11am-3pm
  • 2 hours planning – Thursday 4pm – 6pm
  • 2 hours personal development time – varying between members

The next stage of the process is to get input from the managing director regarding priority order of stories and also the allocation of this weeks scrum master and their tasks.

status of this stage = accepted