Development Process
In this document we will outline our process for development, how we plan to achive our goals, the toold we use and how we prioratize things.
Most likly some work has alredy need done on the product or topic you are working on, determin what stage you are at, review the work that has alredy been done and follow the next steps. It is crucal no spets are skipped as this will slow you down later on.
Our first prioraty is to launch many products so we are established as a marketplace rather than a single app, we will achive this by priritizing MVP releases rather than fully developed features and following each step listed here.
Process
Research
Most likly some business research has alredy been performed, review them and see how it can jump start your development research, (e.g. perhanps what is deemed as a competitor in business can be a great API provider).
Use the "template research document" to keep a recod of your research and write your conclusions
Planning
Once you know what tools, API, etc. are avalible to you, the data you will need etc. update the documentation as you and your team will need it to guide them throughout the development.
MVP
As mentioned before, it is important that you don't try to build a full product but rather only a "MVP". What qulifies as an MVP, how do we achive an MVP and what to do after release?
We have a few options as a starting point, we can find an API that enables the features we want, we can buy frontend code that gives use a complete "Products" and we do not need every feature ready.
-
First, Backend
focuse on the "Backend", ensure the product or feature you want to build can be handled by our backend and database, expand the data fields if needed and create function to handle any new API connection you might need. Before you build new functions refer to your research to see if an API is avalible.
Always check existing functions, don't douplicate.
-
Second, Frontend
develop the nesosary widgets and state management, search on codecanyon for anything that can speed up the release even if it dosn't look exactly like we want.
-
Third, Refactor & Redesign
Once a product or feature has been released we can start to focus on it's refactoring to fit our clean code starndereds and redisighned to match our UI and UX.
To get a more detailed understanding of tech development process, see the following documents
Test & Release
Once your MVP is ready for launch follow the "Testing Process" and "Release proccess"
Etirate
Now that you have released the feature or product, be sure to monitor for bugs, regularly check statistics and get user feedback, use this knowlange to elaborate on the MVP and bring it closer to it's fullly developed goals.
Plan
The process of development will be as follows.
Our first focus will be the state management and API connections, we will establish all connections needed and test the models to ensure all features work properly, this will ensure all functionality is working for Milestone One and the connections and data is secure. Then we will focus on the User Experience, User Interface of Hudi, once that is complete we will switch our focus back to State Management and improve what we originally built. We will determine what would be better off being moved to the backend and make notes for future development.
Means
We have talked about the process of how we do things, now lets look at how we manage this process and stay orginixed.
Scrum
We will work in an agile, Scrum model, in sprints of two weeks (Monday to Friday), each referred to as a “Sprint”. The status and other details on "Tasks" and "Issues" should be kept up to date and should be complte by the end of the sprint. A pull reqest should be opened in acordence with the "Release Scheduale" and branching should be kept orginized with our "Branch structure".
Project & Task Management
Our Sprits are orginixed using tasks and issues within GitHub.