It looks like you folks really know the drill in developing supporting tasks for each competency. I’ve chosen the next one: Problem Solving. Just as you did with QA, please list, please post your answers here to the question:
What Problem Solving tasks do eLearning developers do?
QA was such a great start. Can we continue with everyone adding two or more tasks that developers do that can be categorized as ‘problem solving’? Remember that the form of the task should be verb-object, e.g., Create ways to display large quantities of text without increasing the learners’ cognitive load. (That’s obviously one I thought up and everyone may disregard it completely.)
It’s still brainstorming, so come one, come all!
This is super work, everyone. I’ve collated your comments and revised them a tiny bit. Here’s the current list of Problem Solving Tasks that eLearning Developers do:
• Ask for help if needed
• Choose creative elements or novel features that are useful for both client and ID
• Collaborate with IDs to formulate easy-to-use interactive elements
• Communicate with vendors and convey fixes in a clear fashion
• Determine what other developers have done in order to make an interaction function (in order to replicate it or fix it, if it breaks)
• Document fixes implemented in-case the issue comes up in the future
• Experiment with novel ways to implement features.
• Fix Storyline when it breaks
• Identify technology restrictions for current design ideas
• Identify ways of making non-accessible interactions more accessible
• Identifying limitations in technology, budget, or both
• Investigate and solve browser-related issues with SCORM packages.
• Locate additional needed resources for development, such as authors, IDs, or media artists
• Manage and lead clients who are unfamiliar with eLearning development processes
• Manage budget and timeline issues
• Optimize authoring techniques that can shorten the amount of time spent on a task
• Organize the workload of their teams, when there are more projects than people to do the work
• Plan a development timeline under tight client deadlines strategically
• Think about the needs of the client versus the complexity of the design
• Troubleshoot non-functional web objects or buttons
• Use the internet efficiently to aid in troubleshooting courses
This list closes today, so if there’s anything to add, please post your response!
Identify ways of making non-accessible interactions more accessible.
When Storyline breaks, figure out why it happened and how to fix it.
Determine what other developers have done in order to make an interaction function (in order to replicate it or fix it, if it breaks).
Identifying limitations in technology, budget, or both.
Troubleshooting non-functional web objects or buttons.
Asking for help if needed.
Identify technology restrictions for current design ideas
Think about the needs of the client versus the complexity of the design
Manage budget and timeline issues
Make their work interesting by choosing creative elements or novel features that are useful for both client and ID
Optimize authoring techniques that can shorten the amount of time spent on a task.
Collaborate with IDs to formulate easy-to-use interactive elements.
Communicate with vendors and convey fixes in a clear fashion.
Efficiently utilize the internet to aid in troubleshooting courses.
Experiment with novel ways to implement features.
Document fixes implemented in-case the issue comes up in the future.
Investigate and solve browser-related issues with SCORM packages.
Strategically plan a development timeline under tight client deadlines.
Locate additional needed resources for development, such as authors, IDs or media artists.
Manage and lead clients who are unfamiliar with eLearning development processes.
Organize the workload of their teams, when there are more projects than people to do the work.