AGILE PRINCIPLES IN TERMS OF QUALITY

The agile project team should produce a product that is of high quality, starting with the development and ending with the test results. Each member of the team contributes his or her best possible work. The following principles are especially important for this:

1. The highest priority is to deliver valuable software to the customer early and continuously.
2. The software should be delivered within a few weeks or months, preferably in the shortest possible time
3. The team must work together on a daily basis
4. The information should be effectively and efficiently communicated to the development team
5. the most important thing is the working software
6. sustainable development is driven by the agile processes The team should be able to maintain a constant pace indefinitely
7. paying attention to good design and high technical quality promotes agility
8. the team should regularly reflect on how it can work more efficiently and effectively

In everyday practice, these principles can be described as follows, for example:

• The development team must be able to act in a self-organized manner, which means that it has full responsibility for solving problems. This includes deciding how the product is created and how the tasks are distributed. The person who does the work is allowed to decide how to do it.
• When software is developed, an agile approach should make the programming and the product flexible and extensible. The design should make unavoidable changes as easy as possible.
• When features are completed, the team presents the functionality to the product owner to determine if it meets the acceptance criteria. This is best done on the same day that the requirements development is completed.
• The working code is presented at the end of an iteration. In this way, progress becomes measurable
• Testing takes place constantly as part of the development and not only at the end of an iteration
• To ensure that the complete solution works, we check at regular intervals whether the new code has been tested and can be integrated without problems (continuous integration CI)
• Examples of technical quality:
  - Setting up coding standards
  - Use of service-oriented architectures
  - Implementation of automated tests
  - Taking future changes into account
  - Determine definition of done
• create only those functionalities that are needed at a specific time
• Show stakeholders and customers only those functionalities that have been approved by the product owner

SOCIAL MEDIA

https://www.facebook.com/vollcomdigital

https://www.linkedin.com/company/10696761

https://twitter.com/Vollcom_Digital

Vollcom Digital GmbH
Thierschstraße 34, 80538 München
info@vollcom-digital.de