To map modern business processes in IT systems, increasingly complex software solutions and interfaces are required. When developing these, specific quality requirements must be met. Without an adequate and suitable quality management, problems can arise during the development; for example, if changes are made in the day-to-day business during a project, these often also impact the goals and technical requirements. If test specifications are missing, no overview of the required test cases is possible. If test cases from previous versions are not available as regression tests, the adaptations of the existing software are not or only insufficiently tested. Later software failures or faulty data processing can cause high damages due to production downtimes, damage to reputation and demotivated employees. Poorly or untested software and projects in which requirements are only inadequately met can lead to cost overruns and missed deadlines and thus jeopardise the company's success
Unfortunately, while regular projects can be clearly circumscribed, planned and executed, and the requirements are mostly determined from the beginning, this does not seem to apply to IT developments. IT projects are not an end in themselves but serve specific business units to fulfil their tasks. Often, certain activities shall be carried out more efficiently through IT-supported processes, or additional outputs will be generated to benefit the company. The concerns here can be manifold. However, it is often essential that at least two areas communicate with each other that have little understanding for each other. In practice, it often looks like the business department tries to explain to the IT department what is needed without naming specific IT attributes. On the other hand, the IT employee tries to translate the described wishes and programme them. Unfortunately, the IT employee often lacks the technical knowledge of the subject and doesn’t know which data should be linked with each other or which algorithms describe the process best.
Table of Contents
Introduction
Quality Management in IT-Projects
Quality Challenges in Software Development
Causes of Quality Issues in IT Development
Recommendations to improve Quality in I.T.
Software Development Process with QM Elements
Summary
Objectives and Topics
This report aims to analyze the challenges of quality management within IT projects, specifically focusing on the conflicts between traditional, process-oriented quality standards and the necessity for flexibility in agile software development. It examines why IT projects often face cost and schedule overruns, explores the root causes of these quality deficiencies, and proposes strategies such as the use of quality gates and tailored agile methodologies to mitigate project risks.
- The divergence between business requirements and technical IT implementation.
- Root causes of software quality defects and project failure.
- The limitations of classical quality management in agile environments.
- Implementation of quality gates and standardized information exchange.
- Integration of quality management practices into agile frameworks like Extreme Programming (XP).
Excerpt from the Book
QUALITY CHALLENGES IN SOFTWARE DEVELOPMENT
As mentioned, development projects in the field of IT are often subject to permanent changes due to an initially vague description of the specifications and requirements (Pandeyk, 2010). Therefore, agile project management methods are regularly used in IT projects. With the help of agile methods such as Scrum, XP, Kanban or Lean Management, the development of software projects has been optimised and simplified for years (Jamieson & Fallah, 2012). This applies to most projects, starting with the planning phase, through implementation, to the subsequent evaluation of the project. Agile organisations are particularly recommended for complex environments, as unforeseen changes require quick reactions and rethinking. Such project management methods are generally characterised by lean processes, fast iteration cycles and focusing on short-term goals. The project strategy is aligned with the customer and their needs. Open and direct communication, a learning-by-doing mentality and the principle of transparency are also central elements in daily agile activities.
However, this is where classical quality management reaches its limits. Classical quality management was introduced to control quality systematically. The systematic approach is necessary because quality is widely understood and can have different targets. For example, developers look for clarity of design and maintainable code, those responsible for operations look for stability and usability, users look for complete implementation of their requirements and software ergonomics, project managers look for adherence to the project process, and finally, clients look for adherence to budgets and deadlines. To align itself with these goals, classical quality management starts from the company’s overall goals and derives the objectives for software packages from them. This approach is followed in particular in (TQM) (Youssef & Youssef, 2016). The advantage of classical quality management is that it offers managers a framework for action within quality that can be systematically developed, and the achieved status can be evaluated. However, since classical quality management procedures are strongly process-oriented, they are too inflexible for agile development projects and lead to inefficient and ineffective measures (Peng, et al., 208). Due to their permanent changes, software developments require a different approach than classic process standardisation, which often seems oversized for small and medium-sized software projects.
Chapter Summary
Introduction: Provides a context for IT project complexity, discussing the communication gap between business and IT departments and the resulting risks of cost and schedule overruns.
Quality Management in IT-Projects: Examines how agile methodologies emerged to address the limitations of classical quality management in dynamic IT development environments.
Quality Challenges in Software Development: Analyzes specific organizational obstacles, such as the inherent inflexibility of traditional quality frameworks when applied to agile software iteration.
Causes of Quality Issues in IT Development: Investigates root causes ranging from unclear requirement definitions and immature technologies to communication failures and poorly estimated project complexity.
Recommendations to improve Quality in I.T.: Suggests practical interventions including detailed scope description, the use of quality gates, and better alignment between business expectations and technical specifications.
Software Development Process with QM Elements: Explores Extreme Programming (XP) as an example of a radical agile method that integrates quality assurance directly into the iterative development cycle.
Summary: Concludes that efficient quality management in IT must move away from rigid formality toward flexible, result-oriented, and explicitly integrated processes within the development team.
Keywords
Quality Management, IT Projects, Agile Methodology, Software Development, Scrum, Extreme Programming, Requirements Engineering, Quality Gates, Process Optimization, Risk Management, Stakeholder Communication, Business Units, Specification Sheets, Iterative Processes, Technical Debt.
Frequently Asked Questions
What is the primary focus of this report?
The report explores the intersection of quality management and IT project development, focusing on the difficulties of maintaining high quality standards amidst the change-driven nature of agile software projects.
What are the central thematic areas covered?
Key topics include the communicative divide between business and IT departments, the identification of quality failure risks, the failure of classical quality models in agile environments, and the implementation of modern agile quality practices.
What is the primary research goal?
The goal is to determine how to successfully integrate quality management into agile IT projects to improve efficiency and reduce the likelihood of budget and timeline overruns.
Which scientific methods are analyzed?
The report contrasts traditional, process-oriented quality management (such as TQM) with agile methodologies like Scrum, Kanban, and specifically Extreme Programming (XP).
What does the main body of the work address?
It addresses the "why" and "how" of quality issues, providing a granular look at sources of project failure and concluding with actionable recommendations like cross-departmental coordination and the use of quality gates.
Which keywords characterize this work?
The work is defined by concepts such as Quality Management, Agile Project Management, Requirements Engineering, Quality Gates, and Software Development Process.
How do "Quality Gates" improve the management of an IT project?
Quality gates function as scheduled milestones where work status is checked against checklists. If tasks are unfulfilled, an escalation process prevents the project from dragging on with unresolved, cumulative issues.
Why does the author consider "Extreme Programming" (XP) a radical implementation?
XP is considered radical because it prioritizes iteration and constant testing above all else, breaking away from traditional waterfall-style planning to ensure errors are detected and eliminated almost immediately during development.
- Arbeit zitieren
- Martin Henschelchen (Autor:in), 2022, Quality Management in IT-Projects, München, GRIN Verlag, https://www.grin.com/document/1250259
