2. Agenda  Project Overview  Project Goal & Scope  Estimates  Deadline  Project Environment  Delivery Plan  Project Plan  Team Structure  Risk Analysis  Project Success Indicator  Project Logistics 2

3. What Is It Delivering? Objective Implement a web based Project Resource Management (PRM) System to manage resource allocations of projects efficiently. Approach Agile Development Process System requirement specification Implementation specification Release Synergy Version 1 Release Synergy Version 2 Release Synergy Version 3 3

4. Man Hours Estimation 4 Approximate Calculation of Man Hours Hours per person on Week Days = 1 x 5 = 5 Hours Hours per person on Weekend = 3 x 2 = 6 Hours Hours per person for a Week = 5 + 6 = 11 Hours Total Duration = 10 Weeks Total Hours per person = 11 x 10 = 110 Hours Number of Members = 8 Total Man Hours = 110 x 8 = 880

5. What Does It Take To Deliver? 5 880.0Grand total 88.0Contingency (10%)‏ 240.0Quality Assurance 30.0Environment Preparation 390.0Implementation 42.0Design 40.0Documentation 50.0Requirements Elicitation 792.0Total Effort (Man Hours)‏

6. When Is It Delivered? 21 st February 2011

7. Project Environment Operating System Windows Server 2008 Database Server Microsoft SQL Server 2008 Web Server Microsoft IIS 7‏ 7

8. Development Environment Microsoft.NET Framework 3.5 Visual Studio 2008 IDE Microsoft ASP.NET MVC 2 C#NET ADO.NET Entity Data Model 8

9. Project Plan - Key Milestones 9 MilestonesDev Date QA DateDel DateDescription Project Start12 th Dec 201021 st Feb 2011Final release of the PRM SRS18 th Dec 201007 th Jan 2011Software Requirement Specification TDS25 th Dec 201014 th Jan 2011High level project design and Detail technical design Prototype19 th Dec 201008 th Jan 2011Prototype of the system Synergy V109 th Jan 201115 th Jan 201129 th Jan 2011Project management, tasks allocation and administration modules Synergy V230 th Jan 201107 th Feb 201112 th Feb 2011Time sheets and Reports/charts module Synergy V313 th Feb 201115 th Feb 201121 st Feb 2011Team Calendar and integrate all the modules. Release Final software product

10. Project Plan - Assumptions/Dependencies Assumptions  All team members will involve in implementation.  Team members will play their team roles as expected.  Customer will be able to monitor the progress of the product online and will give the feedback on time.  Customer requirements will not change dramatically.  Team members having the required technical knowledge. Constraints – Application will need to be hosted online. – Application development need to be done in online SVN. 10

11. Team Structure 11 ? NameRoleDescription Shrimal AndrahendiTeam Leader (TL),(SE), (QA), (TW)Business Logic Layer,SRS Amalka JeevanthaProject Manager (PM), (SE), (QA)Coordinate the Project Activities, Business Logic Chanaka Weerawardena(SE), (QA)Presentation Chandu Udayanga(SE), (QA)Business Logic Gayan Weilgama(SE), (QA)Database Design, Presentation Virath C. Liyanage(SE), (QA)Database Design, Business Logic Buddhika Jayaweera(BA), (SE), (QA), (TW)SRS,Requirement Analysis Nalin Kanangara(BA), (SE), (QA), (TW)SRS,Requirement Analysis,User Manual. * All the members will involve in system design and implementation Software Engineer - SEQuality Assurance - QATechnical Writer- TWBusiness Analyst - BA

12. Project Risks 12 L = Likelihood, I = Impact, E = Exposure Risk DescriptionLIEMitigation Schedule Slips4936Regular progress updates and keeping backup resources. Issues in Hosting the Application339Getting prior agreement which meet our hosting requirements from the facilitator. Change of Functional Requirements5525Get the sign off of the SRS. Maintaining Source Code in an Open Source Public Project Host. 4416Keeping regular backups. Selecting a trusted party. Communicating with the Customer5630Planning to use online communication effectively. Arrange meetings. Coordinate the team members339Weekly meetings

13. Project Success Indicator (PSI) 13 A good start for the project5070Total 810Manage for error / manage expectations The roles and responsibilities are assign based on experience and knowledge of each member. 810Assign people to jobs The group has selected one team member as a team leader and has signed roles among other team embers. 10 There must be one leader 1220Define and estimate the jobs 1220Visualise the goal DetailsScoreMax ScorePlanning the Project Studied the similar systems related to the project and have an idea on the functionalities. Here we classify main functional requirements in to five release candidates and calculate effort for each tasks. Carrying out QA process and conduct code review.

14. Project Logistics Project Code Name Synergy Source Control Google Code, Sub Version Control (SVN) Project Communication Skype, MSN, Team Viewer, Email Documentation repository Google Docs Project Email Groups/Wiki Google Groups, Google Code Wiki Documentation repository – Zoho Code repository – Google Code 14

15. THANK YOU Questions?