Agile Software Development


We have designed our own software development process based on the best practices of Agile methodologies such us Scrum and XP. This, in combination with the use of our powerful toolset, helps our team to facilitate their work activities.

Transparency

Our clients are given full access to all our tools to track the status of every project.

Practices

Daily meetings, continuous integration, peer reviews, pair programming, QA reviews.

Support and guidance

We are by your side through each step of the project, until its completion, providing support whenever you need it.

  • TOOLS SETUP

    Client and Project Wiki, SVN, Artifacts repository, clients' user accounts, Scrum management, bug tracker.

  • Kick-Off Meeting

    Project objectives and risks are presented to the team.

  • PRODUCT BACKLOG

    Together with our client's Product Owner, we define the product backlog, which consists of the full list of project stories.

  • PROJECT PLAN

    Sprints, Peer reviews and QA activities are planned.

  • SPRINT PLANNING Meeting

    In a time boxed meeting we define the product backlog items that we're going to work on during the Sprint.

  • TEST-DRIVEN Development

    No test, no glory! Writing unit and integration tests is an important part or our work. It's in our genes.

  • CONTINUOUS INTEGRATION

    Test-driven development is worthless without CI. Our CI server automatically runs every test with each new commit.

  • SPRINT DELIVERABLE

    At the end of the Sprint, a new incremental release of the product is available for our client's review.

  • FINE TUNING

    Stress and scalability tests, usability enhancements, code and documentation review.

  • CLIENT ACCEPTANCE

    Our client's feedback is always important, but at the moment the project is coming to an end, it's our most crucial concern.

  • Production DEPLOYMENT

    At this time, we're ready to go live! We help our clients to set up the required infrastructure for production deployment.

  • Project RETROSPECTIVE

    The project is not finished until a retrospective has taken place. In this way, we learn and improve from the experience.