DEVELOPMENT
Our software engineers develop engaging mobile and web applications using leading technologies and frameworks. We code to high standards and test continuously, working under agile frameworks.
Let's start working together!
HOW WE DO IT
Pre-development Planning
Active Development & Testing
Sprint
Planning
Sprint
Execution
Sprint
Retrospective
Sprint Review +
Product Demo
Launch
Ongoing
Development
Maintenance
1. PRE-DEVELOPMENT PLANNING
Like on any other process, its important to properly prepare before developing a product. This ensures an accurate, effective, and efficient workflow. In this phase we will assemble a development team, execute a design to development handoff, determine the project milestones, create stories, and plan sprints.
ASSEMBLE THE TEAM
We’ll put together a tech team according to the needs of the project. The typical roles are devs, QA engineers, designers, and PMs.
DESIGN TO DEV HANDOFF
In this meeting, we will review the design details to make sure that the product is developed pixel-perfect.
PRODUCT BACKLOG
We’ll create a backlog of user stories, which describe all the requirements in a simple way. They include a time-estimate to complete, and will be assigned to devs during active development.
ROADMAPPING
Determining a product roadmap with key milestones and version releases, helps to prioritize, plan, and make the right decisions during the active development phase.
2. ACTIVE DEVELOPMENT
Once pre-development planning is completed, we’ll proceed to actively build the product. According to the roadmap, the backlog will be splitted into two-week sprints. On every sprint, user stories are assigned to each Developer and designer, and when completed, Quality Engineers will review them.
SPRINT PLANNING
On day one of each sprint, the PM assigns the user stories that must be covered by the devs and designers during those two weeks. QA Engineers define a testing plan. All the tasks are detailed as “to do” in a Jira board, which is accessible to everyone on the team, including the product owner.
SPRINT EXECUTION
During the sprint, each one works on their tasks. Designers keep on building or improving the UX/UI; Developers make progress in the features and perform unit and integration testing; QA Engineers test for quality; and the PM and Tech Leader are responsible for putting everything together.
SPRINT RETROSPECTIVE
At the end of each sprint, the team will have a meeting to discuss if the tasks were completed in time, if estimations were accurate, if there were any unforeseen difficulties or challenges, and if everything is on track.
SPRINT REVIEW + PROJECT DEMO
Sprint Reviews and demos are collaborative working session at the ond of each sprint, were the team shows what was accomplished, and stakeholders provide feedback.
3. LAUNCH
Once all version releases have been completed and have successfully fulfilled all the client requirements, the application is ready for beta testing.
Eventually we will do a public or internal release.
4. MAINTENANCE
Once the product is released, there are two ways to go.
IF YOU JUST NEED TO MAINTAIN THE APP RUNNING WELL...
ONGOING DEVELOPMENT
We’ll keep the team together, or adapt it to the new needs of the project. We’ll work on a new roadmap, and keep on designing and developing new features. Now that the application is already live, we’ll be able to use real user feedback when decision-making.
IF YOU JUST NEED TO MAINTAIN THE APP RUNNING WELL...
MAINTENANCE AGREEMENT
The maintenance agreement determines a monthly number of hours our team will dedicate to maintaining the app. The main activities are error monitoring, bug reporting and fixing, performance optimization, and updating versions, integrations, and dependencies.
