Jan
17
2011
17

Knowledge Management and Dublin Core

1. Introduction

The application of Dublin Core (DC) metadata for information management purposes has been taking place ever since the 15 simple DC elements were developed. Its application for industry specific purposes such as education or government service identification has also been widely adopted, though not without challenges along the way.

Knowledge Management (KM) presents an interesting set of challenges for those interested in utilising DC metadata because it can be perceived as a number of different things – as an academic discourse, an organisational intervention, a set of activities that a community of practice might undertake to ensure optimum knowledge flows, or even what an individual might do to maximize the reuse and retrievability of their own knowledge. To underscore this challenge, it is a very interesting exercise just to find a broadly accepted definition of KM that might be both flexible and comprehensive enough to deal with all these scenarios.

Although KM first emerged in the 1980s it only began to seriously establish in the mid 1990s when the impact of the Web was just beginning to be felt upon the business world. As such, its early character was biased toward business process improvement from a managerial perspective.

The influence of networks upon the way KM has been understood or implemented is something that has only emerged in later discourse (Beerli, et al., 2003; Back, et al., 2006). It has been argued that the fundamental KM problem is all about changing organizational ‘silos’ of activity (manifest in organizational divisions, hierarchical management structures, projects, work teams, documents, and individual workspaces) so that knowledge flows more readily, is shared and leveraged for maximum benefit, and is not pigeonholed nor rendered inaccessible through poor information management practices (Xu and Quaddus, 2005: 382).

Such a problem will likely resonate for most people who are employed by organizations. However, while this ‘silo’ problem is clearly evident within hierarchically structured organizations it is also manifest within networks, and it is commonplace for potentially synergistic communities of practice to actually exist more as disconnected ‘islands’. The problem is in fact a deeper one, and is to do with the nature of knowledge and organization—hierarchies and networks are the two most effective forms of organisation that human beings have yet created; both have their place, but it will always be the situational context that will suggest the most effective way to act.

Another challenge concerning KM for the DCMI community is that it represents a domain that is arguably more expansive than all other communities currently developing application profiles. Thus, a definition of Knowledge Management that might be useful for the DCMI KM community to consider is presented here:

Knowledge Management (KM) finds expression as both an organisational intervention aimed at delivering better efficiencies in the handling of knowledge, and an academic discourse that develops theoretical frameworks and practical techniques for managing the entire knowledge lifecycle from a variety of perspectives: individual, community, and organisational. It can, though doesn’t need to, involve a multiplicity of considerations and tasks and is always influenced by context.

1.1. DCMI KM Community

The DCMI Knowledge Management Community was established in mid 2007 as “a forum for individuals and organisations with an interest in the application and use of the Dublin Core standard in knowledge management.” (DCMI, 2007) To some extent this new community provides continuity with issues addressed by the DCMI Global Corporate Circle, which was deactivated in 2007. To date, while there is clearly an interest in this area with over 120 subscribers to the email listserv there is little serious documented discourse. This paper therefore aims to make a contribution by presenting some theoretical framework for consideration, providing examples of how DC metadata is being effectively applied in some Knowledge Management (KM) contexts, and pointing to current limitations of DC in such contexts.

1.2. Overview

The following discussion deals with topics on modelling and organising knowledge from a theoretical perspective. A number of scenarios are then presented, indicating how DC metadata has been effectively utilised for KM purposes. A sense-making abstraction is presented as a reference model for identifying prominent facets or pathways of knowledge that will typically need to be considered in KM contexts. This model aims to validate current applications while also pointing to potential novel applications, thereby indicating any limitations with currently available schemas that may need to be overcome.

2. Representing, Modelling, and Managing Knowledge

For knowledge to be organised and managed it is necessary to first establish the scope of such an undertaking. This task has been approached by various practitioners and communities of practice in a broad variety of ways. The proceeding discussion is an attempt to summarise some of the more prominent approaches that have relevance for the application of DC metadata.

The field of Computer Science provides at least two key (mutually informing) approaches – through formal knowledge representation languages such as Prolog, the Resource Description Framework (RDF), the Web Ontology Language (OWL), and Attempto Controlled English (ACE); or, through conceptual classification into three categories: declarative, procedural, and conditional knowledge. Declarative knowledge is expressed by explicit statements of the kind ‘it is known that’ and typically involves facts or ‘objective’ information; procedural knowledge is typically expressed by statements that represent ‘know-how’; and, conditional knowledge is represented by statements that represent ‘knowing-if’ and/or ‘knowing-why’ (Murphy, 2008).

