The Ethics of Software Development Project Management [1996]*

2021 ◽  
pp. 63-69
Author(s):  
Simon Rogerson
Keyword(s):  
Project Management ◽  
Software Development ◽  
Development Project ◽  
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.

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.

scholarly journals PERFORMANCE EVALUATION OF SOFTWARE DEVELOPMENT PROJECT TEAM

2017 ◽  
Vol 2 ◽  
pp. 118
Author(s):  
Inga Podjavo ◽  
Solvita Berzisa
Keyword(s):  
Decision Making ◽  
Performance Evaluation ◽  
Project Management ◽  
Software Development ◽  
Team Performance ◽  
Development Project ◽  
Project Team ◽  
Software Development Project ◽  
Planning Decision ◽  
Performance Demonstration

The necessity of finding the connection between the planning, decision making, actions and results create project management interest to an evaluation of the project team performance. By analyzing the team performance, determining successful projects and assessing results, members of such project will have the necessary information to avoid failures, to monitor the progress, to compare similar projects and move to defined goals. The objective of this paper is to provide guidelines for evaluation of the project team performance in the software development project. This paper summarizes measures for evaluation of the team performance, an evaluation objectives and it benefits as well as factors that may have an influence on the team performance. Demonstration example of the guideline usage has been provided.

Managing Software Projects with Team Software Process (TSP)

2011 ◽  
pp. 149-182
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.

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 Analysis of Maturity Level Project Management of Software Development In Scrum Framework: Case Research On Tribe Enterprise PT. XYZ

2020 ◽  
Vol 5 (1) ◽  
pp. 87-97
Author(s):  
Fakhrul Ridha ◽  
Ega Hegarini
Keyword(s):  
Project Management ◽  
Software Development ◽  
Quantitative Research ◽  
Development Project ◽  
Agile Development ◽  
Maturity Model ◽  
Maturity Level ◽  
Software Development Project ◽  
Case Research ◽  
A Company

One of the most widely used product developments now is Agile Development Method. In Agile Development there are several frameworks, one of them is Scrum. This research examines the maturity level of software development project management that applies Scrum framework. The research was conducted using quantitative research methodologies using Scrum Maturity Model. Data was collected by distributing questionnaires to employees at a company that works as a Scrum Master. In addition to the data obtained from the questionnaire, interviews were also conducted to confirm answers from respondents. The interview aims to ensure the answers given by respondents are consistent with documentary evidence carried out through the research of project documents. Then the data analysis is done by assessing the level of maturity of each process in the Scrum framework using Agile Maturity Model (AMM) approach. The results from the analysis of Maturity Level Project Management of Software Development are used to provide recommendations for improvement to achieve a higher level of maturity.

Sign in / Sign up

Export Citation Format

Share Document