Process

How we do it !

Y

Listen

Yes of course we listen. You are paying for it!
If you know what you want and is already out there, this doesn’t means we need to copy it! We like to have an honest and fair discussion [tea included]. We need to build our trust. Trust is the base for the grand plan. We defined together the goals and product requirements which should define the macro view of the project plan. We need to understand your business model and collect data for insight and opportunities. Then we’ll apply the strategy and define the road map for designing the right solution.

It doesn’t matter if is a flyer, a logo or an eCommerce website. The care and support has the same level.

(

Design & Build

Yes there is a methodology like this. It’s ours. It’s unique due the current external factors like: time, resource, product on market. Everything we do is a repetitive cycle uniquely defined by the time frame, resources [technology, team capabilities, general knowledge] and product on market. We try to respond to a few questions:

% How quickly does your product need to be on the market?
% What is the number of features your product needs to be viable on the market?
% What is going to be your product in 6 months from launching?

w

Architecture – Scalability, Dependencies, Risks

We answer most of the questions in our LISTEN session. We do Architecture alongside with the development plan and the entire integration definition. There is not any separation of concerns. Of course we are keeping in mind the scalability, dependencies and risks. Everything is defined in the project plan and development architecture.

8

Prototyping and Maturity

We start working with prototyping, quick and dirty. In initials phases we do repetitive small releases. Then based on the feature completion checks we extend continuously the product based on goals and requirements. When you develop we apply daily QA, bug fixing. Improvement comes along with the pre-releases.

7

Measure to Improve

After first production release, it’s only the beginning. Then we start analysing using tools like Analytics or UI and Code Improvement Standards and Trends [effectiveness is important so refactoring is one of the elements that we consider] and on-going support to ensure that your product doesn’t stand still in its on-going pursuit to find a better way.