Software Development Project Management: Process and Support.

1993 ◽  
Vol 44 (2) ◽  
pp. 203
Author(s):  
Andy Shea ◽  
Dina Berkeley ◽  
Robert de Hoog ◽  
Patrick Humphreys
Keyword(s):  
Project Management ◽  
Software Development ◽  
Development Project ◽  
Management Process ◽  
Software Development Project

scholarly journals A Study on Requirement Specifications and Modifications During the Software Development Life Cycle in M/S Kakunje Software Private Limited

2021 ◽  
pp. 142-161
Author(s):  
Nethravathi P. S. ◽  
P. S. Aithal
Keyword(s):  
Project Management ◽  
Software Development ◽  
Development Project ◽  
Project Manager ◽  
Second Phase ◽  
Management Process ◽  
Project Schedule ◽  
Management Software ◽  
Software Development Project ◽  
Project Management Software

Background/Purpose: In order to face the challenge of optimization and allocation of necessary requirements to complete a project with in the allocated time period, the project manager must be efficient in applying different technical skills and managerial strategies to the project management process. In order to develop a software and mobile application product, a company schedules different process as per the specified order and unique requirements. As the history of project management reminds that most of the industries started to implement this concept by observing the success of mega engineering projects because of the effective utilization of project management concept. Objective: This work is carried to understand the concepts of project management in software firms. To investigate the implementation and importance of these concepts and to know the role of project manager in managing the process in software development. Design/Methodology/Approach: Kakunje Software Private Limited, Mangalore, provides excellent and state-of-the-art customized software and hardware solutions as per the necessities of customers. In order to manage the project activities CEO, CFO and CTO all together acts as project manager. The software development project management process starts by identifying needs and recommending solutions, which can be delivered to value its stakeholders. At the second phase the actual development will begin and the developed software will be tested according to customer requirements. Findings/Results: Budgeting, cost management, finance planning etc., represented by CPM and PERT charts by using Microsoft Project and Atlassian JIRA project management software. The project resources, which are used to manage the project and allocation of technical staff are represented by histogram. With the help of Gantt Chart software development project schedule of 5 month are shown. Conclusion: To manage Kakunje business in an effective and gainful manner, the company managed overall internal and external risks of the project. By using the project management software, the company condensed the project manager’s efforts and human errors to manage multiple projects. Paper Type: Case study-based Research Analysis

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.

Sign in / Sign up

Export Citation Format

Share Document