271,785 research outputs found

    Towards a business-IT alignment maturity model for collaborative networked organizations

    Get PDF
    Aligning business and IT in networked organizations is a complex endeavor because in such settings, business-IT alignment is driven by economic processes instead of by centralized decision-making processes. In order to facilitate managing business-IT alignment in networked organizations, we need a maturity model that allows collaborating organizations to assess the current state of alignment and take appropriate action to improve it where needed. In this paper we propose the first version of such a model, which we derive from various alignment models and theories

    Is agile project management applicable to construction?

    Get PDF
    This paper briefly summarises the evolution of Agile Project Management (APM) and differentiates it from lean and agile production and ‘leagile’ construction. The significant benefits being realized through employment of APM within the information systems industry are stated. The characteristics of APM are explored, including: philosophy, organizational attitudes and practices, planning, execution and control and learning. Finally, APM is subjectively assessed as to its potential contribution to the pre-design, design and construction phases. In conclusion, it is assessed that APM offers considerable potential for application in predesign and design but that there are significant hurdles to its adoption in the actual construction phase. Should these be overcome, APM offers benefits well beyond any individual project

    A Management Maturity Model (MMM) for project-based organisational performance assessment

    Get PDF
    Common sense suggests that organisations are more likely to deliver successful projects if they have systems in place that reflect a mature project environment based on a culture of continuous improvement. This paper develops and discusses a Management Maturity Model (MMM) to assess the maturity of project management organisations through a customisable, systematic, strategic and practical methodology inspired from the seminal work of Darwin, Deming, Drucker and Daniel. The model presented is relevant to organisations, such as construction and engineering companies, that prefer to use the Project Management Body of Knowledge (PMBOK™ Guide) published by the Project Management Institute (PMI), but without the disadvantages of excessive time and cost commitments and a ‘one size fits all’ approach linked to rigid increments of maturity. It offers a game-changing advance in the application of project-based organisational performance assessment compared to existing market solutions that are unnecessarily complex. The feasibility of MMM is field-tested using a medium-sized data centre infrastructure firm in Tehran

    System implementation: managing project and post project stage - case study in an Indonesian company

    Get PDF
    The research reported in this paper aims to get a better\ud understanding of how the implementation process of\ud enterprise systems (ES) can be managed, by studying the\ud process from an organisational perspective. A review of\ud the literature on previous research in ES implementation\ud has been carried out and the state of the art of ES\ud implementation research is defined. Using several body of\ud literature, an organisational view on ES implementation is\ud described, explaining that ES implementation involves\ud challenges from triple domain, namely technological\ud challenge, business process related challenge, and\ud organisational challenge. Based on the defined state of the\ud art and the organisational view on ES implementation\ud developed in this research, a research framework is\ud presented, addressing the project as well as the postproject\ud stage, and a number of essential issues within the\ud stages. System alignment, knowledge acquisition, change\ud mobilisation are the essntial issues to be studied in the\ud project stage while institutionalisation effort and\ud continuous improvement facilitation are to be studied in\ud the post-project stage. Case studies in Indonesian\ud companies are used to explain the framework

    Software Development Standard and Software Engineering Practice: A Case Study of Bangladesh

    Full text link
    Improving software process to achieve high quality in a software development organization is the key factor to success. Bangladeshi software firms have not experienced much in this particular area in comparison to other countries. The ISO 9001 and CMM standard has become a basic part of software development. The main objectives of our study are: 1) To understand the software development process uses by the software developer firms in Bangladesh 2) To identify the development practices based on established quality standard and 3) To establish a standardized and coherent process for the development of software for a specific project. It is revealed from this research that software industries of Bangladesh are lacking in target set for software process and improvement, involvement of quality control activities, and standardize business expertise practice. This paper investigates the Bangladeshi software industry in the light of the above challenges.Comment: 13 pages, 3 figures, 11 table

    Managing design variety, process variety and engineering change: a case study of two capital good firms

    Get PDF
    Many capital good firms deliver products that are not strictly one-off, but instead share a certain degree of similarity with other deliveries. In the delivery of the product, they aim to balance stability and variety in their product design and processes. The issue of engineering change plays an important in how they manage to do so. Our aim is to gain more understanding into how capital good firms manage engineering change, design variety and process variety, and into the role of the product delivery strategies they thereby use. Product delivery strategies are defined as the type of engineering work that is done independent of an order and the specification freedom the customer has in the remaining part of the design. Based on the within-case and cross-case analysis of two capital good firms several mechanisms for managing engineering change, design variety and process variety are distilled. It was found that there exist different ways of (1) managing generic design information, (2) isolating large engineering changes, (3) managing process variety, (4) designing and executing engineering change processes. Together with different product delivery strategies these mechanisms can be placed within an archetypes framework of engineering change management. On one side of the spectrum capital good firms operate according to open product delivery strategies, have some practices in place to investigate design reuse potential, isolate discontinuous engineering changes into the first deliveries of the product, employ ‘probe and learn’ process management principles in order to allow evolving insights to be accurately executed and have informal engineering change processes. On the other side of the spectrum capital good firms operate according to a closed product delivery strategy, focus on prevention of engineering changes based on design standards, need no isolation mechanisms for discontinuous engineering changes, have formal process management practices in place and make use of closed and formal engineering change procedures. The framework should help managers to (1) analyze existing configurations of product delivery strategies, product and process designs and engineering change management and (2) reconfigure any of these elements according to a ‘misfit’ derived from the framework. Since this is one of the few in-depth empirical studies into engineering change management in the capital good sector, our work adds to the understanding on the various ways in which engineering change can be dealt with
    corecore