Distributed Software Development Project Plan Presentation Purpose of

Distributed Software Development Project Plan Presentation

Purpose of Project Plan �Project purpose �Business and project goals and objectives �Scope and expectations �Roles and responsibilities �Assumptions and constraints �Project management approach �Ground rules for the project �Project budget �Project timeline �The conceptual design of project

Project Goals & Objectives ØImproves content authoring. Ø Facilitate researchers, students, presenters with resources of quality and relevant content. Ø Enhances the ability and effectiveness of professionals to perform their jobs. Ø Facilitates plagiarism prevention and reduction. Ø Provide high levels of content availability. Ø Provides an open, flexible, and reliable technology base for the future development. Ø Facilitates the electronic capture of data at its source. Ø Is easy to use. Ø Eliminate redundant data throughout the content.

Assumptions & Constraints Assumptions: � Content authors are willing to change normal operations to take advantage of the functionality offered by the new tool. � Management will ensure that project team members are available as needed to complete project tasks and objectives. � The Steering Committee will participate in the timely execution of the Project Plan (i. e. , timely approval cycles and meeting when required). � Failure to identify changes to draft deliverables within the time specified in the project timeline will result in project delays. � Project team members will adhere to the Communications Plan. � All project participants will abide by the guidelines identified within this plan. � The Project Plan may change as new information and issues are revealed. Constraints: � Project resources are limited, with no contingency. � Dependency on underlying technology.

Size, Quality, Resource & Time Attributes Attribute Flexibility (rank High Medium, Low, None) Rationale Size Low Feature set is already a minimum required for delivery, no further reductions possible Quality Medium Resource High Since this is the first release of these features Given the lack of flexibility in other attributes, Resources must be kept flexible. Time None Needs to be part of Candidate Release.

Project Organization & Responsibilities Group Responsibilities Project • Ultimate decision-maker and Sponsor/ Client tie-breaker • Provide project oversight and guidance Steering • Commits department Committee resources • Approves resource allocation and strategies • Resolves conflicts and issues • Provides direction to the Project Manager • Review project deliverables Key Contact Persons Supervisor (Ivana Bosnic) Division/ Region Croatia Supervisor(Ivana Croatia Bosnic) Project Lead Sweden (Loredana Baracic)

Project Organization & Responsibilities -2 Group Project Manager Development Team Responsibilities • Manages project in accordance to the project plan • Provide overall project direction • Direct/lead team members toward project objectives • Handle problem resolution • Analysis (Requirements) • Architecting Application • Coding • Assure quality of project • Documentation Key Contact Persons Division/ Region Project Lead (Loredana Baracic) Croatia Project Lead (Loredana Baracic) Team Lead (Ather Sajjad) Croatia Sweden

Project Model & Activities �Iterative Development ◦ Scrum Agile methodology �Product backlog will be constructed with user stories �Divided into four sprints �Each sprint consist of average 15 days �Sprint backlogs will be populated based of user stories priorities settled by stakeholders.

Effort, Staff & Budget �Planned Effort �Total Effort �Effort allocated by Activity �Activity categories (Requirement, Design, Code/Implementation, Integration/ Test & Delivery) �Staff Loading �Reconciliation to Budgeted Effort

Milestones & Schedules Milestone Planned Date Requirement Analysis 25 -09 -2010 Prototype complete 01 -10 -2010 Design Complete 08 -10 -2010 Test Plan Review 22 -10 -2010 Development Complete 26 -11 -2010 Integration 03 -11 -2010 Documentation 10 -12 -2010 Unit Testing Complete 17 -12 -2010 Ready for QA 17 -12 -2010 First Submit 24 -12 -2010 QA OK for Delivery 14 -01 -2011 Projected Date Actual Date Status Started

Dependencies & Commitments Dependencies Commitments �Effective �Quality content communication �Third party APIs �Browser support �Good usability �Time, Quality & Budget compliance

Risks & Mitigation Risk Person Hours Impact Probability Mitigation High Certainty Assigned Project Manager, engaged consultant, comprehensive project management approach and communications plan. Estimated Project High Certainty Created comprehensive project timeline with Schedule frequent baseline reviews Team Members Medium Likely Project Manager and consultant to identify Inexperienced knowledge gaps and provide training, as necessary. Steering Low Unlikely Frequently seek feedback to ensure Committee continued support. existence Timeline Medium Likely Timeline reviewed monthly by three groups Estimates (Project Manager and Steering Committee) Unrealistic to prevent undetected timeline departures. Physical Location High Certainty Use of Intranet project website, of Team prevents comprehensive Communications Plan. effective management

Inspection & Quality Assurance �Defect-removal goals �Selection criteria �Coverage targets �QA process throughout the project �Building test cases �Unit testing �Integration testing �User acceptance test

Communication & Reporting Audience : Communication plan is for the following audiences: � Project Sponsor/Client � Steering Committee � Project Manager � User Group Participants � Subject Matter Experts Communications Methodology: � Top Down � Bottom Up � Middle Out Communications Outreach: The following is a list of communication events that are established for this project: � Weekly Status Reports � Weekly Steering Committee Meeting � Bi-Weekly Project Team Status Meeting Tools: � Email � Phone � Google Group � Skype � Project Page

Software Environment &Tools v Existing equipment needed that is fully controlled by this project • Development machines in lab • Team member’s Laptops v Existing Hardware needed not fully controlled my project (shared or borrowed equipment) • SVN Server • Project Webpage • Document Repository v New Software/tools/hardware needed by this plan. • Web development tool (Dreamweaver, Netbeans) • Design Tools (Adobe Photoshop) • Database Server (My. SQL) • Office Suite (MS-Office 2007) • Web Server (Apache)

Delivery Plan Deliverable Planned Date Receiver Project Plan 01 -10 -2010 Steering committee Requirement Definition 01 -10 -2010 Steering committee Project state presentations 26/10, 16/11, 14/12 Steering committee Acceptance Test Plan 10 -12 -2010 Steering committee Beta Release 14 -12 -2010 Supervisor Final Presentation 11 -01 -2011 Product Owner Final Delivery 14 -01 -2011 Product Owner

Security Aspects � Classification of the project information with regard to requirements for integrity, availability and confidentiality, in accordance with the directives on security. � Specific action: Security agreements with suppliers and partners, security check of project team members, security audits of equipment, usage of coded information, etc. � Authorization of information distribution and publishing, that is, who should decide which information will be distributed to whom, � Policy & procedure for monitoring security, � Policy & Procedure for reporting security incidents.

Reference Documents Document Name Location and/or URL Project Plan Document http: //www. fer. hr/rasip/dsd/projects/content_recommendation_and_re use/documents Requirement Definition Document Design Description Document Minutes of Meeting Policy Documents Acceptance Test Plan Final Project Report http: //www. fer. hr/rasip/dsd/projects/content_recommendation_and_re use/documents