Company profile 2017

1

Our company

2

● Established in 2006

● Privately owned

● A profitable company since its establishment

● 35 employees

● 25 Senior developers with an average experience of 12 years

Our Team ● Experience

● Passion

● Self driven

● Conciliation

● Commitment

● Innovation

● Learning

● Personal growth

3

When?● Are you short of time?

● Is the target clear, but difficult to define the functional scope?

● Do you know if the application/business will change?

4

Web Application Development:● Ruby on Rails

● Spring

● Angular JS

● Drupal

Big Data / IoT / Data Integration:● Spark

● Hadoop

● Scala

● Kafka

● Cassandra, MongoDB, NoSQL

Our Tools

Some customers …

6

Own products: FACTURAgem

7

● SaaS Solution

● Based on Neurodidactics.

● Focused on collaborative learning.

● Recovering the role of the teacher.

8

NeuroK: A different way of learning

What does make us different ?● “Customer intimacy”: Our

customers´projects become our own.

● Web Knowledge.

● Methodology: SCRUMgem.

● Tools and flexibility to manage changes.

● Our philosophy: it is the combination of “getting it real” with “less is more”.

9

Things we do not do● Rigid and detailed processes.

● Exhaustive functional descriptions.

● Endless documentation.

● Contract negotiation.

10

Methodology

It is more important what I do not know than what I know

Traditional vs ASPgems

Resources Time

Features Resources Time

Features

Estimated

Fixed

13

MethodologyASPgems suggests a different way to develop projects.

After many years suffering the rigours of the waterfall development model (analysis, design, coding and testing...), ASPgems has chosen an agile and iterative methodology and that's why this project will be implemented following SCRUMgem.

14

Scrum Method/ SCRUMgem

ASPgems has chosen SCRUM, and we have carried out our own implementation SCRUMgem

Review- Review of

functionalities development

- Retrospective about fittings from the sprint

PLANNING- Review of the project

backlog - Estimation Of the

sprint backlog - Design and

compromise for the next sprint

SCRUM- What has been done since

the last meeting?- Planning of the work for

the week - Accelerators/ Roadblocks

Goals to be dealt are identified in the

nteractión

It defines, analyzes and designs the processes

objective of the iteration

Appropiate developments are

carried out

We review with customers the fulfilling of targets and functional details from

implementation

We do the changes agreed in the review in order to

fulfill the targets

1 2

3

5

4

15

MethodologyThis methodology allows an iterative development of the solution, allowing its progressive refinement.

In this way, the probability of a successful project being thanks to:

● Regular project reviews with the customer

● Review of initial requirements according to what has been learnt in the last stage of the project.

The project plan and the scope of each iteration are refined based in:

● Customer requests● Time ● Quality requirements ● Available resources● Functionalities needed

16

The advantages provided by this methodology, over conventional processes are:

● The development process is adapted to customer business priorities.

● It fosters close collaboration between ASPgems teams and the customer teams, and hence encouraging cooperation.

● The empirical testing of concepts brings closer the functionalities that users require . There is no better proof than testing business ideas in front of a user to understand how the application should be improved.

17

Methodology

The advantages provided by this methodology over conventional processes are:

● Increase customer understanding of the product developed, reducing training and adoption costs.

● Increases project success ratio.

18

Methodology

Coordination and ValidationAlong the way, development deliverables will be done at the end of each sprint, so the application will be validated by the Product Owner.

The coordination of the development is done with the tool Taiga, a management tool shared by all the team members that supplies a historic archive of the development evolution.

Visibility of all user stories with its:

● Level of complexity. ● Current situation.● Developer in charge. ● Review of the customer stories at SPRINT meetings. ● Agreed resolutions and establishment of priorities.

19

Team

Project teamEach project is unique and it demands an integrated multi-disciplined team that ensures the contribution to each of the project dimensions.

In the ASP team there are:

● Project Manager● Designers● System Administrator● Web Developers

21

Project Manager● Does a thorough follow up of the project.

● They become the bridge between the customer and the development team.

● Is in charge of mitigating dependences.

● Checking that the product implemented fulfils customer needs.

● Auditing that partial deliveries are done properly.

● Verifies that the team structure is the most adequate for the project.

● Coordination of team member in each phase of the project.

22

System Admin.● Specialized in internet platforms, web servers and

databases.

● Does the platform installation.

● Carries out platform operation.

● Responsible for platform monitoring.

● Management and recovery of backups.

● Preparing the initial setups.

● Configuration of integration machines as well as production ones.

● Preparing the deploy process with the help of the technical manager from each project .

23

Designer● Study of the most adequate navigation structure.

● Study of the most appropriate information architecture.

● Study the most suitable content structure .

● Developing functional designs (wireframes).

● Implementation of the graphic lines of the application.

● Layout of html5 and css3 designs.

● Testing designs on the agreed navigators within the requested solution.

24

Web Developers All our project teams have several developers plus a technical manager and a technical director

CTO:

● Manages best practices. ● Identification of global improvement plans. ● Advises the technical manager about the project

architecture, if necessary. ● Standardizes the way the whole technical team

works. ● Verifies excellence of the development.

25

Web Developers Technical Responsible:

● A developer who takes over the role of main developer in a project.

● She / he decides on the day to day changes to the project architecture if required.

● He / She is one more involved with the development team.

● In charge of deployments.● Support 8x5 in case there is any problem in the

application.

26

Web Developers (II)Developers:

● They design and build project architecture.● Design and building software. ● Identification of the best tools and libraries. ● Point out the best technical solution.● Identification of architectural improvements.● Identification of performance improvements.● Watch over the project to be the most accurate possible,

according to best practices.● Evolution and maintenance of basic software versions.

27

Some of our projects https://aspgems.com/proyectos

29

Abbvie

30

Telefónica

31

BBVA

32

Sanitas

33

Aegon

34

CharHadas

35

Samyroad

36

beRuby

37

vianoleo

38

ESL

39

Grinbuzz

40

Cuidamos tu coche

41

https://collaboratorium.biz/

42

Dontknow.net

Gracias!!!!

43