Share on FacebookShare on LinkedInTweet about this on TwitterShare on Google+

Inovatica works with Agile methodologies influenced by Scrum. We work closely with the client from the very beginning of the project, through requirements gathering, development, testing, and delivery. We work in iterations (sprints) with regular deliveries. Our work is transparent so the client always knows what we’re working on. After each sprint, we demonstrate the product and adjust the process according to the feedback and outcomes. Our main focus is always on the user. That’s why all project requirements and testing criteria revolve around end-user value.

For us being agile means we can be more flexible and deliver maximum value thanks to the well-defined tasks and short sprints. Working in iterations makes changes possible – priorities can be amended after each sprint. It also makes tracking team’s performance easier so that the estimates of our work can be very accurate.  This, on the other hand, makes sure resources are directed to the most appropriate areas and requirements are tailored to fit the budget.

Steps of delivering software Inovatica’s way:

  • ANALYSIS

The first and most important stage of the delivering software is the analysis. At this point, we focus on visioning what the client wants to achieve. We consider users/roles, challenges, goals and gather all requirements. We always try to put a lot of effort in user interviews, assessing risk and prototyping, because we believe that building on a solid base is the only way of making great solutions.

Deliverables:  users/roles, challenges, goals, requirements, user interviews, risk assessment, prototypes

  • DESIGN

While graphic design comes later in the process the next step includes creating user flows, road mapping, setting design principles and choosing the best technologies. When it comes to the last point you don’t need to worry if you’re not sure what technologies you need. That’s exactly why you have us as your partners and advisors.

Deliverables:  user flows, road maps, design principles, technologies

  • PLANNING/ESTIMATION

Planning is equally important as it prioritizes the work and above all helps to produce quality work and stick to the schedule. Define project objectives and milestones in terms of concrete results.

Deliverables:  feature epics, milestones, resources

  • BACKLOG

Another step involves setting up a list of features/tasks to be completed within a framework of the project.

Deliverables: list of features/tasks

  • SPRINT PLANNING

Picking appropriate tasks from the backlog so that they can be completed in each 1-4 week sprint.

Deliverables: a list of tasks to be completed in the sprint

  • DEVELOPMENT/SPRINT EXECUTION

That’s the moment when due to the previously settled ground the team can easily perform all the actions, mainly coding,  to meet the sprint goal.

Deliverables: code

  • TESTING & QA

Making sure every element of the solution works in line with the objectives of the project specification.

Deliverables: assured quality

  • DEMO

Consequently introducing developed part of the solution to the client and gathering feedback.

Deliverables: solution or a part of it developed during the sprint

  • IMPROVEMENTS

As a result of the demo feedback, we’re implementing necessary adjustments

Deliverables: a solution that answers to the real needs

 

  • DEPLOYMENT

Finally and officially adding the sprint outcomes to the whole project or launching the final product.

Deliverables: working increment or product

  • SPRINT REVIEW

Meeting held, to sum up the work, inspect the increment and adapt the product backlog if needed.

Deliverables: updated schedule (if needed)

 

  • RETROSPECTIVE

Last but not least it’s time to reflect on how we’re doing on the project so we could find ways to improve the process of delivering software.

Deliverables: a list of ways to improve the development process

 

Have a project in mind? Need help with existing applications?

Tell us about your project or see what we offer