Scrum board model & E-Learning: How do you divide your Tasks/PBIs?
Feb 22, 2018
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.
Thanks!
4 Replies
Hi LJ, Great post (nothing to add sorry). I like the way you have frame the training development process, and can really see the value of trying to better explain what we do as part of the ICT development chain.
Thought I would follow in on your conversation.
Thanks Christine
We are also considering the move to an Agile development process. Wondering how this worked out for you. Any information you can pass along will be helpful.
Have you looked at this article: https://community.articulate.com/articles/an-introduction-to-sam-for-instructional-designers
Hi, LJ,
You can definitely divide "Develop module in Articulate" into smaller tasks. For example:
When a course will include audio and/or video elements, then add items for scripting, approving scripts, and recording, as per your process.
This discussion is closed. You can start a new discussion or contact Articulate Support.