In the first step, we work together to define a set of ‘User Stories’. These user stories capture all the functionalities that will be available to users. If there are multiple roles in the app, these functionalities are divided based on the role.
For example, user stories in a Medical Software application might be statements like “Patient should to be able to login to the app” or "Caregiver should to be able to add new patients” etc.
In the second step, we take those user stories and design a set of wireframes, storyboards, user flows and prototypes. We try to learn about our target users as much as possible, and design how they interact with the app in a way that would be most comfortable for them.
The feel and look of your app is designed in this step, and hence this is where we will have to meet a few times and make sure the end result is aliged with your vision.
At this point we will start the development of the application. We will follow Scrum methodology. We plan sprints of 2 weeks, and at the end of each sprint we deploy the progress into a staging environment. You can always refer to this environment to test your app as it is being built or get your users feedback.
These sprints can be modified as we move forward. So if your users give you feedback about a specific functionality, we can re-arrange the original sprint planning to apply their comments before getting to new features. It is all flexible!
This is probably the most important part of your product development process. A lot of methods are used to gather analytics about how the users are interacting with the app. Which features are being used, and which ones are not. Having these data in hand, we can go back and trim the design in a way that fits our users behaviour the most.
One example of a method we use in this stage is A/B testing where two different behaviours are implemented and presented to different groups of users, and their results are compared to update the functionality.
Whenever you are ready to release an update to the production environment, we will get the stable version from the staging environment and release it to the public. We use several automation tools for this process, and hence the release cycles can be as short as our sprint length.
This is when you can start your marketing campagin and gather more data from a broader set of users.