Journey ontologies
Though "journey management" is already used by some practitioners, how it articulates with "project management", "programme management" is unclear in global "project management" published practices and "journey management"is still an object under research in the academic arena [1].
In common language, a journey is a "movement from end to end in a fixed course" (Fr : un mouvement d'un bout à l'autre selon un parcours fixé), a travel [2] (Fr : voyage)
Taking a management perspective, we prefer to define a journey as an "initiatory path"[3] (Fr : parcours initiatique) (CC-BY Licence 2.0 France Tru Dô-Khac)
Under this definition, we might revisit various ontologies [4] as journey ontology and identify an IT center transformation journey, a process journey [6], a sourcing journey [7],...
A set of IT function profiles (Fr : profil de la fonction SI) [5] as an IT center transformation journey
- 1. Utility ("Utilitaire"),
- 2. Technology ("Technologique"),
- 3. Service Center ("Centre de Service"),
- 4. Business Partner ("Partenaire des Métiers"),
- 5. Core Business ("Coeur de Métier").
A set of "Capability Levels" of a sourcing ontology [7] as a sourcing journey :
"Capability Level 1. Performing Sourcing",
"Capability Level 2. Consistently Managing Sourcing",
"Capability Level 3. Managing Organisational Sourcing Performance",
"Capability Level 4. Pro-actively Enhancing Value",
"Capability Level 5. Sustaining excellence".
A Service Integration Maturity Model [8] [9] as a IT architecture journey
- 1.Silo (data integration)
- 2.Integrated (application integration)
- 3.Componentized (functional integration)
- 4.Simple services (process integration)
- 5.Composite services (supply-chain integration)
- 6.Virtualized services ( virtual infrastructure)
- 7.Dynamically reconfigurable services (eco-system integration)
A SOA Maturity Model [10] as an IT engineering journey
- 1. "Cosmetic SOA" (revamping legacy IS)
- 2. "Overhaul SOA" (redevelopment without encapsulating business rules and master data)
- 3. "Extended SOA" (encapsulating business rules and master data)
Notes
- [1] Professor Dr David Dombkins, "Redefining our profession Part 2: The history and future of project management", PM World Today, February 2009, (Vol XI, issue II)
- [2] Chambers twentieth century dictionary, Chambers, 1972
- [3] Source : eSourcing Governance Thesaurus, Tru Dô-Khac, 2009-2010.
- [4] We define ontology , composed of the Greek words ontos (being) and logos (discourse), as a "discourse on being". Ex : an ontology on IT is a discourse on the nature of IT.
- [5] "L'information: prochain défi pour les entreprises - Pratiques de création de valeur par les SI et leur usage : cartographie 2009 ", CIGREF and Capgemini Consulting, Capgemini Consulting, 2009, page 14.
- [6] Cobit 4.1 Exerpt, IT Governance Institute, 1996-2007, page 26.
- [7]"The eSourcing Model for Client Organisations (eSCM-CL) v1.1, Model Overview", William E. Hefley, Ethel A. Loesche, ITSqc, Van Haren Publishing, 2010.
- [8] "The Open Group SOA Source Book", 2009. The model is called The Open Group Service Integration Maturity Model (OSIMM). Direct link provided as a courtesy from The Open Group. OSIMM was based on a model provided by IBM [9]
- [9] "Increase flexibility with the Service Integration Maturity Model (SIMM), Maturity, adoption, and transformation to SOA", Dr. Ali Arsanjani, Kerrie Holley, IBM, sept. 2005.
- [10] "Sustainable IT Architecture, The progressive way of overhauling information systems with SOA", Pierre Bonnet, Jean-Michel Detavernier, Dominique Vauquier and al., ISTE, John Wiley & Sons, 2009.
Authored by Tru Dô-Khac, Paris, France. Published on May 31. 2010, Paris in www.journey-ontologies.com. Copyright Tru Dô-Khac, Paris, 2010.
