Global Software Development Project Management – Distance Overcoming

2004 ◽  
pp. 23-33 ◽  
Author(s):  
Darja Šmite
Keyword(s):  
Project Management ◽  
Software Development ◽  
Development Project ◽  
Global Software Development ◽  
Software Development Project

scholarly journals Scrum+: A scaled Scrum for the agile global software development project management with multiple models

2019 ◽  
pp. 105-116
Author(s):  
César Jesús Pardo Calvache ◽  
Piedad Rocío Chilito Gomez ◽  
Daniel Esteban Viveros Meneses ◽  
Francisco José Pino Correa
Keyword(s):  
Project Management ◽  
Focus Group ◽  
Software Development ◽  
Management Practices ◽  
Development Project ◽  
Global Software Development ◽  
Multiple Models ◽  
Software Development Project ◽  
Global Projects ◽  
Agile Software

Nowadays, carrying out a project management is difficult in any situation, even more in global projects of software development, whose environment faces different aspects that make this type of projects even more difficult to manage, for example: lack of coordination, lack of face to face communication, temporary differences, cultural diversity and application of different standards, models and approaches. With the aim of supporting agile global software development (AGSD)  project management when multiple models are present, we have defined Scrum+, which is a guide based on Scrum and defines a set of activities, tasks, roles and criteria to support AGSD projects in multimodel environments. We carried out the harmonization of agile approach Scrum along with project management practices defined in multiple models such as: ISO/IEC 15504, ISO 9001 and CMMI-DEV.  Likewise, the evaluation of the proposal has been conducted through: (i) its application in a focus group with experts in different related areas and (ii) its assessment of the degree of agility by means 4-DAT method. Based on the analysis of the results and the comments obtained in the focus group, Scrum+ seems to be clear, adequate, and agile. The guide proposed here can serve as reference for studying further aspects related to agile software scaled projects.

Making Agile Development and Offshoring Practice Successful on Global Software Development Project

2013 ◽  
pp. 107-119
Author(s):  
Edward Chen
Keyword(s):  
Software Development ◽  
Development Project ◽  
Lessons Learned ◽  
Global Software Development ◽  
Agile Development ◽  
Business Practices ◽  
Global Business ◽  
Software Development Project ◽  
Business Applications ◽  
Develop Software

Two significant trends have been gaining momentum in software development: the utilization of Agile development methodologies, and the continuing trend of companies to outsource development work offshore. These two trends have changed the way companies develop software and business applications. This chapter seeks to evaluate how a company can successfully manage both trends in conjunction with each other on global business. The primary question addressed is whether the benefits derived from Agile development methodologies and the savings from outsourced software development efforts cancel each other out when applied together, or whether they create a synergy greater than the sum of the parts. In order to answer this question, this chapter intends to examine several relevant business practices and industry experiences. From lessons learned, we identify factors which seem to influence a successful combination of Agile methodology and offshoring in global software development projects.

Managing Software Projects with Team Software Process (TSP)

2013 ◽  
pp. 84-117
Author(s):  
Salmiza Saul Hamid ◽  
Mohd Hairul Nizam Md Nasir ◽  
Shamsul Sahibuddin ◽  
Mustaffa Kamal Mohd Nor
Keyword(s):  
Project Management ◽  
Software Development ◽  
Management Practices ◽  
Software Process ◽  
Development Project ◽  
Software Projects ◽  
Engineering Teams ◽  
Software Development Project ◽  
Software Failure ◽  
Team Software Process

Despite the widespread use of sound project management practices and process improvement models over the last several years, the failure of software projects remains a challenge to organisations. As part of the attempt to address software industry challenges, several models, frameworks, and methods have been developed that are intended to improve software processes to produce quality software on time, under budget, and in accordance with previously stipulated functionalities. One of the most widely practised methods is the Team Software Process (TSP). The TSP was designed to provide an operational framework for establishing an effective team environment and guiding engineering teams in their work. This chapter provides an overview of the TSP and its associated structures and processes. It also highlights how the TSP operational framework can assist project manager and software development team to deliver successful projects by controlling and minimizing the most common software failure factors. Comparative analysis between the TSP and conventional project management has also been presented. Additionally, the results of TSP implementation in industrial settings are highlighted with particular reference to scheduling, quality, and productivity. The last section indicates additional advantages of TSP and comments on the future of TSP in the global software development project.

An Experiential Case Study in IT Project Management Planning

2011 ◽  
pp. 1-21
Author(s):  
Charles K. Davis
Keyword(s):  
Project Management ◽  
Software Development ◽  
Role Playing ◽  
Development Project ◽  
Organizational Setting ◽  
Management Planning ◽  
Software Development Project ◽  
Information Technology Project ◽  
Key Issues ◽  
Information Technology Project Management

The case covers key issues in information technology project management. It deals with developing a full set of project plans, including milestones, tasks, schedules, staffing, deliverables, and projected costs, for a complex software development project (Gido & Clements, 2003; Kerzner, 2003; Schwalbe, 2002). The essence of this case is the analyzing of a specific organizational setting with critical software needs and the developing of the needed plans. As in many similar situations, this organization is relatively complex, and the situation is not entirely clear. By reviewing the facts of the case, collecting outside information, conducting role playing interviews, analyzing requirements, and estimating schedules and costs, one can collect the information needed to develop baseline project plans for the software development envisioned in this case.

Bounded becoming: insights from understanding projects in situation

2012 ◽  
Vol 5 (3) ◽  
pp. 345-363 ◽  
Author(s):  
Viviane Sergi
Keyword(s):  
Project Management ◽  
Software Development ◽  
Design Methodology ◽  
Development Project ◽  
Process Ontology ◽  
Content Type ◽  
Software Development Project ◽  
Specific Practice ◽  
The Moment ◽  
Over Time

PurposeThe purpose of this paper is to suggest a situated conception of projects, in order develop finer understanding of how these endeavors emerge and unfold over time. The author proposes that these understandings should be rooted in a process ontology, conceive action as situated and focus on actual practices as they are performed by all project actors. Taken together, these dimensions can renew how one views and approaches projects and their management.Design/methodology/approachThe paper is illustrated with examples taken out of a study of a software development project, conducted in the ethnographic tradition.FindingsThe examples expose how a specific practice, planning, was accomplished differently depending on the moment and was affected by different circumstances and constraints. The paper also discusses how preferring a processual worldview is especially befitting projects. As endeavors instigated to create or to make something happen, projects are perpetually changing and in movement; it is therefore relevant that their conceptualization takes fully into consideration their intimate nature.Originality/valueThe originality and value of the paper lie in the combination of perspectives, which can be both useful in theorizing projects differently, and in enhancing practitioners' reflexivity. This combination, it is argued, can address a wide array of issues in the context of projects, can favor localized reflection on project management prescriptions and tools, and can help practitioners to sharpen their sensitivity to their own practice.

Coordination implications of software architecture in a global software development project

2010 ◽  
Vol 83 (10) ◽  
pp. 1881-1895 ◽  
Author(s):  
Alberto Avritzer ◽  
Daniel Paulish ◽  
Yuanfang Cai ◽  
Kanwarpreet Sethi
Keyword(s):  
Software Development ◽  
Software Architecture ◽  
Development Project ◽  
Global Software Development ◽  
Software Development Project
Sign in / Sign up

Export Citation Format

Share Document