Project Plan Name of the Group (Edit)
Total Page：16
File Type：pdf, Size：1020Kb
Project Plan Name of the group (edit) Version Date Author Description 1.0 18.6.2007 Vanhanen 1.1 28.9.2009 Rainio Project plan first version (Ch 6.1 and 6.2). More detailed pp-tasks with time estimates. Important dates 1.2 9.10.2009 Rainio listed. Reflection workshop information added. Responsibilities for deliverables added. 1.3 16.10.2009 Rainio Chapters 1-7 initial version. Contents 1. Introduction 5. Work practices and tools 2. Stakeholders and staffing 6. Phasing 3. Goals 7. Risk log 4. Resources and budget 1. Introduction 1.1 Overview of the system In the Happyoffice-project for Rocky Advertizing shall be created a browser-used solution for time tracking and scheduling. In essence it is a calendar view where you can paint events for yourself or multiple participants. Ease of usage is the most important criteria for the product. Rocky advertizing has evaluated the existing time tracking solutions out there and they haven’t been able to find an existing product that would be sufficiently easy to use. They have applied for financing from Keksintösäätiö for developing this solution. In the first phase the product shall replace Rocky’s old time tracking system, but later on it may be sold to other interested parties or distributed as freeware software. 2. Stakeholders and staffing The following picture depicts the stakeholders in the project. Their roles are described below the figure. Figure 1. Organizational chart (no template given). 2.1 Rocky Advertizing Rocky Advertizing is the most important stakeholder in the project. The original idea for the solution is owned by Rocky and they shall also be the primary user of the resulting product. Heikki Kärkkäinen is the project owner at Rocky. He makes the final decisions considering solutions and end results. Antti Vaahtersalo is the technical expert at Rocky. Questions related to the technical implementation choices shall be discussed with him. Users of Happyoffice can be any employee at Rocky. They shall use the end product and should thus be asked for opinions about the usability etc. Emails at Rocky are in format [email protected] 2.2 T-76.4115-course The project shall be done for the course T-76.4115/5115 and thus the requirements of the course have to be considered. Mentor is assigned to the group by the course. Our mentor is Atso Koskinen ([email protected]). 2.3 Hosting service provider We have rented a virtual host from Futuron (www.webhotelli.fi). 2.4 Possible client for the system Rocky may be selling the solution to other companies. 2.4 Balboa team The Balboa team consists of three Software engineering experts and six developers. The team gathers understanding of the solution to be build, created requirements, splits them into tasks and implements the system. Our team consists of the following members Role Name Email Phone PM Ohto Rainio o<lastname>@cc.hut.fi QA Mikko Vestola Architect Ville Harvala Dev Teemu Koskinen Dev Marja Käpyaho Dev Risto Laurikainen Dev Nick Eriksson Dev Osmo Salonen Dev Ville Saalo Contact information can be found from https://wiki.tkk.fi/display/t7641152009TeamBalboa/Contact+information Teams web page can be found at https://wiki.tkk.fi/display/t7641152009TeamBalboa/ E-mail to the whole team is balboa at teemukoskinen dot com. 3. Goals 3.1 Project goals These goals have been derived from the discussions with the customer. Table 1: Goals of the customer in the priority order Goal Verification criteria 1. Working By the end of the project Rocky will be able to fake the HappyOffice time functionality of tracking and scheduling solution into usage at their every day work replacing scheduling and time the old time tracking solution. tracking The usability of the system must be good. Users must be able to use the 2. Ease of usage system without reading a manual. The final validation is done by the customer who decides whether the usability is there. The system has to be such that it can be sold or given to use to other 3. Can be sold to companies than Rocky as well. It will work with the SaaS (Software as a other companies Service) model meaning that the system is hosted in one place and can be used by a myriad of users and companies over the net. The system must support mobile extendability. The system must be designed so that it can be later extended to be used in mobile phones without 4. Mobile significant changes to underlying business logic. The architecture of the extendibility system has to be such, that all the calls made between business layer and UI can be replaced easily with another technique than the currently implemented one. 5. Multi language The system must support multiple languages (Finnish, English, Swedish). support The primary language is English. Security. The clients can't access other client’s information in any way (including user interface and raw communication between user interface and 6. Security the server). Passwords must be encrypted. Users can’t see events they are not meant to see. Documentation. The system must be well documented so that it can be later 7. Documenting extended by other developers. The documentation is validated by the customer. The system must at least support a later adding of a reporting functionality if 8.Reporting not implemented within this project. This means most importantly that the functionality Database structure must support generating reports out of the event data per user, per project, per client, per time period. 3.2 Personal learning goals Table 2: Personal learning goals Member Personal learning goal I'm eager to apply in practice the project management tools and techniques that I've learned at TKK courses. I'm waiting to work with a big team and hope that we are able to build a successful end product for Ohto Rainio our client. It is also interesting to work with a client who hasn't that much experience in IT-projects and trying to figure out the best ways to communicate and ensure the end result will be useful. I want to learn about QA-practices and how a QA-manager works in a team. I'm especially looking forward to see how TDD and unit testing Mikko Vestola helps to produce quality software in practice. I'm also interested in how to produce software with good usability. I have implemented many www- projects with php from a scratch without using any php frameworks. So I'm interested to learn what kind of Ville Harvala solutions do the frameworks offer. I'm also interested to learn what kind of challenges does the project offer in the perspective of an architect. My goal for this project is to widen my perspective about software development projects. I'm excited about working with our customer who Teemu Koskinen seems genuinely interested in the project. Personally I look forward to learning both technical and social skills in an environment that is similar to real-life IT projects. I'm interested in learning new technologies and getting to apply them in practice. This is an excellent opportunity to gain some coding experience and to work with different kinds of development tools in a real project Marja Käpyaho setting. This particular project is also very usability oriented and I'm interested in being a part of the design of a real user interface. And, of course, I look foward to working with our great team-mates! I'm interested in learning about practical software development in a more Risto Laurikainen or less realistic setting. I'm also going to take this course as an opportunity to learn about new technologies and how they all fit together. Im interested getting from simple hobby and school projects to this "real- life simulation". Im eager to see, how can I apply my knowledge from other projects and past experience to this project. This is a huge project Nick Eriksson compared with my previous projects, so I see this a chance to learn about real-life projects and working at this level. Also interested in learning new practises and frameworks. As I have no experience working in a software company, I am excited to be able to work in big team environment. I hope that this will allow me to understand what it is like to work in software company and bring Osmo Salonen understanding to the dynamics of a larger team. In addition I'm looking forward to learning new technologies and building quality software for our client. The last but not the least goal is to make new friends and contacts. I look forward to getting to know web development with PHP and the related frameworks. So far I have developed web applications with Java and its frameworks only, so real PHP development — as opposed to some Ville Saalo simple hobby projects — should prove interesting. I would also like to participate in the high-level architecture planning, but I also feel that I have got some strong views on what works from the end user's point of view, so I would like to stick my nose into the user interface design, too. 4. Resources and budget 4.1 Personnel Work is scheduled per week per person. The vacation is held between week 50 and week 3. Developers are planned to use 80% of their time on iteration 1 and 2 and 20% for project planning iteration. The weekly cumulative planned and realized hours per person can be seen in the following table. Iteration Project plan Iteration 1 Iteration 2 Week 39 40 41 42 43 44 45 46 47 48 49 50 3 4 5 6 7 Planned and realized cumulative hours per person Ohto 20 40 60 80 90 99 108 118 127 136 145 155 164 173 182 192 201 Ohto 39 56 72 Difference 19 16 11 -80 -90 -99 -108 -118 -127 -136 -145 -155 -164 -173 -182 -192 -201 Mikko 12 24 36 49 56 63 71 78 86 93 101