Research on Software Product Development Project Management

2013 ◽  
Vol 347-350 ◽  
pp. 457-460
Author(s):  
Jin Hai Zhang
Keyword(s):  
Project Management ◽  
Software Development ◽  
Implementation Strategies ◽  
Development Project ◽  
Software Project ◽  
Project Organization ◽  
Main Research ◽  
Software Development Project ◽  
Organization And Management ◽  
Enterprise Application

Project organization and management software development project management model is the best form of software development enterprises in China's understanding of software development project management has been greatly improved. Traditional software development projects have different characteristics, therefore how flexible application for software project management theory and strategies of the main research objectives of domestic software development project management. Our software in enterprise application software development project management, general shortcomings in implementation, this article on software research and development analysis and project management of implementation strategies.

scholarly journals Towards a methodology to estimate cost of object-oriented software development projects

2004 ◽  
Vol 1 (2) ◽  
pp. 173-194 ◽  
Author(s):  
Radoslav Rakovic
Keyword(s):  
Software Development ◽  
Development Process ◽  
A Priori ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Subsequent Development ◽  
Development Project ◽  
Software Project ◽  
Software Development Project ◽  
Early Estimate

Successful management of a software project, besides a well-defined project development process, requires an early estimate of project complexity. In a prevailing practice, software development costs usually have been determined a posteriori i.e. after software project implementation. It is essential however, to know this estimate a priori, i.e., before commencement of works. This paper presents an attempt to construct a methodology that would enable an early estimate of software development cost and its refinements during subsequent development phases. The methodology assumes an object-oriented approach based on the Unified Modeling Language (UML) and Unified Software Development Process (USDP). It outlines an Use Case Driven Architecture-Centric, Iterative and Incremental estimate process that could significantly improve and simplify early cost estimates. The presented methodology is illustrated on example of the POST software development project.

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.

Software Project Managers under the Team Software Process

2012 ◽  
pp. 115-126
Author(s):  
Marcos Ruano-Mayoral ◽  
Ricardo Colomo-Palacios ◽  
Ángel García-Crespo ◽  
Juan Miguel Gómez-Berbís
Keyword(s):  
Software Development ◽  
Software Process ◽  
Development Project ◽  
Project Managers ◽  
Project Manager ◽  
Software Project ◽  
Software Projects ◽  
Software Development Project ◽  
Team Software Process ◽  
Definition Of

Despite the clear relevance of the Information and Communications Technologies (ICT) market in world economics and the evident lack of success of software projects, organizations devote little effort to the development and maturity of the software project manager profession. This work analyzes the figure of project manager from the perspective of the Team Software Process (TSP), and it considers the required skills, attitudes and knowledge for a software development project. The basis for the study is the analysis of relevant references from the literature for their subsequent categorization into different competency concepts. The results of the analysis are compared with the contributions which the Guide to the SWEBOK® and the PMBOK® Guide models provide of the profiles of the project manager. The results indicate that the literature relating to the Team Software Process is focused on the definitions of skills and attitudes, and to a lesser extent on knowledge components. The lack of the definition of the components which comprise competency constitutes a challenge for software development organizations that use TSP, whose project managers should confront the task with full capacities, and without the help of established and recognized competencies. The current work attempts to establish the competencies for project managers identified in the literature, in the environment of the use of TSP for software development, using a study based on content analysis.

QPLAN

2017 ◽  
pp. 259-283
Author(s):  
Marco Antônio Amaral Féris
Keyword(s):  
Software Development ◽  
Design Science ◽  
Science Research ◽  
Design Science Research ◽  
Research Process ◽  
Project Performance ◽  
Development Project ◽  
Software Project ◽  
Software Development Project ◽  
Key Factor

As business competition increases, there is pressure on software development projects to become more productive and efficient. Previous research has shown that quality planning is a key factor in enhancing project performance. Thus, this article reports on the successful development and implementation of a tool (QPLAN) that enhances software development project performance by evaluating the planning quality of any type of software project and introducing best planning practices (such as references from historical data) that suggest how to manage projects in an appropriate manner, including encompassing lessons learned and involving the customer in the development process. This is applied research aimed at solving a real problem; thus, Design Science Research was adopted as the research methodology and the design science research process (DSRP) model was selected to conduct it. This artifact was designed for the project management literature, and implemented and validated in 11 organizations in five countries.

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.

A study of software development project cost, schedule and quality by outsourcing to low cost destination

2016 ◽  
Vol 29 (3) ◽  
pp. 454-478 ◽  
Author(s):  
Debasisha Mishra ◽  
Biswajit Mahanty
Keyword(s):  
Software Development ◽  
Development Project ◽  
Dynamics Simulation ◽  
Software Project ◽  
Design Work ◽  
Project Cost ◽  
Content Type ◽  
Software Development Project ◽  
Study Results ◽  
Testing Work

Purpose – The purpose of this paper is to find good values of onsite-offshore team strength; number of hours of communication between business users and onsite team and between onsite and offshore team so as to reduce project cost and improve schedule in a global software development (GSD) environment for software development project. Design/methodology/approach – This study employs system dynamics simulation approach to study software project characteristics in both co-located and distributed development environments. The authors consulted 14 experts from Indian software outsourcing industry during our model construction and validation. Findings – The study results show that there is a drop in overall team productivity in outsourcing environment by considering the offshore options. But the project cost can be reduced by employing the offshore team for coding and testing work only with minimal training for imparting business knowledge. The research results show that there is a potential to save project cost by being flexible in project schedule. Research limitations/implications – The implication of the study is that the project management team should be careful not to keep high percentage of manpower at offshore location in distributed software environment. A large offshore team can increase project cost and schedule due to higher training overhead, lower productivity and higher error proneness. In GSD, the management effort should be to keep requirement analysis and design work at onsite location and involves the offshore team in coding and testing work. Practical implications – The software project manager can use the model results to divide the software team between onsite and offshore location during various phases of software development in distributed environment. Originality/value – The study is novel as there is little attempt at finding the team distribution between onsite and offshore location in GSD environment.

scholarly journals ROI Estimation in a Scrum Project: A case study

10.29007/nqq6 ◽  
2019 ◽  
Author(s):  
Rita Cortés ◽  
Fulvio Lizano
Keyword(s):  
Software Development ◽  
Return On Investment ◽  
Investment Decisions ◽  
Development Project ◽  
Project Managers ◽  
Future Research ◽  
Software Project ◽  
Software Development Project ◽  
Financial Metrics

Financial metrics are necessary to inform decisions about the beginning or continuity of a software development project to justify investments. This research discuses initial ROI (Return on Investment) estimates in a software project using Scrum and how to analyze variations in the initial calculations to make return on investment decisions during partial deliveries of the product. The case study included a survey, a review of documentation, two focus group sessions, and an exercise involving application of the proposed technique. Twenty-four professionals participated, of which 4 were Scrum trainers (17%), 4 were officials of the company where the estimation technique was applied (17%), and 16 were project managers of domestic and foreign software development companies (66%), all of whom had experience in project management. This study provides elements to be considered in future research on ROI calculation in projects using Scrum, and can be used as a guide to estimate and review financial metrics during the execution of an actual project.

Sign in / Sign up

Export Citation Format

Share Document