Project Plan 1-3

Project plan
CSD Fall 2011
Project owner Bjrn Pehrson
Project Coaches Bruce Zamaere Erik Eliasson Herv Ntareme Siraj Rathore
Team members Bowei Dai Elis Kullberg Hannes Junnila Nur Mohammad Rashed Siddharth Madan Vasily Prokopov Time commitment Total hours Total man years 3200 2 daib@kth.se elisk@kth.se haju@kth.se nmrashed@kth.se smadan@kth.se prokopov@kth.se 15 credits 18 credits 15 credits 15 credits 15 credits 18 credits
October 18th, 2011
Page 2 of 32 Revision: 1.3 (18-Oct-11)
Table of Contents
1 INTRODUCTION ...............................................................................................................4 1.1 1.2 1.3 1.4 Background ..........................................................................................................4 Summary..............................................................................................................4 Motivations ...........................................................................................................4 Related work ........................................................................................................4
2 GOALS ..............................................................................................................................6 2.1 2.2 2.3 2.4 2.5 Overarching goals ................................................................................................6 Measurable objectives..........................................................................................6 Deliverables and deliveries...................................................................................9 Unique contribution of the team members ..........................................................10 Dissemination of results and expected impact ....................................................11
3 APPROACH.....................................................................................................................11 4 RESOURCES ..................................................................................................................14 4.1 4.2 4.3 4.4 Human resources ...............................................................................................14 Space .................................................................................................................14 Equipment needed .............................................................................................15 Budget................................................................................................................16
5 WORK BREAKDOWN STRUCTURE...............................................................................17 5.1 5.2 5.3 5.4 List of work packages and activities ...................................................................17 List of Milestones and tollgates ..........................................................................23 Individual responsibility matrix ............................................................................25 Organization .......................................................................................................25
6 STAKEHOLDER ANALYSIS ............................................................................................26 7 RISK ANALYSIS ..............................................................................................................28 8 REFERENCES ................................................................................................................29 9 APPENDENCES ..............................................................................................................30 10 BRIEF CV:S .....................................................................................................................31
Contact: Elis Kullberg, elisk@kth.se
Page 3 of 32 Revision: 1.3 (18-Oct-11) Overview of changes: Version 0.1 0.2 1.0 1.1 1.2 1.3 Changes Initial document Predraft for the final feedback round Final draft Implemented feedback Implemented feedback Removed team-member
1 INTRODUCTION
1.1 Background KTH Royal Institute of Technology, the largest technical university in Sweden, and Karolinska Institutet, the largest medical University in Sweden, have formed an advanced research network infrastructure in Stockholm known as CareNet-SE to take the hospital to the patients homes. Research on this project has been going on for over 2 years. During the formation of the project the goal was to design and develop a robust network and maintain the network. This has been achieved with the continuous efforts of the active researchers and masters students at KTH. CareNet is a multi-stakeholder effort involving investment and expertise in many fields including the medical industry, communication systems manufacturers and telecommunications operators. CareNet targets to improve the health-care system by providing quality healthcare services to patients homes, initially targeting prematurely born babies, elderly people and outpatients [1]. The CareNet-SE network is based on a dark fiber backbone of 10-gigabit Ethernet links and contains three backbone routers which are situated at three different locations. Karolinska Institutet has one, and KTH campuses at Kista and Valhallavgen have the remaining two. The Valhallavgen router is working as a border router which is connected to the KTH-LAN. Since the establishment of the project, focus has shifted towards technology enabling remote care and monitoring of patients using this infrastructure. The infrastructure also includes home extensions currently being deployed in a pilot apartment ward at the Neo-natal department of Karolinska University Hospital in Huddinge. 1.2 Summary The main goal of the CareNet fall 2011 project is to refine the services offered over the already deployed CareNet infrastructure. Key activities include testing and improving the residential gateways that will connect out-care patients to the CareNet infrastructure. Additional deliverables include user-case demonstrations and cooperation with similar projects worldwide. 1.3 Motivations CareNet will enable prematurely born babes and patients requiring palliative care to be monitored from their homes (out-patient care) instead of hospital. This transition benefits society as a whole through cost rationalization, since traditional, inpatient care is comparatively expensive. Therefore, CareNet integrates well with value-guided healthcare, which is the global paradigm for providing affordable healthcare to a growing and ageing population. Use cases that will be explored include the monitoring of elderly citizens, premature babies and palliative cancer patients in their homes. 1.4 Related work MonAMI MonAMI is an EU funded project started in 2006 and aimed to provide equal access and independent living within the informational society for elderly people and persons with disabilities. Current status: field trials have been carried out in Sweden, Slovakia and Spain. The
Page 5 of 32 Revision: 1.3 (18-Oct-11) MonAMI project continues to develop its technology and services and aims to increase the number of local implementations. Previous CareNet teams Former CareNet teams have been conducting the research for several years and brought the project to the point where the Fall 2011 CareNet team will take it over. HDVIPER The goal of HDVIPER is to provide an open HD video conference platform which can offer some services through a unified Service Oriented Architecture (SOA) over IP and to be integrated in a set-top-box and in a PC environment (pre-commercial prototype) [5]. HIPERMED The goal of HIPERMED is to design an open telemedicine platform to provide media services, SIP-based control plane services and network services over IP and to support remote consulting, tele-teaching and distributed consensus decision-making on treatment programs. It will also be possible to implement any sort of healthcare unit[4]. CARENET-SE The Vinnova funded overhead organization for all CareNet related activities at Karolinska Indistutet and and KTH [6]. Health and Wellbeing activity of EIT ICT Labs. The European Institute of Innovation and Technology hosts a wide range of projects, among them an ICT effort within Health and Wellbeing. Key stakeholders of this initiative include tslab, the working group behind MonAMI (contact person: Thomas Lind), the man-machine communication group at the school of Computer science and Media (contact person: Kicki Groth) and Ericsson (contact person: Peter Hkansson). [8]
2 GOALS
2.1 Overarching goals The project features two main goals: Successful take-over, operation and hand-over of the CareNet network and services. Success will be measured by network interface uptime, and an external verification of handover documents for spring team. Development and field testing of the CareNet Home Extension, including residential gateways, HDVC clients, sensor gateways, health portal access and associated usecases. Success will be measured through stakeholder surveys, and acceptable field test performance of gateway improvements during field testing.
2.2 Measurable objectives Operation of the CareNet network Required: Successful handover for upcoming CareNet team. Smooth and uninterrupted CareNet network operation.
Additional objectives: Improvements on the CareNet infrastructure
Criteria for evaluation of required objectives: Approved hand-over documentation via 3rd party. Nagios reports showing interface uptime of 99.9%. Deployment of any further infrastructure improvements.
Improving upon residential gateways Required: Connectivity: Deployment of mobile broadband support in Bifrost. IPv6 implementation for residential gateways. Virtualization: Conclusion if LXC-decision is rational through analysis virtualization techniques (full virtualization versus containers). Update of RC scripting for container initialization if needed. Control software: Deployment of gateway control GUI. Deployment of a mechanism to update router software. Deployment of a possibility for uploading relevant data for the field test.
Page 7 of 32 Revision: 1.3 (18-Oct-11) Additional objectives: Create a sensor gateway for the residential gateway: Research and test home automation for healthcare systems:
Criteria for evaluation of objectives Connectivity: Successful multi homing between primary and secondary (3G) links in field trials. Successful selected field trials in IPv6. Virtualization: Quality of conclusions regarding security and performance of LXC. Control software: Residential gateways can be administered without SSH. Software updates can be pushed automatically during field trials. Software facilitates field trial data collection. Sensor gateway deployed and tested. Sensors IPv6 enabled and accessible.
Taking over and running field tests of residential gateway prototypes Required: Gain deeper understanding stakeholder expectations regarding field tests. Aligned tangible roadmap for continuation of the test process. New test scenarios that unit test gateway improvements, and use case examples Ongoing documentation and communication of outcomes. Create plan for handover to the spring 2012 CareNetteam.
Criteria for evaluation of objectives: Review from key stakeholders regarding if expectations have been met. Timely presentation of field testing roadmap. All improvements by gateway team field tested. Review from key stakeholders regarding if communication has been clear. Verification of hand-over documentation from 3rd party.
Exploring the overlaps with the MonAMI project and suggesting coordination Required: Analysis of possible synergy between the projects. Formal suggestions of other potential collaboration partners, if any.
Criteria for evaluation of objectives: Rational decision regarding if to extend CareNet 10GE backbone to Haninge. If decision is yes, a plan for funding. All modes of cooperation between MonAMI and CareNet explored.
Page 8 of 32 Revision: 1.3 (18-Oct-11) Centralizing knowledge of the Bifrost operating system Required: Creating a wiki-based central source of Bifrost documentation. Encourage other projects to append/use wiki.
Criteria for evaluation of objectives: Bifrost wiki deployed. External access possible.
Page 9 of 32 Revision: 1.3 (18-Oct-11) 2.3 Deliverables and deliveries General: Item Project Website Project Plan Draft Final Project Plan Weekly Progress Reports Updates for Residential Gateway Software Mid Term Presentation Field Test Report Project Poster Project Video Final Report Peer Review Exhibition Press Release Lessons learned Document Deadline September 1st, 2011 September 2nd, 2011 September 7th, 2011 Every Sunday at noon Every second week October 12-13, 2011 January 10-11, 2012 January 10-11, 2012 January 10-11, 2012 January 10-11, 2012 January 10-11, 2012 January 10-11, 2012 January 10-11, 2012 January 10-11, 2012
Project specific: Item CareNet network reports Stakeholder contact sheet Residential software updates Formal plan for Field test Learnings from NOChandover Learnings from Field Test handover Bifrost wiki set up Best case practice for handing over the CareNet network Automatic virtual server backup mechanism and documentation Automatic router configuration backup mechanism and documentation Protocol from stakeholder meetings Possible road-map for further network development Ticketing system documentation SLA (more specific) Conclusions from field tests Deadline Every Monday September30th, 2011 Every second week October 1st, 2011 October 30th, 2011 October 30th, 2011 October 15th, 2011 October 20th, 2011 November 1st, 2011 November 15th, 2011 November 15th, 2011 December 1st, 2011 December 15th December 30th December 30th
Page 10 of 32 Revision: 1.3 (18-Oct-11) 2.4 Unique contribution of the team members Bowei Dai Based on previous experiences on network projects, I can contribute to the network part of our project such as CareNet routing and operation,VPN, and Bifrost router configuration. My weakness is programming. I only have some basic knowledge of C so I can learn a lot of programming from our team. Moreover, I used Ubuntu few times before and this project will give me an opportunity to get a deeper and comprehensive understand of Ubuntu and get used to it. Elis Kullberg Key strengths include project management in terms of leading teams of 10-20 people in entrepreneurial environments will help me lead the team forward. Technical competencies include IPv6, gateway design, java/python, general network design and possibly finance will also come in handy. My main weakness is that I have little professional experience in the IT field, for example I consider myself a good programmer, but I have little experience conforming to industry standards when coding. Hannes Junnila My main strength is within software design using various programming languages and environments. My main contribution will be working with the software for the residential gateway. As I have a degree in Industrial Engineering and Management I can also contribute in areas such as management, procurement and supply chains if needed. An area of weakness is that I have no professional experience of large-scale infrastructure deployments, I am planning to shadow the NOC team during the fall to improve this. Nur Mohammad Rashed Worked for 3 years in Telecom industry (Both GSM and CDMA) as BSS (Base Station System engineer) and NOC (Network Operation Centre) engineer. I have knowledge in telecommunication network rather than computer network. My whole experience is in Telecommunication (BSS installation, MSC configuration and installation, frequency allocation, RF planning). I have knowledge on routing, VPN, network security, IPv6, Linux but not in highest quality. So I would like to learn more and enrich my computer network ability working along with Vasily. I do not have that much programming experience and do not like that. I have little experience in management also. I am a very good team player I believe. I have also good documentation ability. I will give my best to get a good grade as well as to achieve the goal of our team. Siddharth Madan I have over 3 years of background in the Information Technology industry and have worked with major IT companies - Tech. Mahindra and British Telecom on IT services projects. I have managed the network database for British Telecom. I have also worked with SME consulting; an IT services company in shaping their testing and quality policies for attracting clients for high quality services at economical costs. My key strengths include networking and database related knowledge. I also have experience in requirement analysis along with testing and quality implementation. I am fairly proficient in coding with Oracle-PL/SQL and Contact: Elis Kullberg, elisk@kth.se
Page 11 of 32 Revision: 1.3 (18-Oct-11) Java, but i would like to improve my skills in programing and Linux as they are not my strongest suit. Vasily Prokopov Having vast experience in network design, operation and documentation development I believe I can contribute strongly to the networking-related parts of the project, such as CareNet network operation. Routing, dual-homing, addressing, VPN, IPv6, mobile backup - these are also the issues I can be helpful with. My weak side is programming. I have some proficiency in C and Java and it would be great if the CareNet project will help me to develop my programmingskills further.
2.5 Dissemination of results and expected impact The results of the teams work will be communicated through the following channels Web: The CareNet project websitehostingtheteams technical and non-technical reports. The Bifrost wiki, which will act as a hub for information about installing, configuring and running Bifrost. Though exposure on Technology Transfer Alliance website (http://tta.ssvl.kth.se)
Direct mail/email News letter directed to stakeholders and most parties listed in section 8. Suggesting tangible methods of cooperation to SIDI (Swedish institute for drug informatics).
Physical Word of mouth from team-members, stakeholders including coaches, and other related persons. Through attending and presenting at the Vinnova conference on November 10, 2011. Through participating in any other conferences hosted by or attended by key stakeholders, for example events hosted by Stockholm School of Entrepreneurship. Demonstrations and proof of concepts via Karolinska Living Lab.
3 APPROACH
The CareNet teams approach to development is an iterative process divided into several phases:
ANALYZE DESIGN & REVIEW IMPLEMENT TEST & DOCUMENT OPERATE
Analyze Aggregate the information gathered from the previous operation phase (if such a phase exists). Collect requirements from stakeholders. Analyze collected data to formulate an actionable problem to be solved or to determine a feature to be introduced or improved. Come up with a list of constraints. Enhance problem formulation adding extra details if required.
Design & Review Work out the architecture of a new feature. Redesign existing infrastructure if required. Come up with a logical design. Estimate the implementation in terms of costs, functionality and performance.
Page 13 of 32 Revision: 1.3 (18-Oct-11) Implement Translate the design and logic into code or configuration commands. Deploy the feature within the existing CareNet infrastructure. In case of updating residential gateway software make the latest release available for downloading from a repository.
Test & Document Test the implemented feature and verify if it functions as expected. Document a new feature and update existing documentation if required. Document the changes have been made to the existing CareNet infrastructure.
Operate In the case of residential gateway software, deploy to all custodians using a public repository. Maintain the infrastructure. Gather information for analysis during the next cycle.
4 RESOURCES
4.1 Human resources Team Member Bowei Dai Background Holds a Bachelor degree in Information Science and Communication Engineering, currently pursuing Master Program in Communication Systems at KTH Holds a Bachelor degree in Industrial Engineering and Management. Currently pursuing a Masters degree within the same field. Electives in operating systems, Java/C/scripting, computer architecture & internetworking Holds a Bachelor degree in Industrial Engineering and ManagementEngineering, minor in Communication systems. Currently pursuing a Masters Degree at KTH Holds a Bachelor degree in Information Technology, currently pursuing Master Program in Communication Systems at KTH, Special Course taken from SSE. Having 3 years Experience in the IT services industry with companies like British Telecom Holds a Bachelor degree in Computer Science and Engineering, currently pursuing Master Program in Communication Systems at KTH Hold a Bachelor degree in Computer Engineering and pursuing the MSC in Communication Systems. Credits (%) 15 (50%) 18 (60%) 15 (50%) Hours 400
Elis Kullberg
480
Hannes Junnila Siddharth Madan
400
15 (50%)
400
Vasily Prokopov Nur Mohammad Rashed
18 (60%) 15 (50%)
480
400
4.2 Space Team will be based in room 8332 on floor 8 in Forum-building. For bulky hardware, we have to cooperate with CareNet summer team until we take over their bigger room in mid October. NOCteam have requested access to server-room 8240A.
Page 15 of 32 Revision: 1.3 (18-Oct-11) 4.3 Equipment needed Gateway package Item 1x Bifrost router 1x Screen 1x keyboard 1x medical sensor featuring nonproprietary output 1xUMTS modem + subscription 2x4gb USB drives 1x4g modem + subscription Date needed Obtained As soon as possible As soon as possible October 1st Obtained As soon as possible As soon as possible
Field test package Item 1x HDVC client Date needed October (can be shared with summer team)
Media Package Item 1x web server (virtual or physical) 1x video camera Date needed As soon as possible November
Page 16 of 32 Revision: 1.3 (18-Oct-11) 4.4 Budget Management: Teambuilding 2000SEK
Subtotal
Field test equipment: Fika etc. for stakeholder meetings Specific testing equipment:
2000SEK
500SEK tba 500SEK tba 1500SEK 1000SEK
Subtotal
Sensor gateway: Blood oxygen meter 4G modem and subscription 3G subscription
Subtotal
Multimedia: Printing posters, flyers (10xA3 color):
<1500SEK
200SEK 200SEK 0SEK 0SEK 0SEK 0SEK 2700SEK
Subtotal
NOC: None
Subtotal
MonAMI: None
Subtotal
Total:
5 WORK BREAKDOWN STRUCTURE

5.1 List of work packages and activities Management package Owner: Elis Kullberg
Meetings / manage workflow (40 hours) Manage team (50 hours) Coordinate scheduling (10 hours)
All external stakeholder contact (20 hours) Stakeholder Contact (30 hours) Management package 260 hours
Coordinate hand-over to spring team (10 hours)
Progress reports (40 hours) Deliver progress reports 2x key deliverables (80 hours) 2x key deliverables (40 hours) Fill in time-sheets, SSK, group meetings (120 hours)
Page 18 of 32 Revision: 1.3 (18-Oct-11) Media package Owner: Nur Mohammad Rashed
Keep website tidy and updated Web/Dropbox master (10 hours) (8 hours) Keep Dropbox sorted (2 hours)
Plan movie (5 hours) Movie (60 hours) Media package 100 hours Make movie (85 hours)
Poster (10 hours)
Make poster (10 hours)
Create wiki (20 hours) Bifrost wiki
(40 hours)
Update wiki (20 hours)
Page 19 of 32 Revision: 1.3 (18-Oct-11) NOC Operation package Owner: Vasily Prokopov
Taking over the operation process (50 hours) Operate CareNet network (250 hours) Administrating CareNet network infrastructure (175 hours) Handing over operation process (25 hours) Regular progress reports (50 hours) Document design modifications (50 hours)
NOC operation (500 hours)
Analyze and improve network design (150 hours)
Relevant documentation (100 hours)
Page 20 of 32 Revision: 1.3 (18-Oct-11) Gateway package Owner: HannesJunnila
Test + implement modem (70 hours) UMTS support (100 hours) Include in network configuration (30 hours) Connectivity (300 hours) OpenVPN on IPv6 connections (100 hours) IPv6 in OpenVPN tunnel (100 hours) Setting up test environment (50 hours)
IPv6 (200 hours)
Analysis of performance Gateway package (1000 hours) Virtualization (100 hours)
(200 hours)
Scripting (100 hours)
Test + analysis (50 hours)
Power Management (100 hours)
Control Software (500 hours)
Implement data collection + sending) (100 hours)
Implement GUI (200 hours)
Implement add-on containers (100 hours)
Page 21 of 32 Revision: 1.3 (18-Oct-11) MonAMI package Owner: Siddharth Madan

