With a Project Brief known (#6), the team needs to agree upon how the Python classes of the project will be named. In that way, the whole team can start coding at the same time :-)
As a group, make a list of classes the majority thinks would make sense to have:
one member suggests a class
each other member use Zoom yes/no to indicate if it makes sense to him/her
keep classes with a majority vote
the person that suggested the class becomes the owner of that class, i.e. he/she may veto on the technical implementation of it. A person owns one class maximally, so ownership of a second class must be transferred
Use a shared document. Class names are CamelCase, for example SimulationParameters, as is used in PEP8.
The end product must be similar to a table like this:
Depends on:
With a Project Brief known (#6), the team needs to agree upon how the Python classes of the project will be named. In that way, the whole team can start coding at the same time :-)
As a group, make a list of classes the majority thinks would make sense to have:
Use a shared document. Class names are
CamelCase, for exampleSimulationParameters, as is used in PEP8.The end product must be similar to a table like this: