PaR - Processes as Requirements
The Book
Seiten
2022
|
2. Auflage
epubli (Verlag)
9783757503895 (ISBN)
epubli (Verlag)
9783757503895 (ISBN)
- Titel leider nicht mehr lieferbar
- Artikel merken
Defining the standards and Processes as Requirements (PaR) that match regulatory standards and are reused in the projects is a smart and intrinsic approach that is welcomed by the teams.
Standards and processes should be an exoskeleton that helps the teams to move safely and efficiently through the storms of the projects. Instead, often the processes grow excessively over time, e.g. because they are designed by central departments that are acting far away from the projects, only looking at the standards. Then the exoskeleton rather becomes a heavy backpack that the projects have to carry in addition to the customers' load. When your teams start considering processes being rather extra effort than help, it is time again to listen to the projects' voice. Actually, standards and processes are just requirements saying "how" to do the "what" in a way of proven best practices. The latter ("what") often is given by a customer as functional and technical product requirements. So, why not defining the former ("how") also as what they are? As requirements that can be reused in projects and during work united with the product requirements in the same developer tool!
Standards and processes should be an exoskeleton that helps the teams to move safely and efficiently through the storms of the projects. Instead, often the processes grow excessively over time, e.g. because they are designed by central departments that are acting far away from the projects, only looking at the standards. Then the exoskeleton rather becomes a heavy backpack that the projects have to carry in addition to the customers' load. When your teams start considering processes being rather extra effort than help, it is time again to listen to the projects' voice. Actually, standards and processes are just requirements saying "how" to do the "what" in a way of proven best practices. The latter ("what") often is given by a customer as functional and technical product requirements. So, why not defining the former ("how") also as what they are? As requirements that can be reused in projects and during work united with the product requirements in the same developer tool!
After decades of software development and project organisation I focus on designing, consulting and coaching efficient and agile development processes, also for platform based product development. I live in Germany and I like riding my bicycles and driving my Tesla S85D.
| Erscheinungsdatum | 03.01.2023 |
|---|---|
| Sprache | englisch |
| Maße | 148 x 210 mm |
| Gewicht | 448 g |
| Themenwelt | Mathematik / Informatik ► Informatik |
| Schlagworte | Agile • Anforderungen • Normen • processes • Prozesse • Requirements • Standards |
| ISBN-13 | 9783757503895 / 9783757503895 |
| Zustand | Neuware |
| Informationen gemäß Produktsicherheitsverordnung (GPSR) | |
| Haben Sie eine Frage zum Produkt? |
Mehr entdecken
aus dem Bereich
aus dem Bereich
Buch | Softcover (2024)
BILDNER Verlag
CHF 55,85
Schritt für Schritt einfach erklärt
Buch | Hardcover (2024)
Markt + Technik (Verlag)
CHF 20,90
das Praxishandbuch
Buch | Hardcover (2024)
Markt + Technik Verlag
CHF 27,90