Through recent years of work on developing a robust ‘abstract model’ that can inform future extensibility and application of DC metadata, the Dublin Core Metadata Initiative is now strongly aligned with the knowledge representation capabilities of RDF (Powell, et al., 2007). It is noteworthy that this work has taken both considerable effort and time and has required ongoing explication through other documents such as the Singapore Framework (Nilsson, et al., 2008). This work has also demonstrated that the goal of defining and using shared semantics is not sufficient for sustainable knowledge sharing in Web environments—for this to occur, semantics must be associated with statements that make clear certain relationships, thereby establishing context through syntax and structural relations. Another approach is to situate knowledge within its relationship to data, information, and wisdom as a value hierarchy and is often depicted as a pyramid .

However, just as the Internet has rendered geographical boundaries and legal jurisdictions as debatable constructs when it comes to information flows, the boundaries that separate data, information, and knowledge can be very fuzzy and depend upon context. Thus, in the context of the Internet, Figure 1 becomes a very poor representation for the simple reason that data, information, and knowledge become intermeshed. In this environment value can be created through rendering information and knowledge as data and many datasets can either comprise or be extracted from a knowledge-base. In short, this inverts the value-chain depicted by the pyramid (Mason, et al., 2003). Capturing explicit knowledge and organising it as structured information for sharing and reuse is thus one of the powerful features and potentials of the Web. This same recursive property can also be seen with metadata. While it is pragmatic that simple models identify ‘digital assets’ or content as one entity and ‘metadata’ as another (that describes the content) such models can mask deeper complexity. For example, in the case of a repository designed to broker resource discovery, the assets it gathers into a collection might only be metadata records but collectively they represent useful content – thus, ‘one person’s metadata may be another’s content’; ultimately, it is the context that determines this (Mason, 2004).

But there is another reason why Figure 1 is not adequate for the Internet and that has to do with the important role that metadata has in the organisation, structuring, presentation, and sharing of content and services—metadata being defined as data associated with or descriptive of other data, information, knowledge, or services. As such, metadata can be expressed in many forms— examples include the manifest file associated with a ‘learning object’, XML tags, user-defined tags, or explicit information such as authorship or publication date of a piece of content. A more accurate representation would therefore be something like what is depicted in Figure 2.

Yet another approach, from the field of Knowledge Management, was inspired by Polanyi (1966), who distinguished between explicit and tacit knowledge. Nonaka and Takeuchi (1995) developed this concept further and proposed a dynamic model that represents the management of (organisational) knowledge as interactions of tacit and explicit knowledge throughout four on going processes involving socialization, externalization, combination, and internalization known as the “SECI model”. As both an academic discipline and an organisational intervention the field of KM has developed considerably in the past decade and is replete with many more detailed models that both draw upon and challenge this foundational work (Snowden, 2002; Earl, 2001; Firestone and McElroy, 2002; Rao, 2005; Wierzbicki, 2006). Thus, while the core concepts of the SECI model continue to be recognised as important by KM practitioners the world over, there is an underlying shift in paradigm from a principle of reduction toward a principle of emergence that is important to highlight (Wierzbicki, 2006:1-13). The work by Snowden (2002, 2005) on complexity, story-telling, and sense-making is representative of this shift. Likewise, Seufert, Back, and von Krogh underscore the importance of networks for KM to develop:

Concerning the integration of networking and knowledge management, we believe two aspects to be crucial. First, knowledge management should comprise a holistic view of knowledge, meaning the integration of explicit and tacit knowledge. Furthermore, knowledge management should take a holistic view on where and how knowledge is being created and transferred … The integration of networking into knowledge management yields great benefits. The openness and richness of networks … foster a fertile environment for the creation of entirely new knowledge.

The influence of networks and networking upon KM suggests then that there is scope for developing updated models of knowledge. This is particularly so, given that hierarchies have historically been the dominant mode of organisational structure; however, while harnessing the flows of knowledge shared within networks would appear to be a natural domain for KM the theory and practice of doing so is not so straightforward. This is borne out in a blog post by Sims (2008) in which an analysis of 53 Knowledge Management definitions is presented:

