Call Calendar Final presentation

1
Call CalendarFinal presentation

• Distributed Software Development
• 2014/2015

Biljana Stanic, Damian Marušic, Marko Vuglec,
Hrvoje Pavlovic,Abdur Razzaque, Marko Velickovic
2
Team members
Hrvoje Pavlovic (FER)
Biljana Stanic (MDH)
Marko Velickovic (MDH)
Damian Marušic (MDH/FER)
Md. Abdur Razzaque (MDH)
Marko Vuglec (FER)
3
Content

• Project Overview
• Project work summary
• team roles
• member responsibility
• job division
• working hours
• github statistics
• Project Status and Requirements
• tools used
• requirements

4
Content

• SCRUM - dos and donts
• Communication
• Experiences
• Workload
• Now and then
• In the end
• Testing and Verification
• Demo

5
Project Overview

• Customers Malin Rosqvist Irfan Šljivo
• Enable researchers to find a perfect project call
• Enable customers easier manipulation with
  applications and projects
• Functionalities calls, applications, reports,
  automatic project and news creation

6
Team roles
7
Member responsibility
Responsibility Team member(s)
Document manager Biljana Stanic and Hrvoje Pavlovic
Design manager Marko Velickovic and Hrvoje Pavlovic
Development team leader(s) Damian Marušic and Biljana Stanic
Server maintenance Marko Vuglec and Damian Marušic
Quality assurance and risk management Abdur Razzaque and Marko Velickovic
8
Job division

• Server maintenance
• Marko Vuglec and Damian Marušic
• Communication to customer
• Marko Vuglec in cooperation with Biljana and
  other team members optionally
• Document editing
• Every member writes about his/her part of job
• Final document editing and preparing -
• Biljana Stanic and Marko Vuglec
• Programming - all team members

9
Working Hours - team
10
Working Hours - individual
11
Working Hours - member
12
Contributions to call, excluding merge commits

• Most work - mid December and beginning of January
• Total - more than 70 commits

13
Contributions by team member
Damian Marušic and Marko Vuglec
14
Contributions by team member
Abdur Razzaque and Marko Velickovic
15
Contributions by team member
Biljana Stanic and Hrvoje Pavlovic
16
Tools used

• Google drive
• Additional 12 documents
• only colored text
• Official documents 2 - 5 different versions and
  iterations
• Real time communication and collaborative work
• All presentations are created on it

17
Tools used

• GitHub
• Code tracking
• Total of 73 commits
• XAMPP
• Used to develop code on localhost
• MySql database was shared

18
Requirements - Summary

• Functional requirements
• 55 total, 2 in progress, 2 incomplete
• High priority 42 total, 42 done
• Medium priority 9 total, 9 done
• Low priority 4 total, 2 in progress, 2
  incomplete
• Non-Functional requirements
• 2 total, 2 complete 1 high, 1 medium
• Document requirements
• 5 total, 5 complete 5 high

19
Requirements
20
Functional requirements - priority
21
Interesting (difficult to implement) requirements

• Send email to researchers
• No documentation in Prestashop
• how to do it
• Reports and export to .pdf
• We managed to do only basic ones
• Attachments
• Problem with developing custom templates

22
Architecture
23
SCRUM - dos and donts

• We used ScrumBut
• Elements of scrum
• Product owner Marko Vuglec
• SCRUM Master Biljana Stanic
• Simplified backlogs
• Sprint Planning meeting

24
SCRUM - dos and donts

• Total sprints 5
• 1st - 57h
• 2nd - 106h
• 3rd - 170h
• 4th - 188h
• 5th - 233h

25
SCRUM - not used

• Scrum elements that we did not use
• Daily Scrum meeting
• Sprint Burndown chart
• Release Burndown chart

26
Communication - with members
27
Communication - with members

• Number of meetings between members
• 13 official meetings
• 17.5h
• Meetings with Supervisors
• 5 meetings
• 5.5h
• Meetings with Customers
• 5 meetings
• 6.5h
• Average 2 meetings per week.

28
Experiences - Good

• Real time communication
• Viber 24/7 (grocery store, bad, etc.)
• Skype - if needed and for group meeting
• Coordination of people

29
Experiences - Bad

• Regarding implementation
• Problems with PrestaShop
• Poor documentation
• Regarding team
• Without strict meetings defined

30
Workload

• Properly synchronized and divided between team
  members
• Flexible job assignment
• No duplication of job
• Work on every functionality was separate
• Database was done first

31
Now and then

• At beginning
• Project looked simple enough
• Approach was easy and slow
• Some problems was not anticipated
• In the middle
• Project got complicated after every meeting with
  customer
• Problems with PrestaShop caused delays
• Around Christmas and New year project got to
  stall

32
In the end

• Project is almost complete
• All turned out well
• Changes in all over again
• Strict meetings with predefined schedule
• All user requirements defined in the beginning
• More work on official documentation less on
  unofficial
• Use complete product backlog
• Start earlier with presentations

33
Verification and validation

• Selenium IDE for functional testing
• Record all actions in site (go through tests)
  manually and repeat them
• Functionalities tested after implementation.

34
Selenium IDE
35
Selenium IDE
36
Demo
37
Thank you!Questions?