Scrum board model & E-Learning: How do you divide your Tasks/PBIs?

Because we operate within a software company that already has the developers using Agile methodology, my training department is moving towards a more formalized Scrum board model, with Epics, Stories, Tasks, and PBIs (Product Backlog Items).

For example-

Epic: Employee Development
Story: Employee Onboarding Path
Task: Main Onboarding Module
PBIs: ??? (ie: research, storyboarding, developing, audio recording, etc)

I was wondering if anyone would be willing to share how they break down the PBI, aka sub-task, portion of this methodology? And if you've got something quite different from my example above, I'd love to hear that too!

The bigger picture elements are easier to identify, but I've been wrestling with how granular to go when things like "develop module in Articulate" can last days, and seem difficult to divide further.


1 Reply