Results 1 -
7 of
7
Reinforcing Systems Analysis and Design Process Learning
"... Reinforcing the value of using a consistent systems development process and developing key models in the design and development of an Information System—in this case a database—are key to a students ’ understanding of any systems development project. In this paper, the use of a case study is describ ..."
Abstract
-
Cited by 1 (1 self)
- Add to MetaCart
(Show Context)
Reinforcing the value of using a consistent systems development process and developing key models in the design and development of an Information System—in this case a database—are key to a students ’ understanding of any systems development project. In this paper, the use of a case study is described involving a small consulting firm (Mallach, 2006) within an IS 2010.6 Systems Analysis & Design course. The case study points out what can go wrong when a “haphazard ” development process, especially one without planning, is utilized to develop a database system. The evolution of the writing assignments associated with case study are also highlighted.
Assessing team performance from a socio-technical congruence perspective
- in ICSSP, 2012
"... Abstract—There are many factors that provide input into the software development process, such as the values, beliefs, norms, practices, skills, behaviors, knowledge and goals of stakeholders. Research has shown that successful software system development relies on alignment or congruence between th ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
Abstract—There are many factors that provide input into the software development process, such as the values, beliefs, norms, practices, skills, behaviors, knowledge and goals of stakeholders. Research has shown that successful software system development relies on alignment or congruence between these factors. How to monitor the level of congruence between these factors and how to use the congruence as an indicator or a measure to monitor a software development process is a challenge in software engineering. This paper proposes a model that uses three congruence measures to examine the levels of social-technical congruence in software development processes. Using a controlled experiment with seven student teams developing a robot project, this paper demonstrates that the proposed congruence measures provide results consistent with the assessment by the course lecturers. Keywords-social-technical congruence; software engineering process; team performance I.
Australasian Journal of Information Systems IS PROJECT RISKS AS EMERGENT PHENOMENA: TOWARDS A MODEL OF RISK ESCALATION AND ITS MANAGEMENT
, 2015
"... ABSTRACT While the number of substantive investments in IS projects continues to grow, the number of failing projects also continues to increase at an alarming rate. Both the academic and industry literature suggests that inadequate attention to risk and its management continues to be a key factor ..."
Abstract
- Add to MetaCart
ABSTRACT While the number of substantive investments in IS projects continues to grow, the number of failing projects also continues to increase at an alarming rate. Both the academic and industry literature suggests that inadequate attention to risk and its management continues to be a key factor in project failure. The typical approach taken is to identify and map potential risks, to act as a planning and diagnostic tool, and to prepare a contingency plan has been a factorbased approach. While it remains a valuable tool for mapping anticipated risks the factorbased approach is less effective when viewing project risks as emergent phenomena that unfold during the course of the project, and require ongoing attention and risk management. Informed by a case study of a failing university IS development project, this paper focuses on the phenomenon of risk escalation. The case findings suggest that rather than being defined ahead of the project, some project risks may emerge during the project as a consequence of escalation factors that were both antecedent to and a consequence of actual risk management decisions. The article concludes with suggestions as to how project managers can better man-age the emergent rather than static nature of risk phenomena.
ScienceDirect Success Management as a PM knowledge area -work-in-progress-review under responsibility of SciKA -Association for Promotion and Dissemination of Scientific Knowledge
, 2016
"... Abstract It is a fact that an organization's success is closely linked with its projects' success. Although there are many studies in literature that focus on different aspects of project success like, for instance, the success factors or the criteria for success assessment, there are onl ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract It is a fact that an organization's success is closely linked with its projects' success. Although there are many studies in literature that focus on different aspects of project success like, for instance, the success factors or the criteria for success assessment, there are only few studies that mention the processes required for success evaluation. Guides and standards, such as the PMBOK 5 or ISO 21500:2012, are not exceptions to this reality. Given the high importance and complexity of the evaluation of the projects' success, in this work-in-progress the Success Management is proposed as a new knowledge area of project management, as well as a set of processes to be carried out in its scope.
Online Journal of Applied Knowledge Management Effective collaboration and knowledge sharing in short vs. long term SD projects [Research in Progress]
, 2013
"... Abstract Sharing knowledge has become a critical part of inter-enterprise collaboration. Knowledge ..."
Abstract
- Add to MetaCart
Abstract Sharing knowledge has become a critical part of inter-enterprise collaboration. Knowledge
Diagrams or Structural Lists in Software Project Retrospectives – An Experimental Comparison
"... Root cause analysis (RCA) is a recommended practice in retrospectives and cause-effect diagram (CED) is a commonly recommended technique for RCA. Our objective is to evaluate whether CED improves the outcome and perceived utility of RCA. We conducted a controlled experiment with eleven student softw ..."
Abstract
- Add to MetaCart
(Show Context)
Root cause analysis (RCA) is a recommended practice in retrospectives and cause-effect diagram (CED) is a commonly recommended technique for RCA. Our objective is to evaluate whether CED improves the outcome and perceived utility of RCA. We conducted a controlled experiment with eleven student software project teams by using a single factor paired design resulting in a total of 22 experimental units. Two visualization techniques of underlying causes were compared: CED and a structural list of causes. We used the output of RCA, questionnaires, and group interviews to compare the two techniques. In our results, CED increased the total number of detected causes. CED also increased the links between causes, thus, suggesting more structured analysis of problems. Furthermore, the participants perceived that CED improved organizing and outlining the detected causes. The implication of our results is that using CED in the RCA of retrospectives is recommended, yet, not mandatory as the groups also performed well with the structural list. In addition to increased number of detected causes, CED is visually more attractive and preferred by retrospective participants, even though it is somewhat harder to read and requires specific software tools.
An Investigation on the Critical Factors of Information System Implementation in Jordanian Information Technology Companies
"... Current modern life styles, huge amount of the data available and the increased complexity of software products made IT projects extremely challenging projects. In Jordan, IT projects play a significant role in the country's economy. Unfortunately, high percentages of IT projects are considered ..."
Abstract
- Add to MetaCart
Current modern life styles, huge amount of the data available and the increased complexity of software products made IT projects extremely challenging projects. In Jordan, IT projects play a significant role in the country's economy. Unfortunately, high percentages of IT projects are considered to be failed or challenging projects. To avoid project failure, success factors must be maintained and enhanced. This study aims to provide a clear definition of critical success factors in IT projects in Jordan, and to explore the differences in the attitudes of project managers and CEO towards such factors.A structured questionnaire was distributed to a random sample of 118 CEOs and project managers. A total number of 90 completely filled questionnaires were returned. A quantitative data analysis has been conducted for the 18 success factors using SPSS software and Excel program. The study revealed that the majority of IT companies in Jordan have a success rate of 75%. Moreover the study implied that project managers are considered to be the most responsible part for project success. In these organizations, the usage of web applications and Email dominated the list of information transfer methods. According to t-test paired result, there is a clear agreement between the two groups (CEOs and Project Managers) on the critical success
