Méthode agile. En ingénierie logicielle, les pratiques agiles mettent en avant la collaboration entre des équipes auto-organisées et pluridisciplinaires et leurs clients[1]. Elles s'appuient sur l'utilisation d'un cadre méthodologique léger mais suffisant centré sur l'humain et la communication[2]. Elles préconisent une planification adaptative, un développement évolutif, une livraison précoce et une amélioration continue, et elles encouragent des réponses flexibles au changement[3],[4]. Fondements[modifier | modifier le code] Le Manifeste pour le développement agile de logiciels est un texte rédigé aux États-Unis en 2001 par dix-sept experts du développement logiciels.
Les quatre valeurs du manifeste agile ont été déclinées en douze principes afin d'aider opérationnellement les équipes qui souhaitaient les suivre. Historique[modifier | modifier le code] L'article doit être débarrassé d'une partie de son jargon (novembre 2016). Apparition du terme « agile »[modifier | modifier le code] En voici la liste : Designing Digital Strategies (Cartography) As digital products and services come to comprise an increasingly important part of our everyday life, the division between the digital and the physical begins to blur. We can, for instance, see a washing machine on TV, read reviews of it online, purchase it on our phone, and have it installed by our local shop—all without leaving our computer. The sum total of these processes functions as a single, continuous experience. Designers can more prudently frame the experiences they create by incorporating ecosystem thinking into their process. Sign Up for Our Weekly Newsletter Original UX articles Curated Resources Never miss an issue!
In 2011, the newly appointed CEO of Nokia, Stephen Elop, wrote: The battle of devices has now become a war of ecosystems, where ecosystems include not only the hardware and software of the device, but developers, applications, ecommerce, advertising, search… location-based services, unified communications and many other things. The basics Who are our users? Balsamiq. Usability Methods. 10 Essential User Experience Methods. Parallel design. Summary Parallel design is a method where alternative designs, often interface designs, are created by two to four design groups at the same time.
The aim is to assess the different ideas before settling on a single concept for continued development. The design groups work independently of each other, since the goal is to generate as much diversity as possible. Design groups should not discuss their designs with each other until after they have produced their draft design concepts and presented them in a design workshop. The final design may be one of the designs or a combination of designs, taking the best features from each. Although parallel design might at first seem like an expensive approach, since many ideas are generated without implementing them, it is a very cheap way of exploring a range of possible concepts before selecting the probable optimum. Benefits Allows a range of ideas to be generated quickly and cost effectively. Method More Information Nielsen (1993) Next Steps. Explication des 9 diagrammes UML. Diagramme de flux de données. Entity relationship diagram (erd) Diagrammes d'influence.