A lot of being productive as you gain more experience is by working on the right things, so you produce more with same amount of effort. What this means is you

A lot of being productive as you gain more experience is by working on the right things, so you produce more with same amount of effort. What this means is you want to start with figuring out goals. What is the project's goal? What are the constraints? Why are things being done the way they are? What does success mean? Once you know that you can start doing tactical stuff (and since answering those questions can take a while you can probably do lots of other stuff in parallel, as discussed in other comments). Two relevant practical talks, from PyCon that was this weekend: 1. I gave a talk on how to choose how and where to test your software (https://www.youtube.com/watch?v=Vaq_e7qUA-4&t=63s https://www.youtube.com/watch?v=Vaq_e7qUA-4&t=63s). 2. Awesome talk on how to structure documentation - prose version at https://www.divio.com/en/blog/documentation/ https://www.divio.com/en/blog/documentation/, video version at https://www.youtube.com/watch?v=azf6yzuJt54 https://www.youtube.com/watch?v=azf6yzuJt54