Skip to main content

Who was Bloom and why should I care?

Benjamin Bloom (1913 – 1999) was an American educational psychologist who developed a taxonomy, or structure, through which educational objectives could be organized according to their cognitive complexity. The cognitive domain deals with a person's ability to process information and use it in a meaningful way. Bloom identified six levels within the cognitive domain, from the simple recall of facts, through increasingly more complex and abstract levels of thinking.

Simply put, Bloom’s Taxonomy helps teachers categorize learning objectives and, from there, assess learning achievements.

Why should you care? Many popular certification exams – such as the ITIL V3 exams – are based on Bloom’s Taxonomy. Understanding the Bloom level at which you will be tested and using appropriate study techniques greatly increases your ability to

  • Engage effectively in class
  • Prepare properly for the exam
  • Achieve success on the exam

It is also useful to understand your learning style, or approach to learning. Learning styles include:

  • Visual – learn through seeing
  • Auditory – learn through listening
  • Kinesthetic – learn through moving, doing, touching

The ITIL V3 Foundation and Foundation Bridge exams (and most “foundation” or “essentials” exams) use Bloom levels 1 and 2

  • Bloom 1 – knowledge – measures recall of terminology and specific facts
  • Bloom 2 – comprehension – measures understanding of ideas and ability to translate or explain concepts

Effective learning and study techniques for learners taking Bloom levels 1 and 2 exams include:

  • Take notes/rewrite notes (visual/kinesthetic) - highlight important points in color
  • Reread course materials (visual/auditory/kinesthetic)
  • Complete available study aids (visual/auditory/kinesthetic)
  • Create and use Flash Cards (visual)
  • Record notes, read notes aloud, discuss terms and concepts aloud (auditory)
  • Create mnemonics to aid memorization (auditory)
  • Partner Quizzing (verbal)
  • Create simple mind maps and diagrams to tie terms and basic concepts to key topics (visual/kinesthetic)
  • Read a composed document such as the Introductory Overview of ITIL V3 that provides a “big picture” perspective www.itsmacademy.com/files/itSMF_ITILV3_Intro_Overview.pdf

The ITIL V3 Lifecycle, Capability and Managers Bridge exams use Bloom levels 3 and 4

  • Bloom 3 – application – measures ability to use information in new ways to solve problems, predict results, tell how, when, where and why
  • Bloom 4 – analysis – measures ability to distinguish between different parts, understand how parts fit together, identify causes, recognize hidden meanings, draw conclusions

Effective learning and study techniques for learners taking Bloom levels 3 and 4 exams include:

  • Actively participate in class discussions, debates and assignments
  • Use the SQ3R (Survey, Question, Read, Recite, Review) reading and study technique
  • Create complex mind maps to tie terms, concepts, and activities to key topics (Visual/Kinesthetic)
  • Practice mapping ITIL concepts to real world situations/problems
  • Create inductive diagrams - diagrams that illustrate inductive reasoning which involves moving from observations to a theory
  • Create deductive diagrams - diagrams that illustrate deductive reasoning which involves starting with a theory and confirming (or not) that theory

Despite its popularity, cramming doesn’t work when preparing to take an exam. Your mind needs time to assimilate new information. The best ways to ensure success on any exam are to (1) pay attention and participate in class, (2) take notes, and (3) use a variety of study techniques. The most effective techniques are those that reflect the Bloom level(s) of the exam you are taking and your personal learning style.

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…