General observation: this again illustrates the definition diversity. It is not like these are 53 definitions with slightly different word choice. These are substantially different. There are only five attributes that are seen in 30% or more of the definitions: KM is a process, it is targeted at the organization (company), it deals with knowledge, sharing is part of the story, and the definition includes a “why”. (Sims, 2008) Thus, it can be seen that the discourse on KM has developed considerably in the past 15 years. In an attempt at summing up the dimensions of ‘emergence’ and ‘complexity’ while not trivializing them Snowden advocates a characterization of the “paradoxical” nature of knowledge “as both a thing and a flow” (Snowden, 2002). As such, an adequate model of knowledge needs to convey dynamism and the tasks associated with organising knowledge involve far more than the description and classification of information resources—it involves both the tacit and explicit dimensions of knowledge. Obviously, metadata can only successfully be applied to explicit knowledge—so, is there another approach that can approximate a holistic view of managing knowledge? Could such a model point to new applications for metadata?

2.1. A Faceted Model

While all the preceding approaches can be shown to be useful a faceted model is presented as a means of identifying the critical pathways of knowledge in KM contexts (see Figure 3). This model is based upon earlier work in Norris, et al., (2003) and further refined in Mason (2007). This model represents an attempt to summarise the key pathways for consideration while an individual is engaged in learning, thinking, or knowing. It has been developed as a device that might assist in providing a ‘shorthand’ reference of considerations when approaching the development of an e-learning activity or a KM task. The model represents ‘primitive’ questions associated with query generation or proposition development (Who, What, When, Where, How, Why, and If). These seven knowledge facets are situated within three key influences: content, community, and context following Seely Brown (1999. p. ix).

Out of these seven primitives Who, What, When, and Where can be seen to function primarily as the primitives of organised information retrieval and resource discovery – particularly within the Internet. This can easily be validated by investigating the essential characteristics of metadata schemas used to describe information resources such as proposed by the DCMI Kernel Community (Kunze, 2001; Mason and Galatis, 2007). It is not yet clear to what extent the Why, How, and If primitives function as catalysts in the development of understanding but they can be seen as important questions in many activities that involve the creation, sharing, and management of knowledge. Of the latter three primitives, How and If can be seen to typically generate procedural or rule-based knowledge. Why, however, presents a significant challenge to deeper modelling, primarily because of its breadth of usage. Unlike the descriptive primitives (Who, What, When, Where, and to some extent, How), Why gives emphasis to the explanative dimension in which facts can be subject to greater subjective perspective. In teaching contexts Why is used as a question to help learners adopt a critical, reflective approach to the content they must interact with. In KM contexts, understanding why a certain communication protocol is important or why certain procedures need to be followed can make all the difference to how these things are operationalised. Knowing-why can also help build “strategic insight” (USDA FS, 2005:6).

There are a number of assumptions that underpin this model, not least of which is the choice of utilising a circular graphic—the assumption being that the relationships between all entities within it are closely interdependent. It is therefore instructive to consider recent literature focused on identifying transitions in knowledge creation that most models are presented as spirals (Wierzbicki and Nakamori, 2006). It is therefore acknowledged that this model could be improved and may need to be tested rigorously and modified.

3. Organising Information

Information can be organised in a multiplicity of ways—in library and enterprise settings the default method is through the application of hierarchical structure, based upon authoritative classifications and taxonomies (such as the Library of Congress Subject Headings or Dewey Decimal Codes); in Web environments, the power of association through hyperlinks is exploited; and, in a seemingly chaotic pile of papers on an office desk. In each case, structure and relation combine as the key organising principles. Focusing on semantics, as the DCMI community and Semantic Web community have done since first being established, also represents a powerful way to organise and discover information.

The simple (but extensible) semantics of the Dublin Core represent an elegant simplification of traditional library cataloguing semantics for use in Web environments. Following this achievement, it is arguable that the even simpler semantics proposed by the DCMI Kernel Community represent an important future key to innovative approaches to metadata interoperability (Kunze, 2001). The application of DC metadata to describe and enrich information resources has proven to be an effective method of managing information for later retrieval and reuse. In fact, metadata can be seen as a key component in managing information resources, But the question arises: to what extent can it be used in organising knowledge?

4. Organising Knowledge

For as long as knowledge has been preserved it has also been organized—whether in the context of non-literate societies such as Indigenous Australians stewarding knowledge through story and song; in the context of the I Ching, the first Chinese book ever written and focused on 64 core life scenarios to navigate; or, in the classification of newly identified plant species according to authoritative taxonomies.

