This is something we think a lot about at Kyso (https://kyso.io/for-teams) - my startup - we let teams manage analytics knowledge basically by letting teams share Jupyter notebooks - we've spoken to lots of people about how the organise them and are writing a guide really soon that sounds like what you want.

- Keep all your teams notebooks in one place (not on laptops)

- Reuse them liberally (the %run command is excellent and often better than creating python libraries)

- Most important of all is make them readable documents not just list of coding commands, that means you should title things clearly, explain what you going to do.

- Label everything, axis labels are needed on almost every chart, and also make sure you put a title and description for every chart.

- Separating your project into processing and presentation notebooks is really helpful. So one notebook for data prep and another for plots and explanations.