Top Banner
Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic
13

Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Dec 27, 2015

Download

Documents

Clement Daniel
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Distributed Software Development

Transport4You1 Project Plan

Gaurav Kushwaha & Dajan Zvekic

Page 2: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Overview

• Welcome New Member• Development Methodology• Deliverables• Communication• Activity Plan• Milestons• Financial Plans• Project Risks

Page 3: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Welcome New Member

• Gaurav Kushwaha– 26 years old– India

Page 4: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Development Methodology(1)• Agile Scrum• Scrum Artifacts

Product backlog – will be defined and changed according to changes in requirements.

Sprint backlog – will be defined for every sprint and will hold information about planned tasks.

• Why Scrum Unclear requirements in starting, may change later. Small team size and informal communication. Short sprints undermine project risks.

Page 5: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Development Methodology(2)• Scrum adjusted for DSD course:

– Transport4You Scrum Roles:• Scrum Master: Dajan Zvekic• Product owner: Customers Elizabetta Di Nitto and Mateo Rossi and

supervisor Aneta Vulgarakis• Team of 7 members

– Transport4You Scrum meetings• Daily Scrum Meeting

– Twice a week, localy• Sprint Planning Meeting

– Once a week tasks for upcoming sprint will be defined• Sprint Retrospective Meeting:

– Once a week on skype• Sprint Review Meeting

– Presentation on Tuesday

Page 6: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Deliverables

• Project plan document • Requirements Definition document • Design Description document • Summary Week Report • Minutes of Meeting • Technical documents, project policies etc. • Acceptance test plan• Test report• Final Project Report, • Final product (installation, source code, etc.)

Page 7: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Communication

Page 8: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Activity PlanWeek 38

Week 39

Week 40

Week 41

Week 42

Week 43

Week 44

Week 45

Week 46

Week 47

Week 48

Week 49

Week 50

Week 51

Week 52

Requirement gathering x x

Requirement Analysis x x

Architecture Design x x xProduct Implementation x x x x x x x

Unit Testing x x x x x x

Prototype x xSystem and Alfa Testing x x x x

Final Product x x

Final Report x x x x

Final Presentation x x

Estimate to complete Buffer

Page 9: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Milestones

Page 10: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

• Calculating 20 Euros/4hrs • Requirement gathering and analysis =20*5*20=2000 Euros• System Design =20*5*20 = 2000 Euros• Implementation =70*7*20 = 9800 Euros• Testing =28*3*20 = 1680 Euros• Documentation =20*5*20 = 2000 Euros• Mobile for testing = 300 Euros • Rent for Bus = 400 Euros• Price of system in Bus = 400 Euros

• Total Estimated Investment : 18580 Euros

Financial Plan(1)

Page 11: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Financial Plan(2)

Euro

Distribution of finances within Project

Page 12: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Project Risks• Missing of deadline.

– Regular meetings to discuss progress.– Keep track of progress by weekly reports

• Team member is leaving – Backup for team members.

• Communication Gap – Information is posted on discussion forum.– Meetings are documented in MOM’s.

• Issue with SVN Repository and Local data– Regular Backup

Page 13: Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Questions??