How to be successful with your digital transformation
Download as PPTX, PDF4 likes158 views
The document discusses strategies for successful digital transformation by focusing on user experience, continuous value generation, and effective team training. It emphasizes the importance of adopting agile methodologies, understanding the value chain, and utilizing design thinking throughout the process. Additionally, it covers tools and techniques for prioritization and continuous delivery to optimize business outcomes.
How to be successful with your digital transformation
- 1. How to be successful with your digital transformation #DigitalBSF
- 2. Presenter slide Alexis Wong Agile expert and project leader Charles Green Director of Thought Leadership Panelists #DigitalBSF
- 3. #DigitalBSF
- 4. WHAT
- 7. #DigitalBSF
- 8. Strategy about incorporating new technologies and transforming processes to reinvent your business and generate new opportunities. Digital transformation #DigitalBSF
- 9. Competition is no longer just between companies from the same industries
- 10. Innovation ”To create something new that makes a difference and generates aggregated value to the client” #DigitalBSF
- 12. Then, what should we do?
- 15. What is really bothering us? What are we asking for? What is frustruating us? In what kind of business are we? Let’s think about it for a few seconds… #DigitalBSF
- 16. You should start with user experience and then procede with the creation of the technology, not the other way around.
- 17. HOW
- 18. Role training to lead the transition You need an effective team with: • Commitment to a continuous generation of value • Executives Innovation Center of Excellence (ICE) #DigitalBSF
- 19. Management role training to accompany the transition 1st day: set the context and establish principles. Understand the current problems: • Understand the mindset Lean-Agile • Apply the principles of Lean-Agile • Experiment with release planning 2nd day: Build knowledge How to execute a 1st release • How to build team culture • Lean-Agile abilities
- 21. Tools
- 22. Playbook 1. Define a purpose 2. Product card (Flag) 3. Enlist DONT’S #DigitalBSF
- 23. Playbook 4. Get to know your neighbours 5. Share the solution
- 24. Look for generalists Be comfortable with ambiguity Leave your ego at the front door 6. Team structure Playbook
- 25. 7. Define a date for the first release Playbook #DigitalBSF
- 26. HOW
- 27. Identifying the value chain RESPONSE TIME PRODUCT COST VALUE DEVELOPMEN T COST RISK Understand the diverse variables Optimize the value chain Economic analysis
- 28. Defining the first transformation team
- 30. Roles
- 32. Design and development cycles The design of the product must evolve along with the product A higher uncertainty requires shorter sprints
- 34. MVP No MVP At the end of a series of iterations, you obtain a funtional version of the final product.
- 35. MVP during the project Evolution over time The first release evolves with time
- 37. The first release evolves with time “It’s focused on people’s experiences with a certain product or service” #DigitalBSF
- 38. Design thinking: 5 steps FIX SPANISH
- 39. Empathy Techniques: • What?, How? Why? • 5 WHY • Interviews
- 40. Interviews Tips: • Don’t ask yes/no questions, nor suggest answers • Promote storytelling • Ask “Why?” • Body language • Use recording devices
- 41. Definition Techniques: • Empathy map • Define the problem playing • How could we?
- 43. Define Personas
- 44. Define Journey
- 46. Ideation • Build on the ideas of others • Forget your serious side, and be creative • A facilitator can help transmit energy to the group • Count using time boxes • Categorize and save all the ideas
- 48. Prototyping
- 49. Prototyping • Use feedback from several prototypes • Identify key variables • Always keep the focus on the user
- 50. Testing (evolution) • Prototype feedback • Observation from every possible angle • Give alternatives to the user • Recycle techniques explained in the previous phases
- 53. Prioritize: The shortest job first (WSJF)
- 55. Prioritize
- 56. Velocity
- 57. Capacity vs Velocity Capacity Velocity Based on expectations or team projections for the future Based on the observation of the results Defined by the team’s availability during the sprint Defined by the historical observation and is a reference for future plans #DigitalBSF
- 59. Digital KPIs Escaling Active use Loyalty Unique visits # Visitors # Registered users Registration growth month to month (MOM) Daily active users (DAU) # Active users # Monthly active users Abandonment rate Rate of repeat users Time spent on the app Satisfaction index Downloads Number of posts Number of likes
- 60. Other tools and techniques •Root cause analysis •Tech talks •Business and design stand- ups •Dependencies map •Open spaces •Team feedback •History breakdown
- 61. HOW Exploring, executing and delivering value
- 62. Be flexible with the scope Predictive process (Waterfall) Adaptive process (Agile) SCOPE SCOPECOST TIME COST TIMEFixed Variable PLAN VALUE #DigitalBSF
- 64. Manage continuous delivery with a Kanban board
- 65. Continuous Delivery Agile culture Cross-functional Empowerment PurposeMastery Autonomy Co-location Client’s commitment Promote non planned collaboration Find the “WHY”
- 66. Continuous Delivery • Visibility when facing setbacks • Rotative faciliator (Agile coach) • SMs, SMEs and some team members • Weekly frequency (30 – 60 min) • Timeboxed with a meeting immediately after • Visibility of the progress, reach and priorities • Rotative faciliator (Agile coach) • POs, SMEs and some stakeholders • Weekly frequency (30 – 60 min) • Timeboxed with a meeting immediately after Communities
- 68. Continuous Integration CODE STORY CHECKIN BUILD INTEGRATION ENVIRONMENTCERTIFICATION ENVIRONMENT
- 69. Continuous Integration WATERFALL INTER-ITERATION WATERFALL INTRA-ITERATION ITERATIONS CROSS FUNCTIONALS
- 70. DevOps This role creates a bridge between development and support to deliver value faster and reliably DEVELOPMENT Creates a shift Adds or modifies features OPERATIONS Creates stability Creates or improves services DevOps IS NOT OPTIONAL
- 71. Continuous Deployment with DevOps CONTINUOUS DEPLOYMENT 4. Automate testing of features and non functional requirements 5. Automate deployment 6. Separate deployment from release 1. Keep development and certification environments the closest possible to production 2. Keep a certification environment that emulates production 3. Deploy certification on each iteration
- 72. Release on demand Final user functionality (every 2 sprints) Security updates (on demand) Backoffice functionalities (monthly) Complete solution (every 3 months)
- 73. Release on demand System validation • User acceptance tests • Non functional requirements final test • Integration tests with other systems • Regulative and standard requirements Documentation • Communication about the release • Final user documentation • Support personnel training • Instalation manuals • Legal approvals, etc. It must be planned
- 74. Don’t forget Celebrate small achievements Good players win matches, good teams win championships!
- 75. EL POR QUÉ WHY
- 76. Our purpose Biologically, the limbic brain controls feelings related to purpose and decision making, not the language.
- 77. Our purpose
- 78. If you work with someone because they can do the job, they’ll work with you for the benefits you provide. If you work with people that believe in what you believe, they will always give you their best. Our purpose