Alignment Chart – Donna Hryniewicki

Purpose of Alignment Charts in Instructional Design: An alignment chart is an instructional design tool that is used to illustrate how the selected activities align with learning objectives. The alignment chart includes both terminal and enabling objectives, along with their corresponding absorb, do, and connect activities as well as the method to assess learners’ mastery of the content.

Absorb Activities: In absorb activities learners read, listen, and watch. These activities may sound passive, but they can be an active component of learning. Types of absorb activities include: presentations, readings, stories, and field trips.¹

Do Activities: Do activities transform that information into knowledge and skills. In do activities, learners discover, parse, decode, analyze, verify, combine, organize, discuss, debate, evaluate, condense, refine, elaborate, and, most importantly, apply knowledge. Types of do activities include: practice activities, discovery activities, games, and simulations.²

Connect Activities: Connect activities integrate what we are learning with what we know. They do not so much add new knowledge and skills as tie together previously learned skills and knowledge. Types of connect activities include: ponder activities, questioning activities, stories by learners, job aids, research activities, and original work.³

Training Goal: The aim of this training is to identify common failure modes in the JourneyQube CICD pipeline and prepare documentation for new help desk employees so they can efficiently address the problem. This training will be entirely online with an optional in person review session.

Terminal Objective: With the aid of supplied documentation, helpdesk employee can verbally summarize the conditions that are most likely to cause each of the top five failure modes in the JourneyQube CICD pipeline.

Enabling Objectives	Assessment Idea	Absorb Activity	Do Activity	Connect Activity
Summarize the most likely set of conditions that cause failure mode one, and resolve those conditions.	Pick-multiple.	Reading – Learners will read a PowerPoint presentation addressing failure mode one.	Guided analysis – Learners will follow a provided audio file that walks them through what they need to look for when failure mode 1 has occurred.	Pick-multiple assessment.
Summarize the most likely set of conditions that cause failure mode two, and resolve those conditions.	Matching.	Presentation – Learners will listen to a screencast addressing failure mode two.	Guided analysis – Learners will follow a provided audio file that walks them through what they need to look for when failure mode 2 has occurred.	Matching assessment.
Summarize the most likely set of conditions that cause failure mode three, and resolve those conditions.	Pick-one.	Reading - Learners will read a PowerPoint presentation addressing failure mode three.	Drill and practice – Learners will be shown a series of screenshots that relate to failure mode 3 and they will be asked questions related to what they see. Pick-one assessment.
Summarize the most likely set of conditions that cause failure mode four, and resolve those conditions.	Pick-multiple.	Presentation - Learners will read a PowerPoint presentation addressing failure mode four.	Drill and practice – Learners will be shown a series of screenshots that relate to failure mode 4 and they will be asked questions related to what they see. Pick-multiple assessment.
Summarize the most likely set of conditions that cause failure mode five, and resolve those conditions.	Matching.	Reading - Learners will read a PowerPoint presentation addressing failure mode five.	Dig and Decide – Learners will be given a series of slides without prompts and they will need to write a short paragraph that explains how and why the situation presented to them is failure mode 5. Matching assessment.

Terminal Objective: Using the build log, helpdesk employee needs to be able to determine if a given failure matches one of the top five failure modes in the JourneyQube CICD pipeline.

Enabling Objectives	Assessment Idea	Absorb Activity	Do Activity	Connect Activity
Demonstrate how to access the build log	Performance (series of actions/clicks on computer).	Presentation – Software demonstration	Guided analysis – Learners will follow a provided audio file that walks them through what they need to do and access to get to in the build log.	Performance assessment (series of actions/clicks on computer).
Using the build log, be able to identify the error that caused a build to fail	Pick-one.	Video	Case Studies – Learners will review several different situations, and asked to identify which point on the build log caused the build to fail (options A, B, C, and D will be given). Learners will get feedback after each answer and if they do not get a question correct, they need to try again, until the answer they submit is right. Pick-one assessment.
Using build log and supplied documentation, determine if the error that caused the failure is one of the top five failure modes in the JourneyQube CICD pipeline	True/False, Pick-one.	Video		True/False, pick-one assessment.

Terminal Objective: Helpdesk employee needs to identify and execute next steps based on the identified failure.

Enabling Objectives	Assessment Idea	Absorb Activity	Do Activity	Connect Activity
Demonstrate how to escalate the failure if it does not match any of the top five failure modes	Fill-in-the-blank.	Reading	Drill and practice – Learner will be given several situations and needs to determine next steps. Fill-in-the-blank assessment.
If the failure is one of the top five failure modes, using supplied documentation, execute the resolution procedure	Performance (series of actions/clicks on computer).	Presentation	Hands-on-activity – Learners will be presented with real failures and asked to identify if it is one of the top five failure modes. Learners will get feedback after each answer and if they do not get a question correct, they need to try again, until the answer they submit is right. Performance assessment (series of actions/clicks on computer).