Distributed Software Development

Distributed Software Development

Project Plan Presentation

Purpose of Project Plan

Project purposeBusiness and project goals and objectivesScope and expectationsRoles and responsibilitiesAssumptions and constraintsProject management approachGround rules for the projectProject budgetProject timelineThe 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 Since this is the first release of these features

Resource High 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 Key Contact Persons

Division/ Region

Project Sponsor/ Client

• Ultimate decision-maker and tie-breaker• Provide project oversight and guidance

Supervisor (Ivana Bosnic)

Croatia

Steering Committee

• Commits department resources• Approves resource allocation and strategies• Resolves conflicts and issues• Provides direction to the Project Manager • Review project deliverables

Supervisor(Ivana Bosnic)Project Lead (Loredana Baracic)

Croatia

Sweden

Project Organization & Responsibilities -2

Group Responsibilities Key Contact Persons

Division/ Region

Project Manager

• Manages project in accordance to the project plan• Provide overall project direction• Direct/lead team members toward project objectives• Handle problem resolution

Project Lead (Loredana Baracic)

Croatia

Development Team

• Analysis (Requirements)• Architecting Application• Coding•Assure quality of project• Documentation

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 sprintsEach sprint consist of average 15 daysSprint backlogs will be populated based of

user stories priorities settled by stakeholders.

Effort, Staff & Budget

Planned EffortTotal EffortEffort allocated by ActivityActivity categories (Requirement,

Design, Code/Implementation, Integration/ Test & Delivery)

Staff LoadingReconciliation to Budgeted Effort

Milestones & Schedules

Milestone Planned Date

Projected Date

Actual Date

Status

Requirement Analysis 25-09-2010 StartedPrototype complete 01-10-2010Design Complete 08-10-2010Test Plan Review 22-10-2010Development Complete 26-11-2010Integration 03-11-2010Documentation 10-12-2010Unit Testing Complete 17-12-2010Ready for QA 17-12-2010First Submit 24-12-2010QA OK for Delivery 14-01-2011

Dependencies & Commitments

DependenciesEffective

communicationThird party APIsBrowser support

CommitmentsQuality contentGood usabilityTime, Quality &

Budget compliance

Risks & MitigationRisk Impact Probability Mitigation

Person Hours High Certainty Assigned Project Manager, engaged consultant, comprehensive project management approach and communications plan.

Estimated Project Schedule

High Certainty Created comprehensive project timeline with frequent baseline reviews

Team Members Inexperienced

Medium Likely Project Manager and consultant to identify knowledge gaps and provide training, as necessary.

Steering Committee existence

Low Unlikely Frequently seek feedback to ensure continued support.

Timeline Estimates Unrealistic

Medium Likely Timeline reviewed monthly by three groups (Project Manager and Steering Committee) to prevent undetected timeline departures.

Physical Location of Team prevents effective management

High Certainty Use of Intranet project website, comprehensive Communications Plan.

Inspection & Quality Assurance

Defect-removal goalsSelection criteriaCoverage targetsQA process throughout the projectBuilding test casesUnit testingIntegration testingUser acceptance test

Communication & ReportingAudience : Communication plan is

for the following audiences: Project Sponsor/Client Steering Committee Project Manager User Group Participants Subject Matter Experts

CommunicationsMethodology: Top Down Bottom Up Middle Out

CommunicationsOutreach: 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 Existing equipment needed that is fully controlled by this project

• Development machines in lab• Team member’s Laptops

Existing Hardware needed not fully controlled my project (shared or borrowed equipment)

• SVN Server• Project Webpage• Document Repository  

New Software/tools/hardware needed by this plan. • Web development tool (Dreamweaver, Netbeans)• Design Tools (Adobe Photoshop)• Database Server (MySQL)• Office Suite (MS-Office 2007)• Web Server (Apache)

Delivery Plan

Deliverable Planned Date ReceiverProject 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 URLProject Plan Document http://www.fer.hr/rasip/dsd/projects/

content_recommendation_and_reuse/documents

Requirement Definition Document

http://www.fer.hr/rasip/dsd/projects/content_recommendation_and_reuse/documents

Design Description Document

http://www.fer.hr/rasip/dsd/projects/content_recommendation_and_reuse/documents

Minutes of Meeting http://www.fer.hr/rasip/dsd/projects/content_recommendation_and_reuse/documents

Policy Documents http://www.fer.hr/rasip/dsd/projects/content_recommendation_and_reuse/documents

Acceptance Test Plan http://www.fer.hr/rasip/dsd/projects/content_recommendation_and_reuse/documents

Final Project Report http://www.fer.hr/rasip/dsd/projects/content_recommendation_and_reuse/documents