Here's a very broad summary of the custom software development process that I use. The real development process is not nearly as linear - if it were graphed, it would seems like a spiral, where Analysis and Production Stage tasks are joined on as needed bases. However, this basic version can give a general idea of the stages and processes involved.

Initial Consultation > Analysis Stage > Production Stage > Delivery Stage

Initial Consultation. First we want to get a general idea about the application development-related needs and requirements and technical requirements. After that I will put together a short written proposal for the app development. I will not charge for these initial steps.

From here, we can proceed in different methods. We can start the development procedure after just one or a few initial meetings. However, for bigger projects, it is suggested that before the application development, we will do necessarily thorough business analysis and will put together an application description that meets the user’s needs and requirements. Most of this website content highlights the latter approach.

Analysis Stage.
I start charging once we have decided on the development approach. If we continue in an agile manner, so that we start on the application development right after the first meetings, the Analysis Stage and the important processes blend in with the Production Stage work.

As was pointed out above, for bigger projects I would prefer putting together the application's description (that I call Users Requirements Statement). In this document I describe the application in detail, its achievement deadlines and cost structure. Unless agreed on otherwise, Users Requirements Statement will amongst other things also contain application development fixed price and development aims that I will honor.

In some cases stable price and deadlines are not in the customer's best interest. We will go over all the relevant details during the initial consultation and the Analysis Stage.

Putting together this important project planning document and roadmap needs quite a bit of work: communication with the application's future users and related analysis. However, as a result I will be able to verify with the users that the application that will be built is really what they need and want. This roadmap also saves a lot of time during the next development stage.

Production Stage. The rest of the development will concentrate on meeting each essential step's objectives and deadlines by using and mixing, as needed, efficiency and creativity-oriented project development styles and methods.

The project development and management methodology that I use places a heavy emphasis on understanding and executing the user’s needs and wants. Working remotely means that some of the communication processes take place differently and some of the development steps are handled differently. However, it does not mean that there is less communication with the application's future users.

Delivery Stage. After all the necessary testing, bug fixing and functionality verification the application is installed. I may do user training either myself, or together with selected user group representatives.

Depending on the conditions, most of the development can be done off-site, but installation and training usually take place again on site.

Significantly more detailed information on the mobile app development process can be found from the Application Development section and from the IT Project Management section.