Four hours per day is normal. I used to work for an organization that used PSP/TSP https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=5283 https://re

Four hours per day is normal. I used to work for an organization that used PSP/TSP https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=5283 https://resources.sei.cmu.edu/library/asset-view.cfm?assetid... https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=5287 https://resources.sei.cmu.edu/library/asset-view.cfm?assetid... As a participant in that methodology, the SEI gives you access to data gathered over thousands of software development teams. One of the findings is that the average time per day spent across all development processes (from getting requirements to testing) was about 2-4 hours. That number is surprising only to people who don't accurately and religiously track their time. Guesses are useless. We found that it took about a year for everyone to really get good at time tracking and to reinforce others ("hey, George. I was looking for you before and I noticed you weren't at your desk, but you timer was still running") to get better. After doing that, we found that our time fell into that range. The Test team was at the higher end with 6-8 hours when executing test cases for days on end and newcomers were around 4-6 which we attributed to them having fewer distractions. Experienced/senior engineers were usually around 2-4 hours/day. So, all in all, I'm not at all surprised by your results.