I'm planning, with a small group of friends from uni, to develop a medium-small sized project during our break. We intend to work at the same time in different parts of this project, so we will need to coordinate our work in a way that allows us to know what has been done and what needs to be done.
I'm wondering what would be the best (perhaps standard) way to do this. I'm thinking that modelling our project could probably help us do this fluently, but I'm unaware of what kind of model we should use.<p>If having an example project helps to the answer, I think the scope will be something similar to developing a gameboy color emulator. We're about 5 people, working at different rates.<p>Do you have any suggestions ? Thank you.
Don't overthink that. Talk the goal through, draw some boxes for what pieces exist on a (virtual) whiteboard, then talk through interfaces as needed, start working, clarify. That's fine for that scope and having fun, and you'll probably learn more from where it's not sufficient than if you try to overdesign something from the start.