Hypertext Markup Language (HTML) can be seen as a key contemporary technology that enables knowledge to be organised through rich associative links. Through combining hypertext with Internet transmission protocols HTML has enabled the Web to become a vast networking platform for connecting information and communication resources. While human societies have always benefited from networking, the scale and reach of networks now available is fundamentally a new development in human history and in the organisation of its disparate knowledge sources. Of course, most of the developed world now takes all this for granted. With recent developments in Semantic Web technologies and Web 2.0 applications there now exists further capacity for organising and sharing knowledge; however, the flipside of this story is that innovation is so extensive there is also a chaotic dimension to the proliferation of knowledge and networks. As soon as a new way of organising or combining knowledge becomes available new ‘islands’ or ‘silos’ of activity emerge and ‘networks’ soon become ‘clubs’ or ‘tribes’ that rely on conventions and protocols to participate.

‘Emergence’ is a concept that describes a scientific paradigm for our times in more meaningful ways than a scientific reductionist paradigm does (Wierzbicki and Nakamori, 2006)—but dealing with the pragmatics of this can be challenging to say the least! It is therefore arguable that in the same way that Jean-Paul Sartre made the famous comment that “man is condemned to be free” that no matter what knowledge we create we are condemned to make new sense of it in new contexts (Sartre, 1966). Just because knowledge may reside within an ‘open architecture’ platform doesn’t render it as operational, and it certainly doesn’t guarantee that it will flow. Because of the many methods of assigning order to otherwise unstructured information the Knowledge Organization System (KOS) is used to describe such methods. Examples include classification schemes, thesauri, taxonomies, controlled vocabularies, and subject headings. This term has been used as the basis for a relatively new Web technology, known as the Simple Knowledge Organization System (SKOS), which is aimed at providing a common data model for

the exchange of data between the kind of KOS referred to above (Miles and Bechhofer, 2008).

All these developments in technologies underscore that the application of metadata in any KM context represents just one component of a broader concern. In other words, metadata alone does not provide a complete solution for KM. Moreover, despite the use of the word ‘knowledge’ in technologies such as SKOS, it is important not to lose sight of the fact that such systems only represent a subset of knowledge. Furthermore, as Ray argues, Data models are insufficient to enable widespread system interoperability, and organizations need to develop an ontology to explain how different data elements interact. Only when this context is rendered in a computational form can external systems make sense of a data model. (Ray, 2009 quoted by Jackson, 2009).

4.1. Other Requirements

Because Knowledge Management is concerned with maximizing the potential application for both tacit and explicit knowledge, certain practical limits govern the application of DC metadata. In some KM contexts the ‘reusability’ of information or knowledge may be limited to basic metadata; however, in some corporate settings other metrics will apply. For example, the ‘trustworthiness’ or ‘reliability’ of the content or its source may depend on local or tacit knowledge about its origins; quality assessment will have industry-specific conventions; the ability to integrate diverse vocabularies in supporting IT infrastructure; the degree to which performance-support can be provided; how to prepare knowledge for transfer to contexts as yet not identified; what business analytics can be discerned; and, then there are security and privacy concerns. All these are issues for KM.

Many KM practitioners also place emphasis upon story as a means to communicate important lessons from the field. In terms of the model discussed in Figure 3, aspects of story align well with the facet know-why. The challenge becomes: how to use a DC approach in developing an appropriate schema to capture this?

5. Practical Perspectives

The following cameos are presented to indicate the diversity of implementation contexts in which Dublin Core metadata is currently used for KM purposes.

5.1. Ohio State University Knowledge Bank

The Ohio State University Knowledge Bank (OSUKB) represents an exemplar in University institutional repositories in the way it integrates diverse digital assets, is well-positioned to interoperate (or federate) with other ‘open access’ repositories, and the project “places its institutional repository in the larger context of a multifaceted knowledge management program” (Branin, 2004). The OSUKB also represents an example of the evolutionary path that academic libraries have navigated in recent years from “collection development to collection management to knowledge management” (Branin et al., 2007). Apart from the value of knowledge sharing with peers, the core value proposition presented to students in order to enlist their participation in using the Knowledge Bank is as a safe, high quality, managed repository in which to store and preserve outputs of their work for later use and or discoverability by others (OSU, 2009). This is clearly an important component of an individual student’s KM requirements. It also serves the purposes of the institution in that it represents an aggregation of intellectual outputs that will expand over time.

