En cours de rédaction
| aculturation | |
| adaptive | vs. predictive |
| agile | |
| agregation | |
| API | |
| granularité | |
| BDM | business process /data management |
| big data | 3V Volume Variété Vélocité |
| BIM | |
| blockchain | |
| bots | |
| BPM | |
| BPM | business process management |
| business Intelligence | |
| buttom up | |
| chabots | |
| cobots | |
| complétion | taux de … au bout du contenu lu intermédiaire à 10 s |
| CRM | |
| crowdsourcing | |
| data vizualisation | |
| datalake | |
| déploiement « on-premise » | |
| design thinking | |
| DFPB | data flow processing business |
| DMP | data management platforme |
| embeded | embarqué (en natif, d’origine) |
| empowerment | be empowered |
| essaimage | |
| flow | |
| flux RSS | |
| from scratch | |
| granularité | |
| ideation sensing | |
| insight | |
| iteration | |
| KPI | |
| lean | |
| machine learning | |
| marketing automation | |
| modelisation | |
| out of the box | |
| outils de listening | |
| PaaS | |
| PERT | |
| Predictive | Development methods exist on a continuum from adaptive to predictive.[28] Agile software development methods lie on the adaptive side of this continuum. One key of adaptive development methods is a « Rolling Wave » approach to schedule planning, which identifies milestones but leaves flexibility in the path to reach them, and also allows for the milestones themselves to change.[29] |
| Processus métiers | |
| Projet cible | |
| Real Time Bidding (RTB) | Ensemble des campagnes médias achetées aux enchères sur les places de marché |
| RGPD | |
| scalabilité | |
| scope | |
| scrum | |
| seo sea sem | |
| slack | |
| sprint | |
| time out | |
| user centric | |
| Adaptive methods focus on adapting quickly to changing realities. When the needs of a project change, an adaptive team changes as well. An adaptive team has difficulty describing exactly what will happen in the future. The further away a date is, the more vague an adaptive method is about what will happen on that date. An adaptive team cannot report exactly what tasks they will do next week, but only which features they plan for next month. When asked about a release six months from now, an adaptive team might be able to report only the mission statement for the release, or a statement of expected value vs. cost. | |
| Predictive methods, in contrast, focus on analysing and planning the future in detail and cater for known risks. In the extremes, a predictive team can report exactly what features and tasks are planned for the entire length of the development process. Predictive methods rely on effective early phase analysis and if this goes very wrong, the project may have difficulty changing direction. Predictive teams often institute a change control board to ensure they consider only the most valuable changes. | |
| Risk analysis can be used to choose between adaptive (agile or value-driven) and predictive (plan-driven) methods.[30] Barry Boehm and Richard Turner suggest that each side of the continuum has its own home ground, as follows:[31] |
SylvieChamorro.com 