distributed software development 11-10-09. coldwatch project plan ante ivanković usman alam...
TRANSCRIPT
Distributed software development
11-10-09
ColdWatch
Project Plan
Ante Ivanković
Usman Alam
11-10-09
Overview
• Project Overview
• Development methodology
• Deliverables
• Communication
• Milestones
• Activity plan
• Financial plan
• Project risks
11-10-09
Project overview
Sub-zero temperatures in facilities cause pipe bursts
Possible solution: Passive heating system
Development methodology (1)
Scrum framework• Product owner
– Product backlog
• Scrum master– Servent leader
• Team– Self-organizing, self-lead
Meetings: Sprint planning
Daily scrum
Sprint review and retrospective
Development methodology (2)
Deliverables (1)To Output Planned date
Supervisor / Customer Project plan document 2011-10-21
Supervisor / Customer Requirement definition document
2011-10-21
Supervisor / Customer Design description document
2011-10-28
Supervisor SW Integration Alpha Version
2011-11-22
Supervisor SW Integration Beta Version
2011-12-13
Supervisor / Customer Acceptance test plan 2011-12-16
Supervisor / Customer Test report 2012-01-09
Supervisor / Customer Final project peport 2012-01-13
Supervisor / Customer Final product 2012-01-13
Deliverables (2)
To Output Planned date
Supervisor Summary week report Every monday
Supervisor Minutes of meeting During project
Team members Technical standards documents
During project
Supervisor / Customer Revisions of existing documents
When needed
Communication
MilestonesProject V ision presentation
Project P lan Docum ent
Requirem ents Defin ition
Design Description Docum ent
A lpha Prototype
Beta Prototype Acceptance test p lan
Release Candidate
Final P roject P resentation
Activity Plan
Financial Plan
Costs are based on provisional activity plan
Graphical RepresentationProject Cost
Project Preparation
Requirements definition
Project design
GSN Impletentation
ETL Implementation
Web Implementation
Integration
Unit & Acceptance Testing
Documentation
Final Delivery
Project risks
Risk Level Prevention
Data loss High Regular bacups
Missing the internal scheduld deliverables
Medium Flagging the issue in time
Improper estimation of resources
High Scope of the project has to be estimated appropriately
Lack of communication within team
Medium A clear-cut transparency required
Incompatible platforms High Proper selection of platforms
Unavailability of a member
Meddium Proper hand-over has to be done