The OSUKB is an implementation of DSpace software and its Metadata Application Profile is based upon qualified Dublin Core (OSU, 2008). Specific additional requirements, such as managing Intellectual Property Rights, are handled via Creative Commons licensing. The OSUKB approach to KM represents a typical repository approach found throughout higher education settings worldwide. As such, the KM infrastructure that is implemented places emphasis on the management of scholarly outputs or content as the primary object for knowledge management. Despite acknowledging the broader KM agenda beyond the storage and retrieval of content to involve the “social life of information,” it is clear that there is a long way to go for other aspects of KM to be implemented as services that enhance the OSUKB—if Figure 3 is considered.

5.2. The Corporate Sector

While there is plenty of evidence that the corporate sector uses metadata to manage its assets, there still seems to be selective adoption of DC metadata. In fact, a recent book published with the title ‘Business Metadata’ (Inmon, et al., 2008), does not even contain one passing reference to DC metadata! This underscores the findings in a 2005 report developed for the DCMI Corporate Circle:

Except where there is a business or regulatory requirement to share information, the private sector has little interest in interoperability with repositories outside their organisation. Most applications that seek to gather metadata into databases so that document-like content can be found and re-used when needed, occur behind the firewall.

… [while there is] wide usage of Dublin Core in this context … there is an unwillingness and inability to share the details of that experience widely. (Busch, et al., 2005) This suggests that while some metadata infrastructure is being put in place to accommodate internal organisational information management requirements there is a long way to go before a holistic approach to KM metadata requirements in the corporate sector is achieved.

5.3. Semantic Web

With the development of the DCMI Abstract Model there is now exists better theoretical alignment with capabilities of RDF and hence the Semantic Web. The implications for KM of this are neatly summed up by Lamont (2007):

The Semantic Web is relevant to knowledge management because it has the potential to dramatically accelerate the speed with which information can be synthesized, by automating its aggregation and analysis. Information on the Web now is typically presented in HTML format, and while very beneficial in some respects, the format offers neither structure nor metadata that is useful for effective management. Cho (2009) echoes this view by arguing the role that Dublin Core has played in “knowledge management activity representation” is a key factor to future success of the Semantic Web. However, identifying significant Semantic Web implementations in KM contexts has not as yet been fruitful.

source : www.dublincore.org/groups/km/

Hal yang dapat di pelajari dari kasus diatas adalah bahwa penerapan knowledge management dalam dublin core metadata dapat memperbaiki proses bisnis dan perspektif manajerial dalam perusahaan diatas . selain itu , Knowledge Management (KM) juga menyajikan serangkaian tantangan yang menarik bagi mereka yang tertarik dalam memanfaatkan metadata DC karena dapat dianggap sebagai beberapa hal yang berbeda – sebagai wacana akademik, intervensi organisasi, satu set aktivitas bahwa komunitas praktek mungkin melakukan untuk memastikan arus pengetahuan yang optimal, atau bahkan apa yang individu mungkin lakukan untuk memaksimalkan penggunaan kembali dan retrievability pengetahuan mereka sendiri. serta  KM dapat domain yang memiliki lingkup yang lebih luas dari masyarakat lain yang sedang mengembangkan profil aplikasi untuk metadata DC dalam rangka mengakomodasi metadata eksplanatif.

Written by erich fernando usman in: 5 Case KM |
Jan
14
2011
20

Career Path For Programmer

I recently interviewed for a Business Analyst position with the CIO of a large multi-national software development firm. This man was in charge of the company’s worldwide IT operations, including offshore development projects, for which he was searching for qualified Business Analysts. The interview quickly became a casual conversation about current trends within the IT service sector, how the company was planning to take advantage of those trends, and, most importantly, how I could fit into those plans. It was during his evaluation of my skills that I asked how I fit and whether it was technical or business skills that were most valuable to his projects. The CIO summed up his advice about my career path with one small sentence: “Stay on the business side.”

Business skills, in this CIO’s view, were most important to his future projects and the industry as a whole. His reasoning was that he could train anyone in the technical skills he needed for a project, but finding those people with the necessary business skills to guide an IT project to success was something that could not easily be obtained. He went on to say that he found it difficult to find people who could communicate on even the most basic of levels. I asked if my background as a developer would help in getting a business analyst job, and he conceded that although it’s not a requirement, it certainly would help matters as long as I could prove that I wasn’t “too technical.”

His comments are consistent with the trend that all US-based programmers have observed since the late 1990’s: global salary competition amongst programmers, and a growing view in big business of programming as a commodity skill. It’s hard to compete with a developer in Russia or India who can work for a fraction of what I make minus benefits. The CIO managed to reaffirm the subtle, but major, shift from technical skills to business-technical skills in today’s labor market. I gave weight to his viewpoint since the people in his position are the trendsetters of the technology industry. They are the ones who set the directives for a company’s IT needs, and often, the requirements desired for the higher-paying positions.

