Gift Case Gijs Bos, Ana Stepić, Vlatko Klabučar, Damir Tomić,

Slides:



Advertisements
Similar presentations
CASDA Project Management A presentation to the CASDA Preliminary Design Review IM&T / CASS Dan Miller | CASDA Project Manager 11 March 2014.
Advertisements

COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
An Integration Platform of Social Networking Applications to Support Life Long Learning in Rural Territories: the “SoRuraLL Virtual Learning World” Environment.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Welcome! Presenter: Sam Foster. Major Topics To Be Covered In This Presentation Content Management System Amazon, eBay, and Gun Broker Integration Shopping.
NOTE: To change the image on this slide, select the picture and delete it. Then click the Pictures icon in the placeholder to insert your own image. PROJECT.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
T Iteration Demo CloudSizzle PP Iteration
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
1 These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer Science.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer Science.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Using Social Media for Fundraising and Communication with Supporters Lindsay Boyle – Communications & Research Coordinator Claire Chapman – Information.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Call Calendar Alpha presentation Distributed Software Development 2014/2015 Biljana Stanić, Damian Marušić, Marko Vuglec.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
NOTICE! These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
2050AP Project WP5: “Conclusions” UPM Madrid 11 de Octubre 2013.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Office Introduction BERNARD DADY Bernard Dady.
Android Mobile App Development India
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Project Workflow.
Project Management PTM721S
Outline Your one-minute feedback from last week
Discover your career at Accenture
Office 365 Continuing Education
Shifting to Agile: Are University Libraries Ready?
The Strategic Role of Information Development in Continuous Delivery
NOTICE! These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Project Workflow.
Eric Schmidt - Assignment
Chung-Min Huang, Chien-Tang Hu Institute of Information Science
Gift Case First Status Presentation
The Improvement of PaaS Platform ZENG Shu-Qing, Xu Jie-Bin 2010 First International Conference on Networking and Distributed Computing SQUARE.
Impact of Agile Methodology on Software Architecture
Seminar CS2310 Multimedia Software Engineering Krithika Ganesh
School of EE and Computer Science
Design Process Overview
How to Successfully Implement an Agile Project
Design Process Overview
Agile Process: Overview
Gathering Systems Requirements
Practical Software Engineering
Data Science Meetup Matthew Renze Data Science Consultant
What is Communication? Source: Source:
Design Process Overview
Scrum Science NGSS: Engineering, Technology, Applications of Science
USC CSCI 577A Course Project
Design Process Overview
Training 01: Project Lifecycle & Business Technology Analysis
Gathering Systems Requirements
Design Process Overview
Agile software development
Business model canvas Prepare a business model canvas of your business idea using the model in the next slide. You can fill it using bullet points and.
CEN 5011 Advanced Software Engineering
NOTICE! These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Critical top 3s v
Cloud Computing for Wireless Networks
Presentation transcript:

Gift Case Gijs Bos, Ana Stepić, Vlatko Klabučar, Damir Tomić, Giulio Cattivera, Aleksandra Salikiryaki Good afternoon, My name is Gijs Bos from MDH in Sweden and i'm going to present the gift cafe project to you today. Lets start with the topics that this presentation will cover.

Agenda Introduction Project description Architecture and technology Risks Tools Development methodology We will start with introducing the team members of the project and the stakeholders involved, followed by the project description. Next we will talk about the preliminary architecture of the system and the technology that will be used. Finally we take a look at the risks, tools and development methodology used.

Stakeholders (internal) Project team Gijs Bos Damir Tomić Ana Stepić Giulio Cattivera Vlatko Klabučar Aleksandra Salikiryaki Client and supervisors Marin Orlić Igor Čavrak Juraj Feljan The team consists of 6 members, 3 situated in Malardalen, 3 situated in croatia. Our stakeholders consist of 2 supervisors and our primary customer.

Gijs Bos Origin: Netherlands Background: BSc Information Sciences Current: MSc Software Engineering

Giulio Cattivera Origin: Italy Background: BSc in Computer Science Current: MSc Software Engineering

Aleksandra Salikiryaki Origin: Bulgaria Background: BSc Information Technologies Current: MSc Software Engineering

Vlatko Klabučar Origin: Croatia Background: BSc in computing Current: MSc Telecommunications and Informatics

Ana Stepić Origin: Croatia Background: BSc Software Engineering Current: MSc Computer Science

Damir Tomić Origin: Croatia Background: BSc Software Engineering Current: MSc Software Engineering

Client and supervisors Marin Orlić Client Igor Čavrak Local Supervisor Juraj Feljan Remote Supervisor

Project description GiftCase Аpplication for gift recommendation and purchasing Android Integration online stores and services social networks GiftCase will be an Android application for gift recommendation and purchasing. The idea of the application is to notify the user for the incomming celebrations and events related to his friends. The application will further propose possible presents customized according to the friends` interests. For this reason the application will be integrated with several social networks like Facebook in order to gather information about the users` preferences. The application will also be integrated with content providers like Amazon and iTunes in order to enable the used directly purchase and send a present to his friends. For now we are going to focus on presents which are electronic.

Project plan Goal: Deliver and deploy the giftcase application within two months Deliverable: Native android application

Architecture informal overview

Technology Application platform: Android / Phonegap Backend technology: Java / Backend as a service Engine: Ericsson ISN Engine

Risks Integration of Ericsson’s matching engine Integration and interoperability between Ericsson’s db and users db

Tools Communication Project management Source Control Slack - Instant messaging service Skype - Voice and video conferencing Google Docs - Document management Project management Kanbanize Source Control GitHub

Why SCRUM? Project size Time constraints Self-organization Previous experience We have chosen the SCRUM methodology for a variety of reasons. Due to the project size and time constraint, we determined that an agile method would be best to use. The first option that came to mind was SCRUM. SCRUM is known for its fast delivery of a working product, this in our case would allow us to get fast feedback on a working product instead off extensive feedback on a list or requirements SCRUM also allows you to be self organized which is convenient for distributed development Finally, some of our team members have previous experience in SCRUM, and the rest is eager to try it.

SCRUM Characteristics 3 Week sprints 3 Customer evaluations 48 Hour scrum meetings Some small adaptations to the standard SCRUM methodology have been made. First of all, our SPRINTS consists of 3 weeks because this would allow us to have three round of feedback from the customer. Next, we choose to have a minimum of three SCRUM meetings per week, thus we decided to name it 48 hour scrum meetings. We decided to adopt most of the standards from the SCRUM methodology. This brings us to the end of our presentation

Thank you for your attention Questions?