Bringing Global Sourcing into the Classroom: Experiential Learning via Software Development Project

Global sourcing of software development has imposed new skill requirements on Information Technology (IT) personnel. In the U.S., this has resulted in a paradigm shift from technical to softer skills such as communications and virtual team management. Higher education institutions must, consequently, initiate innovative curriculum transformations to better prepare students for these emerging workforce needs. This paper describes one such venture between Marquette University (MU), U.S.A. and Management Development Institute (MDI), India, wherein IT students at MU collaborated with Management Information Systems (MIS) students at MDI on an offshore software development project. The class environment replicated an offshore client/vendor relationship in a fully virtual setting while integrating communications and virtual team management with traditional IT project management principles. Course measures indicated that students benefited from this project, gained first-hand experience in the process of software offshoring, and learned skills critical for conduct of global business. For faculty considering such initiatives, we describe the design and administration of this class over two semesters, lessons learned from our engagement, and factors critical to success of such initiatives and those detrimental to their sustenance

Library project management in a collaborative web-based working environment

This paper discusses the emerging paradigm of project management performed in a web-based working environment. It highlights how project management and its associated features are strongly linked to fulfilling quality and value criteria for customers, and it examines how collaborative working environments can greatly reduce the administrative burden of managing large projects, especially and almost paradoxically, when resources are limited. Specifically, the paper examines the application of a project management methodology (PRINCE2) together with the use of a collaborative web-based working environment over a number of pilot projects at Leeds University Library. It describes the pilot phase of a library management decision to run a series of major Library projects using project management methodology, while continuing to run other projects through the existing locally developed planning mechanisms and describes the pitfalls of these latter alternatives, less sophisticated project management tools, and describes the main issues that this change in practice has brought to light. It draws preliminary conclusions about the effectiveness of this change in practice in one of the UK’s largest academic libraries

Uptake of BIM and IPD within the UK AEC Industry: the evolving role of the architectural technologist

Building Information Modelling is not only a tool, but also the process of creation, maintenance, distribution and co-ordination of an integrated database that collaboratively stores 2D and 3D information, with embedded physical and functional data within a project-building model. The uptake of BIM within the UK Architecture, Engineering and Construction (AEC) industry has been slow since the 1980’s, but over recent years, adoptions have increased. The increased collaborative nature of BIM, external data sharing techniques and progressively complex building design, promotes requirements for design teams to coordinate and communicate more effectively to achieve project goals. To manage this collaboration, new or evolved job roles may emerge. This research examined the current use of BIM, Integrated Project Delivery (IPD) and collaborative working in the UK AEC industry and job roles that have evolved or been created to cater for them. Using semi-structured interviews the interviewees indicated while several of the key enablers of IPD were being used, IPD itself had not been fully adopted. BIM was being used with some success but improvements could be made. New job roles such as the BIM Engineer and BIM Coordinator had been seen in the industry and evidence that the Architectural Technologist (AT) role is evolving into a more multidisciplinary role; this reflects similar findings of recent research

Comparative Study on Agile software development methodologies

Today-s business environment is very much dynamic, and organisations are constantly changing their software requirements to adjust with new environment. They also demand for fast delivery of software products as well as for accepting changing requirements. In this aspect, traditional plan-driven developments fail to meet up these requirements. Though traditional software development methodologies, such as life cycle-based structured and object oriented approaches, continue to dominate the systems development few decades and much research has done in traditional methodologies, Agile software development brings its own set of novel challenges that must be addressed to satisfy the customer through early and continuous delivery of the valuable software. It is a set of software development methods based on iterative and incremental development process, where requirements and development evolve through collaboration between self-organizing, cross-functional teams that allows rapid delivery of high quality software to meet customer needs and also accommodate changes in the requirements. In this paper, we significantly identify and describe the major factors, that Agile development approach improves software development process to meet the rapid changing business environments. We also provide a brief comparison of agile development methodologies with traditional systems development methodologies, and discuss current state of adopting agile methodologies. We speculate that from the need to satisfy the customer through early and continuous delivery of the valuable software, Agile software development is emerged as an alternative to traditional plan-based software development methods. The purpose of this paper, is to provide an in-depth understanding, the major benefits of agile development approach to software development industry, as well as provide a comparison study report of ASDM over TSDM.Comment: 25 pages, 25 images, 86 references used, with authors biographie