From idea planning to a working software & satisfying results!

Ready, set, go…

We use iterative software development methodology where the final product is built piece by piece in sprints. One sprint usually lasts between 1 to 3 weeks.

At the start of the project we set a planning meeting. As a result of the planning meeting a prioritized list of project tasks (backlog) is generated.

Let’s Scrum!
Step by step through sprints

Each sprint starts with a planning session. The outcome of the sprint planning session is a list of tasks that will be delivered during that sprint.
During the sprint the tasks to be built, are completed in priority order to provide the most valuable business functionality as early as possible.
During each day of the sprint there is a short daily meeting (max 15 minutes, possibly via Skype) together with your representative.
Tasks are considered completed once the agreed completion criteria is met. Completed tasks can be reviewed by your representative at any time during the sprint.
At the end of each sprint all complete tasks and built product features are demonstrated to stakeholders in a demo session where comments are highly appreciated.
At the end of each sprint retrospectives (retros) are held. It is crucial for improving the product development process and gathering feedback about the progress of the team.

Customer first!
This is how we keep you in the loop!

Dedicated customer representative is involved during the whole product development life cycle by being available for the team on daily basis.
At the end of each sprint a demo session is held for the stakeholders. This way we can ensure that the product is moving in the right direction
Your representative presents the highest priority tasks at the sprint planning session to the team and the sprint tasks are always discussed through.
Your representative can participate each day in the daily meetings with the team and the completed tasks of the sprint can be reviewed by your representative at any time during the sprint.
Backlog is generated and prioritized in collaboration of you and the team. You can modify and specify the backlog at any time during the product building life cycle.
During retrospectives your representative can reflect on what could be improved and what is working well. It is an important part of improving the product development process.

Trusted by