Analyze website (5 hours) Analyze previous touch points (5 hours) Make analysis document (10 hours) Contact stakeholders (5 hours) Cooperation suggestion (20 hours) Written co-op document (5 hours) Document outcome (10 hours)
What is MonAMI? (20 hours)
MonAMI package (40 hours)
Page 22 of 32 Revision: 1.3 (18-Oct-11) Field test package Owner: Siddharth Madan
Understand stakeholder expectations (20 hours)
Investigate methods for user case tests
(20 hours)
Analyze (220hours)
Design User test cases (30 hours)
Understand CareNet summer status (20 hours) Design roadmap & methodology for testing (aligned with stakeholders, 130 hours) Implement changes to gateways to support methodology (60 hours)
Field testing package (660 hours) Execute (220 hours)
Carry out testing (100 hours)
Fix any bugs encountered (80 hours)
Document findings (140 hours) Document (220 hours) Create hand-over for CSD spring (80 hours)
Page 23 of 32 Revision: 1.3 (18-Oct-11) List of Milestones and tollgates What All previous technical documents analyzed Taking over the CareNet network Taking over the field test Mid term presentation Handing over the CareNet network Final delivery When Week 38 Week 40 Week 40 Week 41 Weeks 1-2 Week 2
Page 24 of 32 Revision: 1.1 (18-Oct-11) Gantt diagram
5.2 Individual responsibility matrix
Management MonAMI Bowei Dai Elis Kullberg Hannes Junnila Nur Mohammad Rashed Siddharth Madan Vasily Prokopov Sum 20 160 20 20 20 20 260 40 40
Media 20 20
NOC Gateway 280 380 200
Fieldtest 80 300 180
Sum 400 480 400 400 400 480 2560
40 20 100
300 500
300 40 1000
100 660
5.3 Organization Person Bowei Dai Elis Kullberg Hannes Junnila Nur Mohammad Rashed Siddharth Madan Vasily Prokopov Title Bifrost responsible Project manager Residential gateway responsible Field test responsible Media responsible NOC responsible
6 STAKEHOLDER ANALYSIS
Stakeholder analysis is summarized in below table. Every stakeholder is graded in four areas: Block: This stakeholder will attempt to block our progress unless their particular demands are satisfied. Let: This stakeholder will not intervene in our project and will let us progress. Help: This stakeholder has a particular interest in the ongoing work and will provide help and expertise when needed. Make: This stakeholder will actively provide the project with necessary expertise, hardware and/or software and are the main contributors to the project deliverables. Package Management Role Project owner Block Let Help Make Action x x x x Attend weekly PM meetings to manage expectations Coaching x x Build a constructive relationship, to get as much feedback as possible General help and x Keep regular exchange of contact human capital Assistance x x Contact when necessary. Cooperation x x x x Daily contact with key members Cooperation x x x Contact when necessary Tech assistance x x Build relation before take-over, then contact when necessary Techincal x x Build relation assistance before take-over, then contact when necessary Dissemination x x Market when necessary Use case x x x Meeting as per assistance request to discuss usecases Assistance, x x Gaining guidance knowledge, equipment and support when required
Who Principal
Coaches
All
Other PMs
Management
Teachers CareNet Summer Other teams Network Operators
All NOC, Gateway, Management All NOC, field testing
Karolinska staff, technical Karolinska Living Lab Karolinska staff, medical Other KTH staff
Gateway, NOC, field testing
Gateway, Field testing Gateway NOC, field testing All
Page 27 of 32 Revision: 1.3 (18-Oct-11) Custodians Gateway, NOC, management, field testing Gateway Cooperation x x Meetings according to field test plan Release purchase order when needed Contact if needed
Hardware supplier, Litech[7] Housing industry
Sales and sponsorship Residential gateway integration, use case support Coordination and support, expertise sharing, cooperation Coordination and support, cooperation Service provision, expertise sharing Cooperation, sponsorship Cooperation, field test support Stakeholder in Karolinska Expertise in medical procedures and law Funding
Gateway, field testing
MonAMI
MonAMI
Ericsson
Gateway
Contact with cooperation proposal and request for information Contact if needed Contact and cooperate when needed Contact if needed Contact if needed Keep informed Request legal compliance info for use cases Inform November 10th, and when needed Monitor progress of thesis and help if needed
Network operators Private care providers Stockholm kommun Stockholms lan Swedish ministry of health Vinnova
NOC, field testing Gateway, field testing Field testing Field testing, gateway Gateway, field testing
x x x
xxxxxx
Management
Technology Transfer Alliance
NOC
Possible CareNet NOC extension to TTA partners
7 RISK ANALYSIS
Internal: Risk Team member fails to commit Likelihood Severity Mitigation strategy - Ensure everyone is comfortable with tasks and teamstructure - Take start-stop-keep seriously - Implement SCRUM - Regular team building and feedback - Ensure project plan aligns with skill set of group - Book HDVC intro with Eric -Follow code of conduct. - Have realistic expectations on team - Treat lent equipment with care and respect Contingency Strategy - Actively resolve problems. - Re-allocate tasks to other team-members.
Medium
High
Lack of focus on tasks at hand Lack of skill within key area
Low
High
Medium
High
- Regular meetings to resolve and guide problems - Keep good relations with other teams for borrowing of manpower
Scheduling issues (many 15 credit students) Equipment gets lost/broken
High
High
- Enforce group scheduling rules stringently - Take paperwork regarding signing out equipment seriously
Low
High
External: Risk Critical problems in CareNet network Likelihood Low Severity High Mitigation strategy - Follow project plan for NOCknowledge transfer - Ensure Gantt diagram is realistic High Low Contingency Strategy - Ensure good relationship with KTH technical staff and CareNet summer NOC team - Adapting the project plan - Emphasize the importance the timeframe - Use on hold functionality in SCRUM - Regular feed-back and support from coaches and principal regarding compliance requirements - Be prepared to adapt plan if possible
External Dependencies
Swedish law interferes with use cases Missunderstood expectations from stakeholders Lead time on equipment delivery Stakeholder blocking use case
High
Low
- Conduct proper pre-studies before implementing ideas - Align project plan with all stakeholders - Regular PM reports - Finish prospecting equipment before week 39 - Keep backup plan for use case tests
Low
High
Medium Low
Medium Medium
- Use simulated data for sensors - Implement backup plan and be flexible
8 REFERENCES
[1]CareNetCSD Spring 2011. Documentation:http://csd.xen.ssvl.kth.se/csdlive/content/documentation-3 [2] CareNetCSD Fall 2010.Documentation: http://csd.xen.ssvl.kth.se/csdlive/content/documentation-0 [3] CareNet-SE. Project URL: http://www.carenet-se.se/ [4] HIPERMED. Project URL: http://www.hipermed.org/ [5] HDVIPER. Project URL: http://www.hdviper.org/ [6] Carenet-SE, Project URL: http://www.carenet-se.se/ [7] Litech, Company URL: http://www.litech.se [8] HIB activity of EIB: http://eit.ictlabs.eu/ict-labs/thematic-action-lines/health-wellbeing/
APPENDENCES
Code of Conduct I am aware of the KTH/TSLAB code of conduct including consequences of time-sheet manipulation and plagiarism. I also commit to respecting the time of my colleagues by: Attending and arriving in time to all weekly team-meetings (Tuesdays and Thursdays). Uploading full SSK/timesheet/achievements/schedule for next week before Friday midnight weekly. Aiming to beat the CSD-target of 50% group work (group implying on-site, with at least another team member).
______________________________________________ Bowei Dai
______________________________________________ Elis Kullberg
______________________________________________ Hannes Junnila
______________________________________________ Nur Mohammad Rashed
______________________________________________ SiddharthMadan
______________________________________________ VasilyProkopov
10 BRIEF CV:S
Name: VasilyProkopov Email:prokopov@kth.se ECTS credits: 18 Educational background: 2002-2007 Bachelors degree in Telecommunication Networks 2010-2012 Masters degree in Communication Systems Work Experience: 2007-2009 Network engineer at the National Bank of Belarus 2008-2010 Systems engineer and instructor at Solidex PI, which is a partner of Cisco, Extreme Networks, Fortinet and Ericsson
Name: Elis Kullberg Email:elisk@kth.se Phone: +46762811246 ECTS Credits: 18 Education Background: 2007-2010: Bachelors Degree in Industrial Engineering and Management. 2012: Exchange at Hong Kong University of Science and Technology. 2011-2012: Masters Degree in Industrial Engineering and Management. 2011: Financial Markets at the London School ofEconomics& Political Science (summer) Experience: Team Leader, SIFE-KTH (10-20 team-members in 4 projects). Marketing Intern, Procter & Gamble, (responsible for marketing plan, budget roughly 2 million SEK).
Name:HannesJunnila E-mail:haju@kth.se ECTSCredits:15 Phone: +46700547142 Education background: 2007 - 2012: M.Sc. in Industrial Engineering and Management, with a minor in communication systems at KTH 2010 - 2011: Exchange year at Aalto University in Helsinki, Finland Experience: 2011 - : Self-employed in software development 2010, 2011: Assistant sales manager for Luvata Pori Oy
Name:Bowei Dai Email:daib@kth.se Phone: +46764098399 ECTS Credits: 15 Education Background: Sep.2006-Jun.2010,Two Bachelors Degrees in Zhejiang University in China, one major is Information Science and Communication Engineering; the other is Business Administration Aug.2010-now, Studying as a master student in KTH (major: communication system) Work Experience: Jun.2009-Aug.2009,Internship at China Telecom Name:Nur Mohammad Rashed Email: nmrashed@kth.se Phone: 0760813340 ECTS Credits: 15 Educational Background: 2002-2006 Bachelor of science in Computer Engineering 2009-2012 Master In Communication Systems Work Experience: 2006-2008: Network Operation Engineer at Sheba Phone (Integrated Services Limited) 2008-2009: NSSengineer at Huawei Technologies Bangladesh Limited Name:SiddharthMadan Email: smadan@kth.se Phone: 0764096882 ECTS Credits: 15 Educational Background: 2003-2007 B.Tech (Information Technology),Anna Univ - INDIA 2010-2012 Master In Communication Systems in KTH,Sweden Work Experience: 2007-2009 : Software Engineer & Analyst at Tech Mahindra (British Telecom) 2009-2010 : Business Analyst & Team Lead at SME Consulting Services.

