We’re going to move more quickly. The next competency area to comment on is project management. Please post answers to the following question:
What Project Management tasks do eLearning developers do?
Please post answers by Sunday, December 16th. We’ll start the next area on Monday, December 17. Everyone who posts three or more different responses gets a small prize!
Thanks, everyone! We have a great list for project management:
• Accurately estimate task time required
• Assure the quality of the work is up to standard and requirements that are agreed upon by the stakeholders
• Check in with project managers regarding the priority level of different projects
• Communicate in a friendly and helpful way
• Communicate project task progress and requirements
• Communicate to team members about the status of a project
• Contribute willingly, especially when projects take unexpected turns
• Control and monitor the project through change control requests, schedule and cost control, quality control, monitoring risks and resources.
• Coordinate project tasks (when required) based on strengths and familiarity in large project scenarios
• Create artifacts such as project charter, project management plan, work breakdown structure, requirements register, status reports, closeout reports.
• Document time spent working on projects, hold-ups/blocks encountered, workarounds used
• Ensure team members have all the information needed to continue/complete the project
• Execute the project by acquiring the needed resources (people and machines), manage the stakeholder engagement, manage communications, manage quality.
• Generate ideas collaboratively, especially as it relates to nascent projects
• Identify gaps in the workflow, both personal and institutional
Specify tasks, namely creating action items and potentially assigning those to other members
• Identify opportunities to re-use existing ideas or existing processes
• Identifying and negotiating project roadblocks
• Keep track of tasks that need to be completed
• Organizing tasks by priority
• Plan using processes such as scope definition, schedule management, determine budget, cost management, quality management, resource management, communications management, risk analysis, risk management, stakeholder engagement
• Prioritize tasks, and make effective decisions about task completion
• Provide direction on tasks and help during team transitions
• Record and communicate inter-dependencies when the project has several versions or parts
• Schedule tasks in a logical order for maximum efficiency
• Update team on progress and project deliverables
– Create artifacts such as project charter, project management plan, work breakdown structure, requirements register, status reports, closeout reports.
– Plan using processes such as scope definition, schedule management, determine budget, cost management, quality management, resource management, communications management, risk analysis, risk management, stakeholder engagement.
– Execute the project by acquiring the needed resources (people and machines), manage the stakeholder engagement, manage communications, manage quality.
– Control and monitor the project through change control requests, schedule and cost control, quality control, monitoring risks and resources.
Thanks, ld! Your prize is on its way!
– prioritize tasks, and make effective decisions about task completion
– identify gaps in the workflow, both personal and institutional
– task specification, namely creating action items and potentially assigning those to other members
– collaborative idea generation, especially as it relates to nascent projects
– identify opportunities to re-use existing ideas or existing processes
– keep everyone updated on progress and project deliverables
– be a friendly and helpful communicator
– be a willing contributor especially when projects take unexpected turns
Awesome! Prize is on its way.
-provide direction on tasks
(if someone is taking over a task, jumping in to help)
– identifying and negotiating project roadblocks
– communicating project task progress and task requirements
(when issues arise or something is identified, communicating how it will affect the team’s tasks. Example: Global edit arises in large task – where and how)
– Records / communicates inter-dependencies when the project has several versions or parts (with IDs or team)
– coordinate project tasks (when required) based on strengths and familiarity in large project scenarios
Thanks! Your prize is on its way!
Organizing tasks by priority
Ensuring they have all the information needed to continue/complete the project
Documenting:
– Time spent working on projects
– Hold-ups/blocks encountered
– Workarounds used
Thanks! Prize is on its way!
Check in with project managers regarding the priority level of different projects.
Keep track of tasks that need to be completed.
Schedule tasks in a logical order for maximum efficiency.
Thanks! Prize is on its way!
Managing Quality – While producing a product, its paramount to assure the quality of the work is up to standards and qualities that are agreed upon by the stakeholders. There’s nothing worse than having a client see mistakes in the eLearning they pay for; it shows them we don’t care about the work we do — which simply cannot be true.
Managing Communication – Communicating to team members about either the status of a project or if they’re unsure about how to proceed is essential for the success of a project.
Manage Time – You know the saying “time is money,” it’s absolutely correct, the less time spent on a project while maintaining quality is ideal. Knowing how long a task will take early on is helpful for all those involved.
I don’t believe the other knowledge areas are as important to eLearning developers (however they are important for the overall project).
Thanks! Prize is on its way. But how would you express these ideas in terms of a (relatively) simple statement in the form “Verb – object”. I’m paraphrasing your second comment as “Update team members regularly on project status.” Of course, that may not be what you meant. Could you distill your comments into that format, please?
“Update team members regularly on project status” works. It’s more like: — – Update the project status so team members are aware. or
– Before beginning to work on a project, make sure you are up to date with the status of the project by either talking to the Project Manager or reading the notes. Or,
– if the status of a project changes while you’re working on it, update the project notes and communicate it to the PM.
I don’t know if this is right…