Hello Cyan,
It is a very interesting point you raises here! I should have explained in the introduction, we had a long meeting with the client before we officialy start the project where we discussed together what features to build and how the app should look in the end.
Moreover, we had a weekly meeting to check that the project is going in the right direction.
Lastly, we organized our work and filter requirements according to what we are able to do as junior developers.
Thank you for reading, I hope this answered your question! 😇
Wonderful article.
But I am missing something.
You didn't tell us how did you go for the actual requirements process?
And last but not least, at which point did you gather the requirements? Before UI/UX Design and Data Modeling?
How did you model the data and design the UI? Based on features?
Please share, or write a new article about this since this is the first step where new comers stumble upon.
Thanks
Hello Cyan,
It is a very interesting point you raises here! I should have explained in the introduction, we had a long meeting with the client before we officialy start the project where we discussed together what features to build and how the app should look in the end.
Moreover, we had a weekly meeting to check that the project is going in the right direction.
Lastly, we organized our work and filter requirements according to what we are able to do as junior developers.
Thank you for reading, I hope this answered your question! 😇
This articler worked one year.