Call Calendar
Alpha presentation
Distributed Software Development
2014/2015
Biljana Stanić, Damian
Marušić, Marko Vuglec
Team members
Biljana
Stanić
(MDH)
Damian
Marušić
(MDH/FER)
Marko
Veličković
(MDH)
Md. Abdur
Razzaque
(MDH)
Hrvoje
Pavlović
(FER)
Marko Vuglec
(FER)
Content
❖ Project Overview
❖ Scrum and Spirits
❖ Current Project Status
❖ Future Development
❖ Project Management Tools
❖ Testing
❖ Experiences
❖ Alpha Prototype Demo
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
PrestaShop
❖ Exists of two main parts
❖ Back-office - administration purposes
PrestaShop
❖ Front-office - web page for public
Scrum
❖ Advantages
➢
➢
➢
Adaptive and flexible
Fast customers’ feedback
Incomplete tasks can be corrected in next
sprint
❖ Disadvantages
➢
➢
➢
Relaxed schedule
False security
Idea is simple, but realization is complicated
Sprints
❖ 1st Sprint (27.10. - 9.11.)
➢
➢
➢
Basic documentation
Meeting with customers
Project plan presentation
❖ 2nd Sprint (10.11 - 16.11.)
➢
➢
➢
➢
Detailed documentation
Server setup
Second meeting with customers
Requirements and design presentation
Sprints
❖ 3rd Sprint 17.11 - 30.11.
➢
➢
➢
➢
➢
Online meeting with one customer
Detailed DB design
DB deploy
Alpha product
Status presentation
❖ 4th Sprint (future)
➢
➢
➢
➢
Full DB deployment
Beta product
Meeting with both customers
Documentation
Current Project Status: Working Hours
❖ Last week - 112 Hours and Total - 275 Hours
Current Project Status: Achievements
Sprint
and date
17.11 30.11.
Planed
Achieved Details
Local environment setup
100%
DONE!
Documentation
80%
Documents are
incomplete
Presentations
100%
DONE!
Communication with
customer
100%
Clarified
requirements
Implement Call part
80%
Missing document
part and deadlines
Implement Application
part
0%
Pushed into next
sprint
Current Project Status: Based on requirements
❖ Functional
➢ Add new call
➢ Adding application form to the call
➢ Storing application’s forms
➢ View all calls, View specific call
➢ Create a project
❖ Non-functional
➢ Performance (SQL optimization)
❖ Documents
➢ MoM, Weekly reports
➢ Project plan, Requirements definition, Test report
Future tasks - part 1
❖ 4th Sprint (future)
➢
➢
Meeting with customers
Full database deployment and link local to
server
➢ Finish Call implementation (support for
adding documents and deadlines)
➢ Create custom filters
Future tasks - part 2
❖ 4th Sprint (future)
➢ Implement Application part
➢ Modify documents and publish new revisions
➢ Prepare live beta product demo
➢ Create and add into existing documents tests and
results of testing
Project Management Tools
❖ Tools that we use during our project development:
➢ Project tracking
■ Github
➢ Documentation
■ Google Drive
➢ Communication
■ Skype, Viber, Email
➢ Testing
■ Selenium IDE
Testing
❖ Functional testing
❖ Selenium IDE
❖ Tests connection with the database
Testing
Testing
Experiences
❖ Offline database problems
❖ Documentation is important
❖ Unplanned activities
❖ Customer and product owner in different
countries
Alpha Prototype Demo
❖ Completed database design
❖ Finished setting up local development
environment
❖ Implemented Call part
➢
view/edit/delete calls (type, status, deadline
type)
➢ filter calls by statuses, types and funding
agencies
Alpha Prototype Demo
❖ Online demo:
➢
http://161.53.67.147/prestashop-skeleton/
❖ Offline demo:
➢
Hosted locally on laptop of team member,
Marko Veličković
Thank you!
Questions?