I did a little research and found that the US Bureau of Labor Statistics Occupational Outlook Handbook predicts that computer systems analysts are expected to be among the fastest growing occupations through 2012. The Handbook describes a systems analyst as someone who may plan and develop new computer systems or devise ways to apply existing systems’ resources to additional operations. It describes a computer programmer as someone who writes programs according to the specifications determined by systems analysts. (The book does not separately list business analyst as an occupation.)

According to the Handbook, in the US systems analysts held an astounding 487,000 positions in 2004 (up from 468,000 positions in 2002) compared with 455,000 jobs in 2004 for computer programmers (down from 499,000 in 2002). The Handbook also states that employment for computer programmers is “expected to grow much more slowly than that for other computer specialists.” And recent estimates by the Economic Policy Institute have put the number of jobs being offshored at approximately 330,000 to 500,000 jobs. About 100,000 of those were full-time computer programming jobs.

The key to maintaining a good employment outlook in IT, it seems, is to move out of programming and up into more business-oriented IT positions such as systems analyst, business analyst, project manager, or systems architect. However, a computer programmer can’t just decide to become a systems analyst or project manager overnight. The journey takes time and requires the right amount of experience and learning to be successful.

Making the Shift

So you’ve seen the statistics and watched as the jobs in your market slowly disappear. You want to move more to the “business side,” but you don’t quite know how to do it. As I’ll describe next, making the shift can be done on-the-job by gaining more responsibility, polishing up your problem-solving skills, and using creativity in your work.

I began my journey into systems analysis and design by accepting more responsibilities throughout the project I was on when things proved too overwhelming for my superiors. I gradually accepted more of the project management and business analysis responsibilities when the opportunity presented itself. For example, I would walk to Suzy in accounting and work out a new enhancement with her one-on-one rather than wait for my manager to do so. Over time, as my manager’s confidence in my abilities grew, these responsibilities became a part of my job. It wasn’t long before I became the Programmer Analyst, and ultimately the Project Manager, as new positions were created to fulfill demand for our work.

When the need arises, I recommend walking to the end user yourself and working with her one-on-one. Your manager will be relieved when he discovers that you are capable of communicating with his end-users, identifying their issues, and resolving those issues before they are brought up in the weekly manager’s meeting. Even the best IT managers need a subordinate who is visible to the users who they can trust to get the job done. If a manager is slowly factoring himself away from the day-to-day workings of the project, welcome it. The higher visibility that you are obtaining can be translated into higher value—and that can result in a promotion. Over time, your increased interactions with more business-oriented people will make you more sensitive to business concerns.

A good subordinate has to be open-minded and creative. When solving problems, one has to always believe that there is a way to accomplish something, even if it’s never been done before. Sometimes, just listening to the user will produce an idea. A lot of issues may come down to the business process that the system is attempting to replicate. I have had users actually solve a business problem for me just by listening to what they had to say!

Whether you’re open-minded and creative or not, you can still work towards more business-oriented positions. After all, business systems analysts and project managers are only a small subset of the many positions opening up each year to address the issues of complexity through simplicity. If you love programming, you don’t have to necessarily give it up.

Jobs To Pursue

Senior Technical Positions

Developers will often find that they may have to work side-by-side with the users to iron out difficult bugs. It can be difficult, if not impossible, to fix these problems when both parties can’t communicate effectively. There was always a time in most of my work situations when the developer had to talk with the users or other developers directly to fix difficult issues. This is the programmer’s chance to show management that he or she is someone who can communicate and utilize analysis methodologies—otherwise known as a “programmer analyst.” A programmer analyst is also usually someone who has some years of technical experience, and a certain depth of technical knowledge.

Programmers who seek advanced technical skills without too much end-user interaction may find themselves gravitating toward the design & architecture side of the business. Although these types of positions are still relatively technical, they often involve making key decisions to address how the new system will fit into the organization’s overall IT plans. In order to be successful, the architect needs to understand and control the elements associated with the utility, cost, and risk factors of the proposed solution.

System architects must make very educated decisions about how to decompose and isolate the different components that will be required, how to fit these components into the existing infrastructure, and in what order to implement each component. It can be a disaster to implement an online ordering system that isn’t compatible with the organization’s current accounting packages. The architect must identify these types of issues and present them to non-technical management in words they can understand.

