How we work

How We Work image

We are Agile. Through absolute commitment to transparency of everything we do, we strive to deliver the highest possible quality and reduce risks across projects.
Our work process is illustrated with the Product Development Lifecycle.
It describes the steps we take to turn the initial idea into a working product. Our work process is visible to everyone involved in the product development.

1. Analysis

  • Collecting all product requirements from the client
  • Analyzing the needs, demands and problems that a product should solve
  • Good communication is essential here

4. Project preparation

  • Assembling the team
  • Creating a board on VivifyScrum.com
  • Adding User Stories to the Product Backlog
  • Prioritizing stories after consulting the client
  • Creating a plan for delivering the product

7. Test release

  • Test installation is created at the very beginning of the project
  • It is accessible to the client from the beginning
  • “Done” User Stories are deployed to test installation to be accessed and tested
  • On test installations, we occasionally do “mob testing”

2. Creating the product draft

  • What functionalities and features will the product have?
  • Organizing design workshops
  • Creating the initial product structure
  • Defining target audience for the product
  • Creating wireframes
  • The result - formulating a defined scope of the product

5. Design

  • Creating high fidelity mockups based on wireframes
  • Using Invisionapp.com to present mockups and get feedback
  • UX review
  • Frequent validation with the client

8. Production Release

  • Once the User Stories are done and the client considers that we have a Minimum viable product (MVP), it’s time for the production release
  • Product life on the market starts here

3. Estimation and proposal

  • Dividing the project into User Stories (tasks)
  • Defining the initial technology stack
  • Determining the optimal team size and composition
  • Estimating every User Story
  • Creating the cumulative estimation
  • Sending the proposal to the client

6. Development

  • Development team is organized in Scrum or Kanban framework
  • QA defines Test Case scenarios
  • Developers work on User Stories
  • Developers test a Story against predefined Test Case scenarios
  • Code Reviewer analyzes code
  • QA tests a Story
  • Once a Story is completed correctly, it is marked as "Done"

9. Maintenance

  • The Team is restructured if necessary
  • Fixing bugs
  • Implementing new features and improvements
  • The Product Increment is created and applied every 1-4 weeks