MENINGKATKAN KINERJA PERUSAHAAN DENGAN MENERAPKAN KONSEP MANAJEMEN SUMBER DAYA MANUSIA STRATEGIK DALAM MENYONGSONG PERSAINGAN GLOBAL

The concept of Strategic Human Resource Management has been a very important topic since the late 1980s. A company, if it wants to succeed in the competition in this global era, must be able to make human resource management plans that are capable and responsive to changes in world business in the future (strategic). This research aims to explain the concept of strategic human resource management (MSDMS) in an effort to contribute to company performance. MSDS research using a qualitative approach by using a literature review in presenting theories about research problems that are currently being carried out. There are two things that are analyzed in the concept of strategic human resource management (MSDMS). First, the relationship between HR strategy, HR practice and organizational performance is reviewed. As a result, the best practice approach has been used and yields useful results comparatively to the contingency approach and the configurational approach. Second, intervening factors and the causal relationship between HRM practice and organizational performance are analyzed. Retention results and multiple factors are found and placing too much control on causal relationships is unrealistic in empirical studies

Proceso de requisitos adaptable a factores situacionales

La estrategia de ingeniería de requisitos orientada al cliente, que se ha desarrollado a lo largo de varios proyectos de investigación desde 1995, ha sido difundida a través de cursos de grado y posgrado, y puesta en práctica en varios proyectos de software en la industria. Aún cuando esta estrategia puede considerarse suficientemente madura, todavía requiere mejoras en algunos aspectos relevantes. Una de las mejoras posibles está relacionada con la adaptación del proceso de requisitos a las características del proyecto de software. Estas características se manifiestan en factores observables que atañen al contexto de aplicación y al proyecto mismo. En base a estos factores se pueden tomar decisiones referidas a qué artefactos de requisitos deben construirse, qué actividades del proceso de requisitos son necesarias realizar y qué técnicas específicas son más convenientes aplicar. Es decir, se propone adaptar el proceso de requisitos a cada proyecto de software específico, en base a los factores situacionales imperantes en él. En la práctica hemos encontrado que esta tarea de adaptación no se realiza, o sólo se lleva a cabo parcialmente en base a la experiencia del ingeniero de requisitos a cargo, sin una guía de parámetros a contemplar.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informática (RedUNCI

Proceso de requisitos adaptable a factores situacionales

La estrategia de ingeniería de requisitos orientada al cliente, que se ha desarrollado a lo largo de varios proyectos de investigación desde 1995, ha sido difundida a través de cursos de grado y posgrado, y puesta en práctica en varios proyectos de software en la industria. Aún cuando esta estrategia puede considerarse suficientemente madura, todavía requiere mejoras en algunos aspectos relevantes. Una de las mejoras posibles está relacionada con la adaptación del proceso de requisitos a las características del proyecto de software. Estas características se manifiestan en factores observables que atañen al contexto de aplicación y al proyecto mismo. En base a estos factores se pueden tomar decisiones referidas a qué artefactos de requisitos deben construirse, qué actividades del proceso de requisitos son necesarias realizar y qué técnicas específicas son más convenientes aplicar. Es decir, se propone adaptar el proceso de requisitos a cada proyecto de software específico, en base a los factores situacionales imperantes en él. En la práctica hemos encontrado que esta tarea de adaptación no se realiza, o sólo se lleva a cabo parcialmente en base a la experiencia del ingeniero de requisitos a cargo, sin una guía de parámetros a contemplar.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informática (RedUNCI

Proceso de requisitos adaptable a factores situacionales

La estrategia de ingeniería de requisitos orientada al cliente, que se ha desarrollado a lo largo de varios proyectos de investigación desde 1995, ha sido difundida a través de cursos de grado y posgrado, y puesta en práctica en varios proyectos de software en la industria. Aún cuando esta estrategia puede considerarse suficientemente madura, todavía requiere mejoras en algunos aspectos relevantes. Una de las mejoras posibles está relacionada con la adaptación del proceso de requisitos a las características del proyecto de software. Estas características se manifiestan en factores observables que atañen al contexto de aplicación y al proyecto mismo. En base a estos factores se pueden tomar decisiones referidas a qué artefactos de requisitos deben construirse, qué actividades del proceso de requisitos son necesarias realizar y qué técnicas específicas son más convenientes aplicar. Es decir, se propone adaptar el proceso de requisitos a cada proyecto de software específico, en base a los factores situacionales imperantes en él. En la práctica hemos encontrado que esta tarea de adaptación no se realiza, o sólo se lleva a cabo parcialmente en base a la experiencia del ingeniero de requisitos a cargo, sin una guía de parámetros a contemplar.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informática (RedUNCI

Evaluating IS/IT Projects: Revealing the Causes of Equivocality

Evaluating IS/IT projects and deciding on their continuation has been hampered by the problem of equivocality. Equivocal situations hinder decision-makers to clearly recognise potential problems and implications of these decisions, as well as to decide the course of action in a purposeful fashion. However, little attention has been devoted to examine the causes of such situations. Extant literature was analysed and synthesised to identify typical characteristics of equivocal situations and uncover the potential causes of equivocality. We developed a framework based on this review and used it further to assist the investigation and to corroborate the causes of equivocality through expert interviews. In this paper, we investigated the causes of equivocality in practice by eliciting insights from different perspectives of decision-makers and their perceptions toward equivocal situations. We found that equivocal situations prevailed are much strongly related to the Challenges in project management, the Complexity in process and the Sophistication of technology within the Content of evaluation. Intriguingly, we found less solid relations with the Lack of standards and the Failure of evaluation methods as these two factors did not emerge as dominant causes during our discussions with the experts

Evaluating IS/IT Projects: Revealing the Causes of Equivocality

Evaluating IS/IT projects and deciding on their continuation has been hampered by the problem of equivocality. Equivocal situations hinder decision-makers to clearly recognise potential problems and implications of these decisions, as well as to decide the course of action in a purposeful fashion. However, little attention has been devoted to examine the causes of such situations. Extant literature was analysed and synthesised to identify typical characteristics of equivocal situations and uncover the potential causes of equivocality. We developed a framework based on this review and used it further to assist the investigation and to corroborate the causes of equivocality through expert interviews. In this paper, we investigated the causes of equivocality in practice by eliciting insights from different perspectives of decision-makers and their perceptions toward equivocal situations. We found that equivocal situations prevailed are much strongly related to the Challenges in project management, the Complexity in process and the Sophistication of technology within the Content of evaluation. Intriguingly, we found less solid relations with the Lack of standards and the Failure of evaluation methods as these two factors did not emerge as dominant causes during our discussions with the experts

Moderating Effects of Requirements Uncertainty on Flexible Software Development Techniques

Partially due to increasing requirements uncertainty, flexibility has been in the focus of many software development activities for many years. Only few studies have analyzed the indirect effect that different levels of requirements uncertainty have on the effects of established flexible development techniques. This study analyzes how requirements uncertainty moderates the well studied effects of (1) sequential development, (2) investment in architectural design, and (3) intensity of early feedback on the performance of contract development projects. It finds that requirements uncertainty negatively moderates the effects of sequential development. It also points out that requirements uncertainty negatively moderates the effect of investment in architectural design. For agile development approaches, the value of investment in architectural design falls with increasing uncertainty. However, for plan-driven approaches, investment in architectural design is positive at any level of requirements uncertainty. Finally, the paper finds that early feedback throughout the development process is helpful at any level of requirements uncertainty

Coping with Requirements Uncertainty: An Interpretive Case Study

Information systems development projects (ISDPs) often face requirements uncertainty. Thus, coping with this issue is an important project management task in ISDPs. In order to gain insights into which different requirements uncertainty situations exist and how to cope with them, we conducted a longitudinal interpretive case study. We investigated the requirements analysis of an ISDP in an international insurance company for 17 months. Thereby, we identified eight distinct requirements uncertainty situation types, observed ten requirements engineering (RE) techniques applied in practice and their impact on requirements uncertainty situation types, and finally derived recommendations for applying RE techniques in requirements uncertainty situations based on our observations. We combine these findings and contribute to RE literature by making a first step towards a framework for coping with requirements uncertainty in ISDPs. We believe that RE researchers as well as practitioners in ISDPs can make use of this article’s insights