Softwell serviços 15102012

Post on 11-May-2015

88 views 2 download

Tags:

description

Softwell approach to agile application development.

Transcript of Softwell serviços 15102012

Our approach for solving business problems with customized

applications

Agile Development

António Gonçalves

Who we are and what we do

AD – Agile Development

AD – How we do it

Agenda

Grupo Freire

Who we are and what we do

Renewable energies

Consultancy

Advertising

Software

Communication

2010 2011 20122008200720062000

Who we are and what we do

Idea conception to facilitate internal development. Maker 1.0

Maker is used internally to build applications. Softwell is established to sell Maker

Maker 2.0. Maker 2.4 is released

Lisbon Office

Strategic shift from selling Maker to

application development

Strategic shift from selling

Maker to application

development

Maker Mobile

Maker to develop out of

the box applications to

help our clients to solve business

problems

Who we are and what we do

• Low productivity in application development

• Quick technological innovation• Learning curve• Technological dependency• Applications maintenance• Collaborative development

Who we are and what we do

Development is 100% visual not a single line of code

Who we are and what we do

Development is 100% visual not a single line of code

Who we are and what we do

Development is 100% visual not a single line of code

Who we are and what we do• Why use Maker instead of another platform?

100% WebTechnology

independentScreen

independent

Project documentation

Development productivity

Application complexity

Geographic dimension Development

collaboration

Application maintenance

Learning curveUsers talk good

things about our applications

Who we are and what we do• We make business people work together with the application developers

Who we are and what we do

AD – Agile Development

AD – How we do it

Agenda

AD – Agile Development

AD

Process analysis and design

Process redesign

Implementation

Design

Modeling

OperationControl

Optimization

AD – Agile Development• Process scope – The scope of our applications usually is focused on the 3Bs that

make the core of the organization’s business value chain. We develop applications that above all try to automate the operations of the organization’s specific business processes. Those are the activities that usually are difficult to have in an out of the shelf software.

B2B B2C B2E

AD – Agile Development• Functional scope

Document Management

Forms and fields

managementSecurity Report

managementProcess

management

AD – Agile Development• Our applications are usually integrated with the ERP system because…

Finance

Purchases & Stock Management

Human Resources

ManufacturingSales

ERP

AD – Agile Development• …is our conviction that developing in the ERP framework has a bigger TCO and is

riskier than building the application in Maker and then integrate with the ERP.

Integration

Develop.

Specific

Licensing

Develop.

ERP upgrade

• Master data• Sales data• Manufactoring data• CRM data• …

Mobile functions

Internet access

Who we are and what we do

AD – Agile Development

AD – How we do it

Agenda

AD – How we do it• Because what we do is so specific to the customer’s business:

• We have no pre-conceived ideas• We do not present products or other kind of arguments that might skew the

customer’s idea• We can show implementation scenarios that might be framed in the customer’s

business needs• We listen to what the client has to say and see what the client has to show• We ask questions and give opinions that are based in our experience• With the client we create a solution ... and a way to get there!

AD – How we do it – Scenario 1• We divide the application development in n user tests. Each user test can

approve what has been done. Only after all the application’s features are ok we move on to the development of the application’s layout

Business needs blue

print

...n×

AD – How we do it – Scenario 2• We divide the application development in n phases. Each phase is a Scenario 1

implementation.Phase 1 – Features’ scope must be completely defined for each phase. When phase’s scope is defined it cannot be changed. New features should be implemented on the following phases.

Phase n

...Phase 2

AD – How we do it• Business needs blueprint – Document where we define the different visions for

the application. We have in each area different templates which help implementation teams to rapidly transfer the business description into Maker’s forms, flows and reports.

Business flowchart Interfaces Fields and forms Reports and documents

Business needs blueprint

AD – How we do it• The application could be deployed in the client’s IT structure or elsewhere in a

supplier of IT structures.

Licensing Cloud Outsorcing

Thank you for your attention!

Any Questions?António Gonçalvesantonio.goncalves@softwell.pt