Hi,
On a minor project, I suggest you to create only 1 solution, which you work with through deployments. You add components needed to your solution and export the solution package to the other environments. When you need to make changes on your project, you simply work with your already created solution, add or remove components and re-export the package as a higher version, which you redeploy in your environments as needed. Once created, components are unique and available to add in solution. In a unmanaged environment, a component can be added to many solutions, but still be unique and remains the same through all solution. It means component changes will be the same through all solutions since it is the same component. Solutions are simple containers.
If you have a bigger project, you can create 6 solutions, a solution for each component group types:
-1_Webresources;
-2_Customization; (tables, forms, views, businessRules)
-3_Security roles;
-4_ReportsAndDashboards;
-5_FlowsAndWorkflows.
Then, you deploy each modified solutions in that order to prevent dependencies errors. So, if you have many solutions changed, use this order (1 deployed before 2, 2 before 3, 3 before 4 and 4 before 5).
I hope it helps!
_____________________________________________________________
Please click Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like.