Behavioural Aspects of Software Project Management- In- House Software Development

This research paper aims an analytical study on the software development organization insight into trending automation technologies and their implementation Software Engineering Management (SEM) processes. Software Project Management (SPM) is a scientific art for planning, controlling execution and monitoring. SPM approaches are more focusing towards the essential requirement for the success of software project development. It has been very challenging to manage software development using existing project management procedures driven by software development organizations and this is one of the areas of problem statement for this research. This paper discusses an analytical study for the requirements and consideration of BPR in SPM, explores to spot and emphasizes the important success factors for the execution of a BPR using benefits of Artificial Intelligence (AI) in software development organization. BPR is organizational mechanism that improves ability to respond to challenges of qualitative result by change and improvement in software engineering processes, productivity, product quality and competitive advantages. AI will be the best approach and scope of automation SEM processes for software development organizations. This paper also represents a conceptual view of software engineering model shift for improvements in capability of project managers to handle agile thinking and problem solving for betterment of SPM using Artificial Intelligence.

Download Full-text

eXtreme Programming, Agile Methodologies, Software Project Management, Customer Role, Rigorous Testing

10.4018/978-1-7998-7872-8.ch009 ◽

2022 ◽

pp. 163-182

Author(s):

Kamalendu Pal

Keyword(s):

Project Management ◽

Software Development ◽

Extreme Programming ◽

Acceptance Testing ◽

Software Project ◽

Software Project Management ◽

Software Projects ◽

Agile Methodologies ◽

Rigorous Testing ◽

Software Development Methodologies

Agile software development methodologies are attracting attention from academics and practitioners for planning and managing software projects. The eXtreme Programming (XP) challenges conformist wisdom regarding software system development processes and practices as agile methodologies. To work efficiently in the current software development practice, characterized by requirements fuzziness, XP moves away from document-centric operations into people-centric management. In the XP-based software project, the customers play an essential role, having multiple responsibilities such as driving the project, gathering requirements (‘user stories'), and exercising quality control (or acceptance testing). Besides, the customers must liaise with external project stakeholders (e.g., funding authorities, end-users) while maintaining the development team's trust and the wider business. The success of such software project management practices relies on the quality result of each stage of development obtained through rigorous testing. This chapter describes three characteristics of XP project management: customer role, software testing feedback, and learning.

Download Full-text

The Principle of Architecture First in Software Project Management Minimizes the Cost of Software Development Process: A Review

International Journal of Innovative Technology and Exploring Engineering - Special Issue ◽

10.35940/ijitee.a8154.1110120 ◽

2020 ◽

Vol 10 (1) ◽

pp. 177-179

Keyword(s):

Project Management ◽

Software Development ◽

Software Architecture ◽

Development Process ◽

Risk Mitigation ◽

System Level ◽

Software Project ◽

Software Development Process ◽

Software Project Management ◽

The Cost

Software architecture involves the structure and organization by which modern system components and subsystems interact to form system and the properties of systems that can best be designed and analyzed at the system level. This paper provides a review of the principles of architecture first approach in software project management and its effect on cost of software development process. This paper reviews the literature and practitioners’ experiences relating to architecture first approach, and advantages of architecture first approach in cost of software development process. This paper also reviews related works about factors that may reduce the cost of software development process. Weobserved parameters related to software architecture that may affect the cost of software development process.The parameters are software (product) delivery time, defect prevention, risk mitigation, and change management. After this, the parameters show that they have their own effect on the software development process. Finally, the paper concludes by describing how those parameters affect the cost of software development process.

Download Full-text

Identifying risks of software project management in Global Software Development: An integrative framework

2016 IEEE/ACS 13th International Conference of Computer Systems and Applications (AICCSA) ◽

10.1109/aiccsa.2016.7945664 ◽

2016 ◽

Cited By ~ 4

Author(s):

Saad Yasser Chadli ◽

Ali Idri ◽

Jose Luis Fernandez-Aleman ◽

Joaquin Nicolas Ros ◽

Ambrosio Toval

Keyword(s):

Project Management ◽

Software Development ◽

Global Software Development ◽

Software Project ◽

Software Project Management ◽

Integrative Framework

Download Full-text

Identifying Challenges and a Research Agenda for Flow in Software Project Management

Project Management Journal ◽

10.1177/8756972818800559 ◽

2018 ◽

Vol 49 (6) ◽

pp. 103-118 ◽

Cited By ~ 2

Author(s):

Denis Dennehy ◽

Kieran Conboy

Keyword(s):

Project Management ◽

Software Development ◽

Real World ◽

Research Agenda ◽

Generic Version ◽

Development Projects ◽

Software Project ◽

Software Project Management ◽

Extant Literature ◽

World Environment

Flow and its associated tools and metrics are increasingly being reported as an approach used to achieve continuous deployment of software and delivery of value in software development projects. Yet, the extant literature on flow tools to date is rather limited. Also, what does exist tends to largely focus on the generic version of flow, rather than any rigorous examination of its use in the turbulent and constantly changing ‘real world’ environment within which it is applied. This study draws on a longitudinal case to identify the challenges of implementing flow and to provide a research agenda for flow project management.

Download Full-text