Download
1 / 18
200 likes | 403 Views
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
E N D
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.
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
Dependencies & Commitments Dependencies • Effective communication • Third party APIs • Browser support Commitments • Quality content • Good usability • Time, Quality & Budget compliance
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 • 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 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
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)
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.