Project Plan 1-3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Plan 1-3

Uploaded by

Copyright:

Available Formats

Project plan

CSD Fall 2011

Project owner Bjrn Pehrson

October 18th, 2011

Page 2 of 32 Revision: 1.3 (18-Oct-11)

Contact: Elis Kullberg, elisk@kth.se

Contact: Elis Kullberg, elisk@kth.se

Page 4 of 32 Revision: 1.3 (18-Oct-11)

Contact: Elis Kullberg, elisk@kth.se

Contact: Elis Kullberg, elisk@kth.se

Page 6 of 32 Revision: 1.3 (18-Oct-11)

Additional objectives: Improvements on the CareNet infrastructure

Contact: Elis Kullberg, elisk@kth.se

Contact: Elis Kullberg, elisk@kth.se

Contact: Elis Kullberg, elisk@kth.se

Contact: Elis Kullberg, elisk@kth.se

Contact: Elis Kullberg, elisk@kth.se

Page 12 of 32 Revision: 1.3 (18-Oct-11)

ANALYZE DESIGN & REVIEW IMPLEMENT TEST & DOCUMENT OPERATE

Contact: Elis Kullberg, elisk@kth.se

Contact: Elis Kullberg, elisk@kth.se

Page 14 of 32 Revision: 1.3 (18-Oct-11)

