HelpAboutBlogBOKKEDPodcastsTopicsWizardLinksBooks

Skep's Pick: The IT Skeptic Awards for 2008 This link is here because...(hover)

BOKKED™: The IT Skeptic's Body Of Knowledge Known Error Database



This database holds known errors in Body of Knowledge (BOK) publications such as ITIL®, COBIT, ISO20000... The purpose is to:

  • provide a public reference
  • allow public debate
  • feed back to the BOK owners

If your requirement is solely to notify OGC/TSO of an error in a book, you can use the official "Change Control System".

We do NOT track errors in websites, white papers and other ephemera; only published books and documents. Note that we take a fairly broad interpretation of 'error' to include such things as inconsistencies between BOK (eg ITIL differs from COBIT) because tracking these will be useful. Please do not make it any wider: the fact that you do not agree is not an error.

Use of this database is subject to the terms and conditions of the IT Skeptic website

BOKKED™ is provided by The IT Skeptic™ as a public service, at no cost to OGC, TSO, APMG, itSMF or any other organisation. (Well, somebody had to do it).

The IT Skeptic™ and BOKKED™ are neither associated with nor endorsed by OGC, TSO, APMG, itSMF or any other organisation.
We are not associated with or funded by any organisation other than Two Hills Ltd and our advertisers. This is an independant website.





You may comment on and rate BOKKEs. Please feel free to add new BOKKEs (You must be logged in first)

You can Google for BOKKEs: (Google index us approximately daily)


Google

or here you can search by publication...
ContributorRankingssort iconcmtsUpdatedstatus
Proactive problem management description does not exist in V3aroos
 
 
 
 
 
509/05/07
SD p79 ‘Catalogue’ replaced with ‘Level’skeptic
 
 
 
 
 
008/03/12
SS P58 Logical errorbrian_dayton
 
 
 
 
 
108/03/12
Large amount of PYIFE book rendered obsolete by AMPG syllabus changesskeptic
 
 
 
 
 
008/02/14
ST p223 CAB/EC to ECABvinodka
 
 
 
 
 
008/03/12
SO 4.2 Incident Management process never determines the serviceskeptic
 
 
 
 
 
209/08/12
PYIFE Page 157: 12.2 Question 4 wrongskeptic
 
 
 
 
 
008/02/14
ST p59 Renaming FSC to CS then referred to as SCmbuzina
 
 
 
 
 
108/03/12
PYIFE Page 89: 6.6 Question 4 wrongskeptic
 
 
 
 
 
008/02/14
CSI Model diagramAlison Adams
 
 
 
 
 
908/03/28
SO p58, p61 ‘unknown’ deletedskeptic
 
 
 
 
 
008/03/12
definition of incidentaroos
 
 
 
 
 
308/03/14
ITIL V3 Service Operation disconnect between Incident and Problem Managementskeptic
 
 
 
 
 
4409/12/28
SO regards KEDB as distinct from CMS, ST does notskeptic
 
 
 
 
 
307/06/22
Problem management process graph is wrongmbuzina
 
 
 
 
 
609/03/06
SD p31 PM and warrantyskeptic
 
 
 
 
 
008/09/13
Service Gap ModelPELIJN
 
 
 
 
 
207/06/23
Supplier strategy & policy undefined in ITIL V3 Service Strategymbuzina
 
 
 
 
 
009/05/07
Retired Services shown inside Service CatalogueRumagoso
 
 
 
 
 
407/12/20
paragraph 2.4.3 should be the value of the volume to the businessPELIJN
 
 
 
 
 
007/06/26
ST Figure 4.20 typo "assume" means "assure"skeptic
 
 
 
 
 
007/07/01
SD p291 Glossary: Brainstormingskeptic
 
 
 
 
 
008/03/12
SS p238 Glossary: Cost Modelskeptic
 
 
 
 
 
008/03/12
SD p214 ‘Service Transition Pack’ changed to ‘Service Design Pack’skeptic
 
 
 
 
 
008/03/12
Marginal costing definitionJamesFinister
 
 
 
 
 
007/06/26
ST p200 SCM or CMS?skeptic
 
 
 
 
 
008/03/12
PYIFE Page 90: 6.6 Question 3 wrongskeptic
 
 
 
 
 
008/02/14
SS p114 Figure 5.8skeptic
 
 
 
 
 
008/03/12
SD 4.6.4.3 five or six elements?skeptic
 
 
 
 
 
009/10/30
Figure 4.8 in Service Transition and Figure 4.6 in Service Operationpfranck
 
 
 
 
 
107/06/22
SD p101: MTBFHAZET
 
 
 
 
 
008/08/04
SO p35 Event definition pfranck
 
 
 
 
 
008/03/12
ST Service V-model figure 4.21 and 4.30 confusingskeptic
 
 
 
 
 
007/07/27
SD P33 Figure 3.6skeptic
 
 
 
 
 
008/03/12
SD p145 Figure 4.27skeptic
 
 
 
 
 
008/03/12
No ... Manager roles defined in glossaryskeptic
 
 
 
 
 
007/06/25
SS P86 Incorrect reference to Table 4.6brian_dayton
 
 
 
 
 
208/03/12
ST p69 Wrong hierarchy in the CMSavallesalas
 
 
 
 
 
009/03/13
SD p145 Figure 4.27 Security control - It is shown as 'Direction' - instead of 'Detection'vinodka
 
 
 
 
 
008/03/12
SS P201 Figure 9.5skeptic
 
 
 
 
 
008/03/12
12next ›last »