Downloaded 78 times
Uploaded byXavier Warzee
Innovation games + agile in retail banking
The document discusses an upcoming event on innovation games and agile practices in retail banking. It provides an agenda for workshops focused on understanding current contexts and practices, validating recommendations, and implementing agile best practices. The workshops will use various games and exercises to quickly engage teams from multiple countries in identifying opportunities to reduce time to market and adopt agile. The goal is to help transform organizations and facilitate emerging agile approaches tailored to different contexts.
More Related Content
Similar to Innovation games + agile in retail banking
Innovation games + agile in retail banking
- 1. January 24-‐25, 2013 Igsummit.weebly.com Innova>on Games & Agile in Retail Banking Xavier Warzee, CTO Paris, France xwarzee@palo-‐it.com & Catherine Boudlal, Agile Coach Cédric Mainguy, Marke>ng Specialist Sidi MoHammed Ramdani, Coach
- 2. January 24-‐25, 2013 Igsummit.weebly.com Xavier Warzee 2012: IG Trained Facilitator 2006: Agile Alliance 2011 -‐ 2013: Scrum Day chair 2001: Internet/Web 2013: Scrum Gathering chair applica>ons 2010: French Scrum User 1995: Simula>on/Design Group President of complex systems 2006: Cer>fied Scrum 1989: Object Oriented Master Technologies
- 3. January 24-‐25, 2013 Igsummit.weebly.com Agenda ü Objec>ves of the Retail Bank ü Our approach ü The Workshops J ü Closing remarks
- 4. January 24-‐25, 2013 Igsummit.weebly.com OBJECTIVES OF THE RETAIL BANK
- 5. January 24-‐25, 2013 Igsummit.weebly.com
- 6. January 24-‐25, 2013 Igsummit.weebly.com How to reduce Time
- 7. January 24-‐25, 2013 Igsummit.weebly.com to Market
- 8. January 24-‐25, 2013 Igsummit.weebly.com In Retail Banking IT departments?
- 9. January 24-‐25, 2013 Igsummit.weebly.com
- 10. January 24-‐25, 2013 Igsummit.weebly.com
- 11. January 24-‐25, 2013 Igsummit.weebly.com
- 12. January 24-‐25, 2013 Igsummit.weebly.com Agile “Methods” • Lean – 1987 • Dynamic Systems Development Method (DSDM) -‐ 1995 • eXtreme Programming (XP) – 1996 • Scrum – 1996 • Feature Driven Development (FDD)-‐ 1997 • Agile Manifesto – 2001 • Agile Unified Process -‐ 2002 • Lean Sohware Development – 2003 • Crystal Clear – 2004
- 13. January 24-‐25, 2013 Igsummit.weebly.com
- 14. January 24-‐25, 2013 Igsummit.weebly.com The context Several types of • Itera>ve, Agile, Unified Process, Waterfall, project management … Several types of • Offshore, distributed teams, organiza>ons • IT teams leading Business choices!, … Several types of • BI, Mainframes, Web, Java, … technologies And several countries • Belgium, France, Italy, Luxembourg
- 15. January 24-‐25, 2013 Igsummit.weebly.com
- 16. January 24-‐25, 2013 Igsummit.weebly.com Maarten Volders Cédric Catherine Xavier “Hammed”
- 17. January 24-‐25, 2013 Igsummit.weebly.com Why Play Games? To collect a large number of informa9on in a short period of >me To engage teams to ease the next step: start a transforma9on! To facilitate the emergence of new agile organiza>ons for various contexts, countries, cultures, maturi>es, …
- 18. January 24-‐25, 2013 Igsummit.weebly.com OUR APPROACH
- 19. January 24-‐25, 2013 Igsummit.weebly.com Interviews? Image credit: auremar / 123RF Banque d'images
- 20. January 24-‐25, 2013 Igsummit.weebly.com
- 21. January 24-‐25, 2013 Igsummit.weebly.com
- 22. January 24-‐25, 2013 Igsummit.weebly.com
- 23. January 24-‐25, 2013 Igsummit.weebly.com
- 24. January 24-‐25, 2013 Igsummit.weebly.com
- 25. January 24-‐25, 2013 Igsummit.weebly.com
- 26. January 24-‐25, 2013 Igsummit.weebly.com
- 27. January 24-‐25, 2013 Igsummit.weebly.com Selected Games Graphic Gameplan SWOT to collect $100 Test to to Implement in an Current Contexts 20/20 Vision to Implement in an IT IT department: and Prac9ces Validate and select department: recommenda9ons To define a And focus on issues To put priori9es on roadmap to adopt and expecta9ons recommenda9ons prac9ces
- 28. January 24-‐25, 2013 Igsummit.weebly.com The “corporate” presenta>on Interviews Workshop 1 Agile Best Current level of Agile Prac9ces Guide Current Contexts and Prac9ces Recommenda9ons Workshop 2 Workshop 3 Valida9on and selec9on of Implementa9on Implementa9on in an IT Implementa9on Guide recommenda9ons Guide V0 department V1
- 29. January 24-‐25, 2013 Igsummit.weebly.com Agile Methods Guide Interviews results Current Prac>ces & Recommenda>ons To adopt Agile Prac>ces Tables of Law J Implementa>on Guides
- 30. January 24-‐25, 2013 Igsummit.weebly.com Current Contexts and Prac9ces WORKSHOP 1
- 31. January 24-‐25, 2013 Igsummit.weebly.com Let’s Play a SWOT
- 32. January 24-‐25, 2013 Igsummit.weebly.com Collec>ng current development prac>ces People quickly engaged 7 Teams from 4 countries
- 33. January 24-‐25, 2013 Igsummit.weebly.com Each team lists its current prac>ces (here, slides of remote teams)
- 34. January 24-‐25, 2013 Igsummit.weebly.com SWOT Mechanics • Teams from different departments from 4 countries listed their current development prac>ces on Post-‐its. • Then, each team shared their Post-‐its on the SWOT board explaining the why? • Goal: Quickly find current issues and map current dev process really used!
- 35. January 24-‐25, 2013 Igsummit.weebly.com SWOT Our observa>ons • Teams felt engaged • Quickly they used walls and Post-‐its • Lot of discussions during the prac>ces collec>on • Real contexts emerged through explana>ons when Post-‐its were added on the SWOT board • Discussions between teams from different organiza>ons give us context to collected prac>ces
- 36. January 24-‐25, 2013 Igsummit.weebly.com SWOT
- 37. January 24-‐25, 2013 Igsummit.weebly.com Strength Weaknesses Office space organiza9on • Project Planning Office space organiza9on • Specialized teams • Dedicated mee>ng rooms • Es>ma>on • Communica>on tools (visual, chats, mails, • Project follow up • Open space • Transversal teams RSE, etc.) • Project commiuees • Classical office • Domain teams • Open Space • Architecture commiuees • Remote open space Requirements Management Project Infrastructure • Release configura>on management • Development Env. • War room (Dev., Testers, Business) • Remote classical office • Func>onal Analysis • Internal tes>ng plasorm • Tasks priori>es defini>on • Dedicated mee>ng rooms • GUI mock ups • Valida>on tes>ng plasorm Specifica9ons Management • Communica>on (camera, chats, • Requirements traceability • Con>nuous integra>on plasorm • UML specifica>ons • Pre-‐produc>on plasorm • UML -‐ Uses Cases / Actors mails, RSE, etc.) Development • Pilot plasorm • Func>onal Analysis Project Infrastructure • Build • Documenta>on server • Technical Analysis Project Organiza9on • GUI mock ups • Development Env. • Unit tes>ng • Features development splitng • Requirements traceability(QC) • Pre-‐produc>on plasorm • Coding norms and standards • Itera>ve development Development • Pilot plasorm Project Management • Incremental development • Unit Tests Project management • Anomalies management • Produc>on plasorm • Daily tasks management • MCIP method V&V tes9ng Project organiza9on • Scrum usage • Valida>on tes>ng • Ver>cal teams Opportuni9es Threat Office space organiza9on • Coding norms and standards Office space organiza9on • Features development splitng • Open Space Tests V&V • Remote classical office Project Management • Dedicated mee>ng rooms • Integra>on tes>ng Project Infrastructure • External access to documents Project Infrastructure • Verifica>on tes>ng • Con>nuous integra>on plasorm repositories • Con>nuous integra>on plasorm • Performance tes>ng • Pre-‐produc>on plasorm • Wiki Server Project Management • Pilot plasorm Project Organiza9on • Quality Insurance Plan • Produc>on plasorm • Specialized team • Es>ma>on Project Organiza9on • Features development splitng • Architecture Commiuees • Ver>cal teams Requirements Management • Project Debriefing • Specialized teams • Requirements traceability • War room (Dev., Testers, Business) • Requirements documenta>on • Tasks priori>es management • Quality Center U>liza>on Indicators Development • Project status • Unit tes>ng • Quality • Technical documenta>on / Wiki • Workload Lot of feedback provided • Costs
- 38. January 24-‐25, 2013 Igsummit.weebly.com SWOT ANALYSIS & RECOMMENDATIONS
- 39. January 24-‐25, 2013 Igsummit.weebly.com SWOT analysis
- 40. January 24-‐25, 2013 Igsummit.weebly.com SWOT analysis
- 41. January 24-‐25, 2013 Igsummit.weebly.com Recommenda>ons
- 42. January 24-‐25, 2013 Igsummit.weebly.com Recommenda>ons
- 43. January 24-‐25, 2013 Igsummit.weebly.com Valida9on and selec9on of recommenda9ons WORKSHOP 2
- 44. January 24-‐25, 2013 Igsummit.weebly.com
- 45. January 24-‐25, 2013 Igsummit.weebly.com 20/20 Vision Mechanics • Write your feedbacks about prac>ces on Post-‐its for 5mn • One feedback per Post-‐it • Consider important prac>ces according to your context • Goal : • Collect your feedbacks to improve your agile adop>on roadmap • Types of feedbacks : • Instant feedbacks • Easy versus difficult to implement in your context • Great versus poor business value • Relevance level in your context : low, medium, high • …
- 46. January 24-‐25, 2013 Igsummit.weebly.com 20/20 Vision Our observa>ons • We avoid self-‐censorship – all members share their cards • People keep a global view by arguing on priori>es with all teams • We put a large amount of informa9on in context • These informa>on in context helped to define a common path to be agile taking into account organiza>ons, skills, maturity in terms of Agile prac>ces, …
- 47. January 24-‐25, 2013 Igsummit.weebly.com 20/20 Vision
- 48. January 24-‐25, 2013 Igsummit.weebly.com A common path to be Agile!? Tables of laws J
- 49. January 24-‐25, 2013 Igsummit.weebly.com Result of the workshops
- 50. January 24-‐25, 2013 Igsummit.weebly.com Maps of the Agile World hup://guide.agilealliance.org/subway.html
- 51. January 24-‐25, 2013 Igsummit.weebly.com Implementa9on in an IT department WORKSHOP 3 : FIND A PATH TO AGILITY FOR A GIVEN DEPARTMENT
- 52. January 24-‐25, 2013 Igsummit.weebly.com $100 Test Game Mechanics • A team assigns rela>ve value to a list of dev prac>ces selected in the previous workshop by spending an imaginary $100 together. • The selec>on must be done as a team and choices must be explained
- 53. January 24-‐25, 2013 Igsummit.weebly.com $100 Test Game Our observa>ons • By using the concept of cash, people are more focused and more engaged than with an arbitrary point or ranking system • Ease the transi9on by involving the team as a whole and by deciding the priori>es in collabora>on
- 54. January 24-‐25, 2013 Igsummit.weebly.com $100 Test Game
- 55. $100 January 24-‐25, 2013 Igsummit.weebly.com Topic Pra9ques $ Why? Constitution de - l'Equipe Autonome et Pluridisciplinaire 10 Efficacité et rapidité Gestion des - spécifications Use case estimé -‐ valeur métier, Priorité,Critères d'acceptation, 8 Priorisation des Use cases Taille rentre dans 1 sprint, Valeurs de tests fournies Définition du contenu d'un incrément -‐ Story Map 3 Représentant métier et technique ensemble dès le démarrage du 7 Validité de la solution projet Planning d'une itération 5 Planning de release sur la base de la vélocité 2 Réunion quotidienne 7 Transparence et suivi des risques Maintenance d'un tableau des tâches destiné aux membre de 2 l'équipe Démonstration 5 Visibilité avancement Rétrospective 5 Capitalisation - Amélioration Backlog grooming -‐ Définition des Efforts, Risque des use cases, 6 revue des priorités, Gestion du changement Recette en cours et fin d'itération -‐ Vérif & Valid 4 Management Visuel -‐ Mur d'information 3 Définition de "Fini" 4 Le code - Gestion de configuration 2 Tests unitaires 2 Normes et standards de code 2 Refactoring 2 Utilisation de l'Intégration continue -‐ Build automatisé 8 Fluidité - Stabilité - Sécurité Tests fonctionnels automatisés 2 Vérification sur la plateforme de vérification 4 Indicateurs - Burn Down Chart 4 Vélocité 4
- 56. January 24-‐25, 2013 Igsummit.weebly.com Graphic Gameplan Mechanics • From the result of the $100 test game, take most important prac>ces. • Find problems to implement them • Propose steps to achieve implementa>on
- 57. January 24-‐25, 2013 Igsummit.weebly.com Graphic Gameplan Our observa>ons • The team took into account dependencies to adopt the prac>ces • The team acted in collabora>on easing next step to implement prac>ces • First roadmap defined as a team J
- 58. January 24-‐25, 2013 Igsummit.weebly.com Graphic Gameplan
- 59. January 24-‐25, 2013 Graphic Gameplan Igsummit.weebly.com Pra9ques Etape 3 $ retenues Problème(s) iden9fié(s) ? Etape 1 Etape 2 10 Equipe autonome et -‐ Pb organisa>onnel: cloisonnement par -‐ Implica>on du mé>er -‐ Forma>ons sur les pluridisciplinaire discipline -‐ Iden>fier un expert par disciplines -‐ Ou>llage pour être autonome (plateforme discipline dans chaque équipe -‐ Forma>on méthodes de receues) (mé>er, archi, dev, test, agile -‐ Isola>on des perturba>ons extérieures packaging) -‐ Forma>on par rôle Agile iden>fié 8 Use case es>més Implica>on mé>er 8 Intégra>on con>nue -‐ Coûts de l’infrastructure Déployer Former U>liser -‐ Compétences -‐ Disponibilité des plateformes dans les CSB 7 Mé>er et IT ensemble au Informa>on sur le démarrage de l’avant projet Iden>fier un représentant démarrage du projet mé>er et IT dès le démarrage 7 Réunions quo>diennes -‐ Equipe dédiée +++ Organisa>on systéma>que -‐ Espace disponible pour tenir les réunions quo>dienne -‐ Espace d’affichage -‐ Moyen de communica>on (infra et ou>l projet) 6 Backlog grooming Implica>on mé>er et de toute l’équipe Mé>er dédié travaille sur Planifier ces tâches de l’affinage du backlog revues du backlog dans les L’équipe es>me au fur et à itéra>ons mesure 5 Planning des itéra>ons A intégrer dans la méthode de Faire un guide conduite de projet: formaliser l’étape 5 Démonstra>on Organisa>on systéma>que 5 Rétrospec>ve Organisa>on systéma>que
- 60. January 24-‐25, 2013 Igsummit.weebly.com WORKSHOPS PLAYED BY AN IT DEPARTMENT
- 61. January 24-‐25, 2013 Igsummit.weebly.com CHECK THE CURRENT PRACTICES: SWOT AT THE LEVEL OF THE IT DEPARTMENT
- 62. January 24-‐25, 2013 Igsummit.weebly.com Current Dev Prac>ces Organisa9on de Organisa9on Ges9ons des Infrastructure Dev Tests Ges9on de projet Indicateurs l’espace Projet specs Bureaux classiques UML – Use cases Ges>on des Plan assurance Indicateurs Env. d’intégra>on distants Equipes en silo -‐ RSM anomalies ALM Tests Unitaires qualité avancement Sépara>on UML – Diag de Concep>on Env. Receue MOA / MOE / classes détaillée Tests Indicateurs MOA Sous-‐traitants Méthode MCIP RSM Spec. Papier d’intégra>on Planifica>on qualités Env. receue Lo>ssement des Traçabilité des Tests de Indicateurs de interne développements exigences Doc technique performance Chiffrage charge Modèle du datawarehouse Env. de dans PowerAMC -‐ Dossier Réunions de Indicateurs de développement RSM d’exploita>on valida>on coûts Dossier Réunions de d’installa>on projet Comités de projet Débriefe de projet Suivi d’avancement Ges>on et suivi des versions
- 63. January 24-‐25, 2013 Igsummit.weebly.com WORKSHOP 1: SWOT
- 64. January 24-‐25, 2013 Igsummit.weebly.com Workshop 1 Agile level adop>on
- 65. January 24-‐25, 2013 Igsummit.weebly.com Workshop 2 results Agile Prac>ces to adopt
- 66. $100 January 24-‐25, 2013 Igsummit.weebly.com Topic Pra9ques $ Why? Constitution de - l'Equipe Autonome et Pluridisciplinaire 10 Efficacité et rapidité Gestion des - spécifications Use case estimé -‐ valeur métier, Priorité,Critères d'acceptation, 8 Priorisation des Use cases Taille rentre dans 1 sprint, Valeurs de tests fournies Définition du contenu d'un incrément -‐ Story Map 3 Représentant métier et technique ensemble dès le démarrage du 7 Validité de la solution projet Planning d'une itération 5 Planning de release sur la base de la vélocité 2 Réunion quotidienne 7 Transparence et suivi des risques Maintenance d'un tableau des tâches destiné aux membre de 2 l'équipe Démonstration 5 Visibilité avancement Rétrospective 5 Capitalisation - Amélioration Backlog grooming -‐ Définition des Efforts, Risque des use cases, 6 revue des priorités, Gestion du changement Recette en cours et fin d'itération -‐ Vérif & Valid 4 Management Visuel -‐ Mur d'information 3 Définition de "Fini" 4 Le code - Gestion de configuration 2 Tests unitaires 2 Normes et standards de code 2 Refactoring 2 Utilisation de l'Intégration continue -‐ Build automatisé 8 Fluidité - Stabilité - Sécurité Tests fonctionnels automatisés 2 Vérification sur la plateforme de vérification 4 Indicateurs - Burn Down Chart 4 Vélocité 4
- 67. January 24-‐25, 2013 Graphic Gameplan Igsummit.weebly.com Pra9ques Etape 3 $ retenues Problème(s) iden9fié(s) ? Etape 1 Etape 2 10 Equipe autonome et -‐ Pb organisa>onnel: cloisonnement par -‐ Implica>on du mé>er -‐ Forma>ons sur les pluridisciplinaire discipline -‐ Iden>fier un expert par disciplines -‐ Ou>llage pour être autonome (plateforme discipline dans chaque équipe -‐ Forma>on méthodes de receues) (mé>er, archi, dev, test, agile -‐ Isola>on des perturba>ons extérieures packaging) -‐ Forma>on par rôle Agile iden>fié 8 Use case es>més Implica>on mé>er 8 Intégra>on con>nue -‐ Coûts de l’infrastructure Déployer Former U>liser -‐ Compétences -‐ Disponibilité des plateformes dans les CSB 7 Mé>er et IT ensemble au Informa>on sur le démarrage de l’avant projet Iden>fier un représentant démarrage du projet mé>er et IT dès le démarrage 7 Réunions quo>diennes -‐ Equipe dédiée +++ Organisa>on systéma>que -‐ Espace disponible pour tenir les réunions quo>dienne -‐ Espace d’affichage -‐ Moyen de communica>on (infra et ou>l projet) 6 Backlog grooming Implica>on mé>er et de toute l’équipe Mé>er dédié travaille sur Planifier ces tâches de l’affinage du backlog revues du backlog dans les L’équipe es>me au fur et à itéra>ons mesure 5 Planning des itéra>ons A intégrer dans la méthode de Faire un guide conduite de projet: formaliser l’étape 5 Démonstra>on Organisa>on systéma>que 5 Rétrospec>ve Organisa>on systéma>que
- 68. Closing remarks January 24-‐25, 2013 Igsummit.weebly.com Successful and Rich Assessment in Collabora9on Posi>ve Percep>on of Change through Engagement Efficient approach for organiza>ons to find their path to be Agile All people highly engaged during a short period with great results Time and expenses earning Value & ROI maximiza9on
- 69. January 24-‐25, 2013 Igsummit.weebly.com
- 70. January 24-‐25, 2013 Igsummit.weebly.com
- 71. January 24-‐25, 2013 Igsummit.weebly.com Image credit: flippo / 123RF Banque d'images
- 72. January 24-‐25, 2013 Igsummit.weebly.com Images Credits • Slides 13, 14, 18: Play>me, the movie J • Slide 17 : Components to deliver: an Agile PMO – hup://foxhedgeltd.com/blog/page/2/ • Slide 19 : Europe – hup://ansionnachfionn.com/tag/an-‐bheilg-‐belgium/ • Slide 21 : About bootstrapping, entrepreneurship & personal development – hup://blog.eerlings.com/index.php/2012/08/ • Others slides : mostly pictures from – hup://123rf.com – And from workshops given by Palo IT