Business and Systems Analysts

My job searches have suggested that business and systems analysts with a good programming background and a high-level of “business savvy” are becoming the next hot ticket. More and more organizations are finally hiring business analysts to explore, record, and recommend systems that fit the business—as opposed to the other way around.

The business analyst must often work with project managers, systems architects, and systems analysts, all of which are growing occupations that can make the difference between success and failure. In some cases the business analyst’s responsibilities are being combined with that of the systems analyst or the project manager under the guise of “business analyst” or “business systems analyst.” A quick search on Dice.com will reveal that many business analyst jobs have hidden deep within their job descriptions requirements to develop technical specifications or to guide and manage projects. My first business analyst job required both project management and systems analyst skills. These positions are sure to become more common as organizations struggle to reduce project failure and development time.

Project Management

According to the Bureau of Labor Statistics’ Occupational Handbook, employers prefer project managers who possess advanced technical skills that have been acquired through work experience. The project manager is often responsible for hiring the staff, setting the schedule, and keeping track of the progress through every phase of development. This person is also responsible for assigning the work, dealing with everyday problems affecting that work, and making sure each analyst or programmer is carrying his own weight. The project manager can best carry out this function if he truly understands the work he is managing.

The project manager must also be a “people person” as well as a “technical person” in order to succeed. This individual must work with technical and non-technical staff at every level of the organization in order to succeed in his goals. Additionally, the project manager has to manage his team effectively to produce the desired product on time.

Management

The ultimate assignment for many IT professionals looking to move up the IT food chain is to become the manager. The Occupational Handbook explains that “employment of computer and information systems managers is expected to grow faster than the average for all occupations through the year 2014.” These job opportunities are best suited for applicants with computer-related work experience and often require an advanced degree, such as an MBA. And of course, strong communication skills are a requirement for any management job in IT.

Skills To Develop

Okay, so you’ve heard all about what’s required and where IT is going, but how can you capitalize on this new information?

My interview with the CIO and my experience in the field have shown me that companies want IT professionals who can understand what their business is and how to apply technology to make it better. Being able to follow directions is important, but being able to take some initiative and make your own judgments without handholding is equally important. The solution is to differentiate yourself from the traditional developer.

We have already discussed two ways of building up your current skills—acquiring business knowledge and advanced technical knowledge—but two other areas are important as well: communication and leadership.

Whether that CIO I interviewed with believed that communication skills could be learned or not is irrelevant. Everyone can learn to be a better communicator with practice. The difference is that communication skills take much longer to develop. Communication takes the right mix of experience and training to become effective. I have worked on this since my college days and have had great success in my career as a result.

I learned to communicate more effectively by dealing with those who couldn’t. Many software users can’t understand the technical side enough to describe any of their requirements in any type of detail regardless of their background. On the other hand, many technical people don’t understand the intricacies of the business processes they are implementing because they can’t openly communicate with the users. Learning to communicate, and having the patience to gain knowledge from the user, is an essential skill that many of my former and current coworkers don’t have.

To add to your problem solving skills, instead of asking your superior or a more experienced programmer to help with a problem, take it upon yourself to find the answer to that complex problem. Before too long, you can be the one who others consult when there is a problem to fix or a new project to complete. Gaining problem-solving experience not only improves communication, it also improves your chances of moving into analyst and management positions. Eventually, you can do as I did and get your own project to manage.

The key to moving up the ladder at any company is to let them know what you know. Answer those questions, solve those problems, accept those new projects, and don’t be too shy to share a better solution. It could mean the difference between being “just another programmer” or being the top candidate for a promotion.

Source: http://www.developerdotstar.com/mag/article/programmer_career.html

Written by erich fernando usman in: Artikel KM |
Jan
12
2011
5

Knowledge Map

Knowledge Map adalah sebuah pengetahuan yang di susun sehingga membentuk suatu system yang strategis dan sistematis sehingga menjadi sebuah pengetahuan transparasi sehingga mudah untuk ditransfer atau disebarluaskan.

Dimana kita dapat membuatkan sebuah Knowledge Mapnya sehingga memperumudah perusahaan dalam menentukan mana karyawan sesuai dengan skill masing masing , sehingga dapat membuat sebuah tim yang solid baik dari segi bertanya maupun menjawab sebuah tantangan yang ada dalam perusahaan.

– Knowledege Map lainnya

