« Less - Centré client » : différence entre les versions
De Wiki Agile
Aucun résumé des modifications |
Aucun résumé des modifications |
||
| Ligne 13 : | Ligne 13 : | ||
Traduction : | Traduction : | ||
[[LeSS - Portail Principes]] | |||
In a small single-team product, organizing the team around customer value and being centered on the customer is pretty simple and obvious. But the more teams, the more they become like cogs in the large development machine. Like Charlie Chaplin in Modern Times, their jobs are to turn screws but have no idea how the customer will use the product… or who that customer actually is. In large-scale groups, we see people creating code without really knowing why with respect to the paying customer. | In a small single-team product, organizing the team around customer value and being centered on the customer is pretty simple and obvious. But the more teams, the more they become like cogs in the large development machine. Like Charlie Chaplin in Modern Times, their jobs are to turn screws but have no idea how the customer will use the product… or who that customer actually is. In large-scale groups, we see people creating code without really knowing why with respect to the paying customer. | ||
| Ligne 26 : | Ligne 26 : | ||
* A focus on [https://less.works/less/structure/feature-teams.html| feature teams] that are aligned with creating end-to-end customer-centric features, rather than component teams. | * A focus on [https://less.works/less/structure/feature-teams.html| feature teams] that are aligned with creating end-to-end customer-centric features, rather than component teams. | ||
* L'accent mis sur les [ | * L'accent mis sur les [[LeSS - Equipes Feature]] qui sont alignées pour créer des fonctionnalités orientée client de bout en bout, plutôt que sur des équipes composants | ||
* In very large groups that need to subdivide to be manageable, the [https://less.works/less/less-huge/index.html| LeSS Huge] framework divides teams into Requirement Areas focused on major areas of customer requirements, rather than on architectural subsystems. | * In very large groups that need to subdivide to be manageable, the [https://less.works/less/less-huge/index.html| LeSS Huge] framework divides teams into Requirement Areas focused on major areas of customer requirements, rather than on architectural subsystems. | ||
* Dans de très grands groupes qui ont la nécessité de subdiviser pour être gérable, le cadre de travail [ | * Dans de très grands groupes qui ont la nécessité de subdiviser pour être gérable, le cadre de travail [[LeSS - Portail LeSS Huge|LeSS Huge]] divise les équipes en [[LeSS - Domaines d'exigences]] qui se focalisent sur les domaines majeurs des exigences client, plutôt que sur des sous-systèmes au niveau de l'architecture | ||
* The LeSS Product Owner is a connector of customers/users and teams, rather than an intermediary. | * The LeSS Product Owner is a connector of customers/users and teams, rather than an intermediary. | ||
