1 / 10

T-76.4115 Iteration Demo

T-76.4115 Iteration Demo. Game On! Solutions PP Iteration 24.10.2006. Agenda. Project status Work results Used work practices. Introduction to the project. What is this project about? Develop a front-end system for a game-on-demand service with LAMP Client: G-Cluster

lane-levy
Download Presentation

T-76.4115 Iteration Demo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. T-76.4115 Iteration Demo Game On! Solutions PP Iteration 24.10.2006

  2. Agenda • Project status • Work results • Used work practices

  3. Introduction to the project • What is this project about? • Develop a front-end system for a game-on-demand service with LAMP • Client: G-Cluster • Used in testing, presentations and sales • A reference model for systems developed by G-Cluster’s customers • Documentation of the problem domain

  4. Status of the iteration’s goals • Goal 1: Creation of project plan and understanding the domain - ok • Goal 2: Requirements engineering - ok • Goal 3: Select and implement practices - ok • Goal 4: Sign contract - work in progress • Goal 5: Select tools and architecture - ok

  5. Iteration’s deliverables • Project plan • Ok, but allocated time does not match • Iteration plan • Ok, but outdated • Requirements document - ok • Progress report - ok • Architectural design document • Ok but only a draft for internal use

  6. Task Assignee Allocated time Used time Implement web pages Tapio Auvinen 1h 2h Contact graphic designer candidates Ismo Lehmus 3h not done Decide on used framework Antti Kaunisto & Joni Leiponen 2h 2h Decide on coding convention Antti Kaunisto & Joni Leiponen 2h 2h Design architecture Antti Kaunisto & Joni Leiponen 2h 2h Review old code Antti Kaunisto & Joni Leiponen 2h 1h Write architectural design documentation Antti Kaunisto & Joni Leiponen 3h 2h Decide on what version control software to use Ismo Lehmus & Juuso Jääskeläinen 1h 1h Define requirements for the product Juuso Jääskeläinen Included in meetings Decide on issue tracking software Ismo Lehmus & Juuso Jääskeläinen 3h 4h Decide on time tracking software Ismo Lehmus & Juuso Jääskeläinen 2h 2h Decide on risk management practices Ismo Lehmus & Juuso Jääskeläinen 1h 1h Install all necessary tools Antti Kaunisto 6h 8h Decide on communication practices Ismo Lehmus 1h 1h Decide on documentation practices Ismo Lehmus 1h 1h Meetings with the client Lehmus, Jääskeläinen, Kaunisto, Leiponen 10h / person 10h / person Internal meetings All members 9h / person 9h / person Tasks & time usage

  7. Resource usage • Not available yet • Data outdated

  8. Risk Description Avoidance Probability Impact Hardware problems Server breaking down, tools and code base lost Keeping most important issues somewhere else also, keeping backup of the code base. 1 4 Shortage of human resources People getting sick, other activities that take time Constant development, information sharing 3 2 Server-client architecture Multiplayer and other player-to-player functionalities can not be implemented in the client operating environments due to the strict server-client architecture and limited support for techniques to circumvent that. The multiplayer functionalities will be simplified. Available techniques for circumventing the problem (auto-refreshing) will be used. Separate versions for environments supporting asynchronous scripting might be created. 5 5 Risks

  9. Results of the iteration • Project plan • Goals • Practices • Tools • Requirements documentation • System overview • Functional/non-functional requirements

  10. Used work practices • Eventum for issue and time tracking • Up, but not yet fully configured • Time reporting with issues not yet in use • Subversion for version control • TikiWiki in use • experiences

More Related