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

Author(s):  
Nethravathi P. S. ◽  
P. S. Aithal

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

1993 ◽  
Vol 44 (2) ◽  
pp. 203
Author(s):  
Andy Shea ◽  
Dina Berkeley ◽  
Robert de Hoog ◽  
Patrick Humphreys

Author(s):  
Boris Todorović ◽  
Miroslav Matić

This study is focused on the software development process, viewed from perspective of information technology project manager. Main goal of this research is to identify challenges in managing such projects and provide a model for delivering software solutions that satisfies client’s expectations. Project management theory describes six constraints or variables in every project, which project managers can use to better control the project and its outputs. Fixing some of the six project management constraints (scope, cost, time, risks, resources or quality) will allow project manager to focus on most important project aspects, rather than being drawn between all of the variables.This paper is aimed at information technology project managers and portfolio managers, as it describes the practical application of this model on a software development project. Findings of this research support the theory that, by applying good project management practice and focusing on project/business-critical requirements, will enable project managers to complete projects successfully and within tolerance limits. Results show that by identifying key business constraints, project managers can create good balance of six constraints and focus on the most important ones, while allowing other constraints to move between limits imposed by clients and stakeholders.


2012 ◽  
Vol 7 (2) ◽  
pp. 126
Author(s):  
Henry Chong ◽  
Violitta Yesmaya ◽  
Ardian Eko Y.P. ◽  
Novita Sariand ◽  
Zakharia Yudistia Malino

There is nothing in this world that do not change unless the change itself. Almost every aspect of the world, particularly the world of IT, can changed. In project management software, for instance, people have to work on software that frequently subject to change. That is why the greatest challenge faced by the company within today's competitive world is how to deal with those changes. In relation with the previous explanation, the objective of this research is to standardize project management in software development by using change management. Objective will finally help project developer to ensure that the management of project has a need of standardization that essential for reflecting the current business needs. To achieve the objectives, this research will also attempt to show why does the standardization using the change management is essential task, which is almost inevitable. This research directed for discussing about the management of change as a common way to reduce risks, costs and maximizing the benefit from major changes in business and information technology. The result showed that the project can determined as success because it delivered on time, on budged and have a standardized quality. Tidak ada di dunia ini yang tidak berubah kecuali perubahan itu sendiri. Hampir setiap aspek dunia, khususnya dunia IT, dapat berubah. Dalam perangkat lunak manajemen proyek, misalnya, orang harus bekerja pada perangkat lunak yang sering mengalami perubahan. Itu sebabnya tantangan terbesar yang dihadapi perusahaan dalam dunia yang kompetitif saat ini adalah bagaimana menghadapi perubahan tersebut. Sehubungan dengan penjelasan sebelumnya, tujuan dari penelitian ini adalah untuk standarisasi manajemen proyek dalam pengembangan perangkat lunak dengan menggunakan manajemen perubahan. Tujuan akhirnya akan membantu pengembang proyek untuk memastikan bahwa manajemen proyek memiliki kebutuhan standarisasi yang penting untuk mencerminkan kebutuhan bisnis saat ini. Untuk mencapai tujuan tersebut, penelitian ini juga akan mencoba menunjukkan mengapa standarisasi menggunakan manajemen perubahan adalah tugas penting yang tidak dapat dihindari. Penelitian ini diarahkan untuk membahas tentang manajemen perubahan sebagai cara umum untuk mengurangi risiko, biaya dan memaksimalkan manfaat dari perubahan besar dalam bisnis teknologi dan informasi. Hasil penelitian menunjukkan bahwa proyek tersebut dapat dinyatakan sukses karena disampaikan tepat waktu, sesuai budget dan memiliki kualitas standar.


Author(s):  
Janhvi A. Sahare

Abstract: Smart-Sheet is a project management software product, developed and sold by Smart consultancies. It is designed to assist a project manager in developing a plan, assigning resources to tasks, tracking progress, managing the budget, and analysing workloads. Smart sheet can be used as a standalone tool for tracking project progress or it can be used for tracking complex project distributed in many geographical areas and managed by a number of project managers. Smart Sheet is designed to assist a project manager in: 1) Developing a plan, 2) Assigning resources to tasks, 3) Tracking progress, 4) Managing budget and 5) Analysing workloads. In this study an effort is made to estimate the changes in overall cost and time required to execute the phase 1 work of Nagpur metro rail project when done by conventional execution approach and when done by project management software tool of smart sheet Keywords: Project management, Smart sheet, Conventional construction execution, Cost optimization, Time optimization, Resource optimization.


2013 ◽  
pp. 84-117
Author(s):  
Salmiza Saul Hamid ◽  
Mohd Hairul Nizam Md Nasir ◽  
Shamsul Sahibuddin ◽  
Mustaffa Kamal Mohd Nor

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.


Author(s):  
Marcos Ruano-Mayoral ◽  
Ricardo Colomo-Palacios ◽  
Ángel García-Crespo ◽  
Juan Miguel Gómez-Berbís

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.


Author(s):  
Charles K. Davis

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.


Sign in / Sign up

Export Citation Format

Share Document