First off, each person shouldn&#x27;t have &quot;their&quot; stories. The stories in the sprint backlog should be owned by and worked by the entire team. Second, not everything needs to be a story or a task in the backlog; agile isn&#x27;t about tracking every activity. Everybody will have things outside of planned stories (meetings, time off, whatever). If you feel the need to get detailed about it and plan at the hours level, assume a baseline &quot;development hours per day&quot; (6 is a common one) and adjust for planned time off. If your team is not able to get in the development hours you&#x27;re expecting, there&#x27;s something else wrong; such as a &quot;manager&quot; asking you to do TPS reports, outside the scope of the project your team is actually working on. Anyway, velocity at the point level is a better measure of a team&#x27;s ability to take on a certain amount of work in an upcoming sprint, because it inherently accounts for distractions. However you do it, don&#x27;t get too caught up on detailed accounting and planning of hours; that&#x27;s not how agile works. And definitely don&#x27;t create &quot;stories&quot; for things that aren&#x27;t actual user stories.