Eg: Assume a task has been estimated to take 8 hours working time, for 1 person to complete. Supposing that person takes a break of 15 mins every 2 hours. Obviously the task will take 1 hour extra and, assuming an 8-hour working day, will now be completed only the next day.
1. Should breaks also be entered into the plan, during the Tracking phase?
2. Should these breaks be entered using the “split task” tool (on MS-Project). Alternatively how can a break be represented in MS-Project?
3. If breaks aren’t entered, planned completion dates of tasks would be inaccurate.
4. Would the resource involved really be interested in exposing breaks while tracking the Project Plan? How should this motivational issue be handled?
5. On MS-Project (an older version), beyond a certain number of splits in a task, the task is inaccurately represented on the Gantt chart.
Regarding, representing breaks while tracking the plan, I quote the following SE post >
"The best practice as far as I'm concerned is to measure down to approx 15-30 minutes what time you've been spending on what project. This time is not just coding or design time, but any bathroom breaks or office chit-chat that occurs. If you do this, it will tell you more than just estimates and billing. It allows you, the programmer, to track your own performance" ... Mike Cellini