Business Process Modelling
BPM means formalizing and mapping business processes down to the application activity layer. Usually, the business process includes different roles. We design BPM flowchart for each role. The proper result of Business Process Modelling a set of UML diagrams (or flowcharts) that are clear for all roles. The convenience of this method is in the ability to combine (or postpone) multiple models before implementation in the application.
Another advantage of this technic is monitoring and analyzing. The formalized process can be monitored and scaled.
Here is a custom example of BPM model for booking a trip:
Minimum viable product
Based on the amount of BPM models we take key features only and build a minimum viable product. MVP gives us ability to talk about work scope and money. Indeed MVP is very famous and I don't want to write a lot.
My checklist of a good MVP:
-
Best is the enemy of the good. Product should not be ideal.
-
Minimum doesn't mean uncompleted. It also doesn't mean poor quality.
-
Product should be finished. It is usable.
-
We are able to analyze feedback.
- We have enough users of our app
- Users are able to leave feedback or bug report
- Facebook Pixel (or any other analytics tool) is set up and we have a conversion
Project estimation
All clients want to control the budget and understand how much it will cost. Technics described above allow the client to manage the budget and have a clear understanding of how the application is developing.