This paper is a basic work for introducing the CMMI for in-house software development department. The purpose of this paper is to develop a ground and a clear understanding for the organizations who are willing to adapt the best practices in general for increasing the functional and technical efficiency at their in-house software development department.
Normally the CMMI is implemented at organization level in the software development, software engineering, system engineering or system security organizations. The main theme of this paper is to attain CMMI level-2 in software development department.
Once the best practices become common in an organization at departmental level, that opens new horizons to build high level understanding of more mature and simplified set of processes that leads toward the organizational maturity which covers the set of overall process areas across the organization. There are various factors involve that limits an organization to adopt a process improvement model.
Usually the new emerging organizations having the staff who have previous experience in highly functioning organizations plan to adapt the process improvement models. It is also a dilemma that small and medium size organizations could not establish successful implementation of Software improvement process models because such organizations work in limited resources and restrict time frame [1]. It is more hard to adapt the CMMI at departmental level because main focus of such an organization is towards the productivity or the main stream of the business.
Specifically, this paper will provide the structural process and case study of software development department of an organization having very diversified functional and financial dimensions to improve functional efficiency from poorly controlled activities to a managed environment or in short achieving the CMMI maturity level-2.
Table of Contents
1. INTRODUCTION
2. HISTORY OF CMMI
3. CMMI COMPONENTS
4. BENEFITS OF CMMI
5. CASE STUDY OF ‘AKHUWAT’
5.1 Requirements Management
5.2 Project Planning
5.3 Project Monitoring and Control
5.4 Measurement and Analysis
5.5 Process Quality Assurance
5.6 Configuration Management
6. FUTURE WORK
7. CONCLUSION
Research Objectives and Core Themes
This paper aims to provide a foundational understanding for organizations seeking to implement CMMI best practices at the departmental level, specifically focusing on achieving CMMI maturity level-2 within an in-house software development environment to improve technical and functional efficiency.
- Implementation of CMMI level-2 in software development departments.
- Transitioning from poorly controlled activities to a managed, stable environment.
- Bridging communication gaps between technical units and the rest of the organization.
- Overcoming resource and budgetary constraints in small to medium-sized entities.
- Structuring organizational processes through rigorous, standardized best practices.
Excerpt from the Book
5.1 Requirements Management
At the initial stages there was a there was a single part time developer at Akhuwat. The software development department was stablished and development of credit management system was started without any processes. In due course budgets were allotted for the department for capacity building, making processes, user trainings and for software process improvement. A fully qualified software development team was hired; Detailed list of requirements were setup. Processes and policies were defined and working hierarchies were structured to manage and monitor the functions and activities.
Summary of Chapters
1. INTRODUCTION: Provides an overview of the Capability Maturity Model Integration (CMMI) and explains its role as a collection of best practices for organizational process improvement.
2. HISTORY OF CMMI: Outlines the origins of CMMI and its application across various disciplines like software and system engineering.
3. CMMI COMPONENTS: Describes the two main representations of CMMI, namely 'Staged' and 'Continuous', and explains the roles of Generic and Specific Goals.
4. BENEFITS OF CMMI: Discusses how adopting CMMI leads to increased productivity, higher product quality, and improved ROI for organizations.
5. CASE STUDY OF ‘AKHUWAT’: Presents a real-world application of CMMI level-2 implementation within the software development department of the organization ‘Akhuwat’.
6. FUTURE WORK: Suggests ongoing improvements and research to maintain maturity levels and further refine organizational policies.
7. CONCLUSION: Summarizes the necessity of adopting structured methodologies like CMMI for long-term organizational survival in the fast-paced technology era.
Keywords
Department level CMMI, Process Improvement, Process maturity, CMMI Level-2, Software development, Organizational maturity, Managed environment, Quality assurance, Configuration management, Project planning, Technical efficiency, Best practices, System engineering.
Frequently Asked Questions
What is the primary focus of this research paper?
The paper focuses on the introduction and practical application of CMMI level-2 best practices specifically tailored for in-house software development departments.
What are the core thematic areas discussed in the work?
The paper covers the history and components of CMMI, its organizational benefits, and a detailed case study illustrating the implementation of specific process areas.
What is the main objective or research question?
The objective is to establish a clear framework for organizations to transition from poorly controlled development processes to a managed environment, thereby achieving CMMI maturity level-2.
Which scientific methodology is utilized?
The research utilizes a case study approach, analyzing the practical implementation of CMMI processes within the specific context of the ‘Akhuwat’ organization.
What topics are covered in the main body?
The main body covers requirements management, project planning, project monitoring and control, measurement and analysis, process quality assurance, and configuration management.
Which keywords best characterize this work?
Key terms include CMMI level-2, Process Improvement, Software development, Process maturity, and Departmental-level implementation.
Why is it difficult for small organizations to adopt these models?
Small organizations often face budget constraints, limited resources, and tight timeframes, which makes the rigorous adoption of improvement models like CMMI challenging.
How does the case study illustrate the transition to a managed environment?
The case study shows how ‘Akhuwat’ moved from having no defined IT processes to hiring a qualified team and establishing formal policies for project planning and quality assurance.
Why is CMMI considered essential for survival in the current technological era?
In a fast-growing technology era, failing to structure organizational units and implement mature, standardized methodologies leaves companies unable to adapt to change efficiently.
- Citar trabajo
- Rehan Shabbir (Autor), 2017, The Adaption of CMMI for an In-House Software Development Department, Múnich, GRIN Verlag, https://www.grin.com/document/382077