Hannes Junnila Siddharth Madan

Vasily Prokopov Nur Mohammad Rashed

Contact: Elis Kullberg, elisk@kth.se

Contact: Elis Kullberg, elisk@kth.se

Page 16 of 32 Revision: 1.3 (18-Oct-11) 4.4 Budget Management: Teambuilding 2000SEK

Contact: Elis Kullberg, elisk@kth.se

Page 17 of 32 Revision: 1.3 (18-Oct-11)

5 WORK BREAKDOWN STRUCTURE

Coordinate hand-over to spring team (10 hours)

Contact: Elis Kullberg, elisk@kth.se

Poster (10 hours)

Make poster (10 hours)

Create wiki (20 hours) Bifrost wiki

Contact: Elis Kullberg, elisk@kth.se

NOC operation (500 hours)

Analyze and improve network design (150 hours)

Relevant documentation (100 hours)

Contact: Elis Kullberg, elisk@kth.se

Page 20 of 32 Revision: 1.3 (18-Oct-11) Gateway package Owner: HannesJunnila

IPv6 (200 hours)

Analysis of performance Gateway package (1000 hours) Virtualization (100 hours)

Test + analysis (50 hours)

Power Management (100 hours)

Control Software (500 hours)

Implement data collection + sending) (100 hours)

Implement GUI (200 hours)

Implement add-on containers (100 hours)

Contact: Elis Kullberg, elisk@kth.se

Page 21 of 32 Revision: 1.3 (18-Oct-11) MonAMI package Owner: Siddharth Madan

What is MonAMI? (20 hours)

MonAMI package (40 hours)

Contact: Elis Kullberg, elisk@kth.se

Investigate methods for user case tests

Design User test cases (30 hours)

Field testing package (660 hours) Execute (220 hours)

Carry out testing (100 hours)

Fix any bugs encountered (80 hours)

Contact: Elis Kullberg, elisk@kth.se

Contact: Elis Kullberg, elisk@kth.se

Page 24 of 32 Revision: 1.1 (18-Oct-11) Gantt diagram

Contact: Elis Kullberg, elisk@kth.se

Page 25 of 32 Revision: 1.1 (18-Oct-11)