System yang baru berbasis web database, KnowledgeMap, adalah membuat proses lebih mudah. Database termasuk dokumen yang dibuat dimana pembuatan Knowledege map berupa handout, slide PowerPoint dan web link untuk mempermudah untuk mencari informasi.

Pemetan knowledge map cocok dilakukan terhadap tipe knowledge activities, karena knowledge map dilakukan berdasarkan fungsi kerja.

Dimana dalam membuat knowledge map ada beberapa hal yang perlu diperhatikan diantaranya:

o Fokusnya harus ke area yang memang sangat membutuhkan knowledge secara intensif dimana fungsi kerja merupakan knowledge yang dibutuhkan secara intensif.

o Memetakah antara knowledge yang ada dengan para expert tersebut sesuai dengan bidang dan pemetaan pekerjaan di organisasinya.

o Sistem perlu menerapkan sistem index baik untuk asset (knowledgenya) maupun para pemiliknya (expert orangnya)

o disiapkan link disetiap area atau aplikasi dimana karyawan bekerja, sehingga kalau kesulitan bisa langsung terhubung dengan expert yang memang bisa membantu di organisasi.

o Diatur didalam data untuk knowledge map ini bisa terus terupdate secara desentralisasi sehingga tidak tergantung oleh pusat.

Written by erich fernando usman in: ilmu - ilmu |
Jan
12
2011
5

Materi mengenai Acquiring Knowledge

Acquiring knowledge adalah suatu pendekatan knowledge dengan cara menghadirkan pihak dari luar perusahaan untuk memberikan informasi atau sharing knowledge kepada perusahaan kita.

sebelumnya , terdapat beberapa kesulitan ketika kita menghadirkan para ahli dari luar , yaitu :

  1. Potensi investasi
  2. Potensi resiko
  3. Membuat pembayaran investasi

Tipe – tipe stakeholder acquiring knowledge :

  1. Shareholder Knowledge –> Orang yang mensharingkan informasi mengenai knowledge ke setiap perusahaan.
  2. Supplier Knowledge –> Orang yang bertugas sebagai pemasok untuk memenuhi setiap keperluan yang di perlukan oleh perusahaan.
  3. Customer Knowledge –> Orang atau pelanggan yang memberikan masukan kepada perusahaan untuk dapat meningkatkan kinerjanya dalam hal pelayanan pelanggan.
  4. Employee Knowledge –> Karyawan menghasilakn ide – ide inovatif demi kelangsungan perusahaan kita.
  5. Political Knowledge –> Orang yang memberikan informasi mengenai kinerja politik yang dapat mempengaruhi kinerja perusahaan kita.
  6. Opinion Leader Knowledge –> Menghadirkan para ahli atau konsultan dari luar untuk memberikan pembelajaran seputar knowledge kepada perusahaan kita.
  7. Public Knowledge –> Berusaha menjalin kerja sama dengan perusahaan luar untuk menunjang kinerja perusahaan kita.
  8. Knowledge Hold by Financial World –> Menghadirkan orang – orang yang ahli dalam bidang financial untuk memberikan masukan bagaimana meningkatkan peforma keuangan perusahaan kita.
Written by erich fernando usman in: ilmu - ilmu |
Jan
11
2011
6

Identifying Knowledge

Masalah – masalah dalam identifikasi knowledge :

  • Aset internal knowledge suatu perusahaan tidak kelihatan
  • Kebanjiran informasi yang berlebihan
  • bersifat memadai , tidak mutlak dan transparency
  • visibilitas struktur dan karyawan

ada 3 tahap dalam identifikasi knowledge :

  1. struktural knowledge –> Pendekatan melalui knowledge struktural dapat dilihat melalui knowledge yang telah dibentuk di suatu perusahaan baik dalam bentuk tatanan, rules  maupun standar dari setiap struktur perusahaan yang menjadi bagian dari perusahaan tersebut.
  2. Operasional Knowledge –> Suatu pendekatan melalui operasional knowledge dapat di lihat melalui fungsi – fungsi dari setiap orang dalam suatu perusahaan dalam menjalankan suatu proses bisnis.
  3. Behaviour Knowledge –> Suatu pendekatan melalui behaviour knowledge dapat di lihat melalui kebiasaan – kebiasaan para karyawan suatu perusahaan berdasarkan dari segi budaya untuk meningkatkan kinerja perusahaannya.
Written by erich fernando usman in: ilmu - ilmu |

Powered by WordPress. Theme: TheBuckmaker. Zinsen, Streaming Audio