What is the order of application development?

Question

iOS

There is a ready-made design on how to organize the development of a mobile application using the scrum methodology.
What to do first, make up all the screens, and then tie up the server part?
Or at the same time - to make up an authorization screen, for example, to tie it up with the server - passed the sprint?

Answer 1

Scrum has nothing to do with the sequence of layout or parallel work.
For starters, it’s better for you to just somehow organize the work, without any scrums. And then you will think whether you need this scrum or not.

Answer 2

In general, it is better to understand it in practice, for example, we make blocks at once, that is, a screen with logic. Once you've done one, move on to the next one, and so on. We only do layout if the server is far behind, and, for example, it’s not convenient for me: to do pure layout (which means that you need to come up with test data yourself, at least, and fill it in to see if everything is displayed correctly, and so on , and so the server will come and okay.

Answer 3

Management in this vein takes the form of analytics. In order to draw up a plan and plan actions, it is necessary to understand what the entrusted resources (people) are capable of. Wherever the manager's competence is lacking (for example, in questions asked by the author), the performers must answer and take responsibility. And actually negotiate, plan and work together. If it doesn’t work out and there is an imbalance of resources and no one is ready to take responsibility, then look for suitable resources (change the manager, performers, hire a shepherd team leader).