Methodology for planning a mobile app

Question

Methodology for planning a mobile app

Navigation

#1 by (2 votes)

0

Background :

I was thinking of starting a mobile app project myself, but not to be tiresome and with no perspective of ending, I thought of organizing the activities in the Kanban method, after prioritizing the important aspects of the app, I noticed that reading the activities still had difficulty abstracting and visualizing the final product. Home I would avoid leaving vague details as I know that everything must be defined before it is developed, avoiding changes in course in the middle of the project and thus its extension, so I thought that an appropriate methodology for the mobile development style could be adopted. Home When looking at the subject, I could not find a solid methodology, only some articles suggesting to adopt some positions towards development, so I had some doubts like:

Is there any methodology for this kind of development that I did not find?
Using an agile common software methodology such as scrum is feasible?
Is there anything other than Kanban that helps in project organization and results in faster development?
[ Offtopic ] Using a class diagram to better abstract the program is something necessary and will I be the only responsible developer?

metodologia mobile

asked by anonymous 09.06.2017 / 19:06

1 answer

Redirect domain to given server folder via htaccess Adding inputs with jquery and real-time

score 2 · Accepted Answer

Thinking about App Mobile development can also be seen as the development of any software.

You can find some methods that may have been created that focus exactly on mobile development. Particularly I do not know any in particular. But I believe that your Organization and focus is what will be paramount in the final delivery quality of the solution.
The use of agile methodologies has more to do with the size of your project than with the type of Software you are developing. From an ERP to an Application, techniques like Scrum can be used. In the end what determines the need is your goal of organizing the development activities. For longer projects it would really be a good way to organize and maintain the schedule of all the activities of a TEAM.
I also do not know anything that can meet this requirement mentioned in the third topic. But in front of your scenario the initial planning you have done will most likely be enough for the project to be properly developed within your time frame. The speed of delivery will depend only on you.
Whenever possible I like to use class diagrams to develop my projects, so I advise you to do it, just so you can better predict everything that will be created and already filter possible implementation failures even before the code was written .