Agile approach

Scrum

Scrum is one of the leading agile development methodologies aimed at business value. Here we work in a small, cross-functional and self-organized team and spend a little time building a small thing but in a high quality, ensuring it’s a potentially useful version of working product and regularly integrating to see the whole.

By the pillars of transparency, inspection and adaptation it creates values for clients and the team like commitment, courage, focus, openness and respect and builds trust for everyone.

We use Scrum for COMPLEX projects, that is to say:

  • very complicated: lots of parts and lots of interconnections

  • highly uncertain: there are likely to be many changes or disruptions

  • heavily time-constrained: there is no time to sit back and re-plan sensibly – disruptions need working-around immediately

  • stakeholders don’t 100% know their requirements and technology

  • there is a high risk of failure

Kanban

Kanban is another agile methodology, a visual process management system that helps promote the improvement of production systems in various industries. It helps resource planning, ensures transparency, and lets your teams focus on their work to create better quality products faster. Here we have a perfect flow visualization, no need in sprints and estimates which leads to flexibility and maximizes the productivity of a team by reducing idle time.

We use Kanban for projects that require an ability to change requirements on the fly and to release anytime. Customers can provide honest feedback and request changes during a particular iteration while preserving the timeline and keeping the budget in check.


Traditional approach

Waterfall

Waterfall model is simple and easy to understand and use. It consists of initially determined phases which are Requirement gathering analysis, System Design, Implementation, Testing, Deployment of System and Maintenance. Here, each phase must be completed fully before the next phase can begin and each phase has specific deliverables and a review process. Phases do not overlap.

We use Waterfall for smaller projects where requirements are very well understood, well known, clear and fixed.

It works well only when

  • product definition is stable

  • technology is understood

  • there are no ambiguous requirements

  • ample resources with required expertise are available freely

  • the project is short