1 / 26

Lean UX + DevOps

Lean UX + DevOps. Presented by Vinayak Joglekar, CTO, Synerzip. About the Speaker. Vinayak Joglekar Founder & CTO, Synerzip Hires & Mentors Agile Software Development Teams Over 3 decades of experience in Software Product Development Hands on practitioner of Agile and Lean techniques

clydeb
Download Presentation

Lean UX + DevOps

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Lean UX + DevOps Presented by Vinayak Joglekar, CTO, Synerzip www.synerzip.com

  2. About the Speaker VinayakJoglekar Founder & CTO, Synerzip • Hires & Mentors Agile Software Development Teams • Over 3 decades of experience in Software Product Development • Hands on practitioner of Agile and Lean techniques • Speaker at 2008 Agile Conference in Toronto • Hands on experience in QA automation, DevOps, UX design and CD • Blogs about trends in software development • LinkedinProfile: https://www.linkedin.com/in/vinayak-joglekar-b95329/

  3. Agenda . • Benefits of CD in building an engaging UX • Problems with monolithic architecture • Use of microservices and containers as a solution

  4. Why Do You Do CD? To validate product market fit I can get feedback about my MVP To be in the state of readiness to deploy anytime Fix issues in time To move fast and break things like FB For quicker time to market To validate problem solution fit

  5. Survey- Why Do We Do CD Only 20% to 30% of the deployments are “frequently released” to the customer Only 70% of the times the feedback is sought Then why do we do CD? Because its cool? Why are companies like Facebook or Netflix deploying so frequently?

  6. Does CD Really Help? Not useful for validating problem-solution fit. That’s better served by low-fi prototypes Not useful to validate product-market fit. In fact we need to with-hold deploying changes while monitoring logs to reach conclusion. Very useful to observe changes in user behavior & for building an engaging UX. CD builds the confidence to quickly deploy a feature/change to test a newly formed hypothesis based on validated learning.

  7. 3 Axes of Customer Engagement In expertise (Weeks) Mastery Habit Building On Boarding Discovery In session (Matter of seconds) MVP Investment Trigger Action Reward Beta Launch Expansion In lifecycle (Months and years)

  8. In Session Engagement Concept courtesy: Nir Eyal External Trigger-email, f/b post, ad. Internal Trigger- hunger, boredom Action-Order food, Open f/b Variable reward – see who liked your last f/b post (Some suspense there) Investment- you are tied to f/b because of all the friends made & pictures posted there

  9. Reinforcing Core Loops Embedded trigger takes you to the next level of core loop showing a new call to action E.g. After searching an address on Google maps you not only see the location but icon of a car- taking you to the next level to search for driving directions- improving engagement Reward has the next trigger embedded in it. E.g. top half of next set of recommended movies are visible on Netflix. Makes the user want to scroll again- habit forming.

  10. Engagement in Expertise Building Concept courtesy: Amy Jo Kim

  11. E-commerce False Summits & Core Loop Every time your product solves a problem, it adds a loop to the habit forming core loop. But then customers start facing the next problem. Every summit is a false one How can we satisfy the demand with minimal waiting and delivery problems? How can users get to see other related products or what others like them are buying? Demand forecasting based on trends of what users are buying and liking enables better availability and quicker deliveries thus reducing the time between action of buying and reward of getting to use the product. Purchase history of users can be mined for building buying habits Now that users are able to find the products can they compare and rank those? Recommendation engine makes recommendations based on what users with similar profile are searching and buying. Users post reviews and ratings of products bought by them. Where can users find interesting products? User profile and search history is used to rank the search results leading to the user getting more engaged and habituated to use search more often. Many user profiles get built. Enough data becomes available to mine similar users Search gives interesting results. User repeatedly uses search. User profile gets built , search history gets built.

  12. Google Maps False Summits & Core Loop How can users get a ride or see the reviews of restaurants or see the pictures of places they are visiting? Every time your product solves a problem, it adds a loop to the habit forming core loop. But then customers start facing the next problem. Every summit is a false one How can users plan their itinerary providing for travel time and meeting time on their calendar? Integration with Uber , Zomato and social medial sites for users to post photos of places visited Now that users are able to find the location how can they reach there? Traffic data is used to predict travel time and organize itinerary by integration with Google calendar and travel booking portals How can users get a road map of an address? Driving directions in text as well as on the voice. Options for walking and public transport. GPS data of users gets logged providing traffic data Google maps gives the exact location of the address on the map. Users add their business location and other important pins

  13. User Engagement thru PLC Prototyping tools->Sketch,Invision, Axure, Balsamiq, FluidUI, Yeogurt, Ninjamock, IFTTT, appery.io MVP Testing-> LaunchRock, Kickstarter, Usabilityhub, ICO Rapid Application Development-> Monolith using PHP (Code Ignitor) Ruby on Rails or Node,js Silverlight, Viaduct, Codesmith, Genexus, Webmatrix, Thymeleaf,WebDynrpo Faster,cheaper & better UX by scaling thousands of . SpringBoot, Kafka-reactive micoservices in docker containers orchestrated by Kubernetes, Swarm, Rancher, Consul, Zookeeper, lambda. API (CDC) testing by Pacto, Swagger Better UX by leveraging AI/ ML/NLP BOTs, Spark, R, Storm, Tensorflow, NLTK, UIIMA, IBM Watson,GATE. Big data with Hadoop, Cassandra, Mongo, Neo4j, Redis. Once a user enters in smart contracts on a blockhain using a cryptocurrency – its hard to switch (Investment) Concept courtesy: Amy Jo Kim

  14. Many Hypotheses to Validate Trigger Action Reward Investment Concept courtesy: Amy Jo Kim

  15. Lean Startup Way Build-Measure-Learn loop. Companies who iterate faster do better. Measure & Learn parts of the loop don’t take long. Build is the bottleneck. At times it takes some build cycles to make results measurable. We need the ability to deploy what is built and test it in the market – as frequently as possible.

  16. Problems with Monolithic Architecture • Dev-Test-Production environments need to be differently configured. .

  17. Problems with Monolithic Architecture – contd. Reduced time to build and test Build + test Time Testing Process Build Process Monolithic Application 6 1 Number of changes Build + test Time 6 containerized microservices 6 1 Number of changes

  18. Microservices Facilitate Hypothesis Validation 13 Prioritized backlog Next Hypothesis to validate Continuous integration server kicks a script that compiles and runs unit tests and API contract Validation tests on the containerized microservice Docker files and docker compose files are used to create test containers by the docker demon running in the same container as Jenkins to create and test docker images with the required environment such as nginx, tensorflow, java, play framework, PHP etc. If the tests succeed the images are stored in the Nexus repository. Test containers are deleted after running the tests. Next hypothesis is formed on the basis of the learning The repository consists of the source code as well as dockerfiles/configmaps that control the way the development, test and production clusters are composed by networking/scaling docker containers. Backlog of feature that will validate the hypothesis is created. Expected outcome is spelt out. 12 Repository Repository 2 3 Continuous Delivery Feedback from the market and cosumer research is used to learn why the users behaved the way they did Learning From the Feedback Code 14 Continuous Deployment Dockerfiles+ Configmaps 4 11 Analytics are studied to ascertain how the product has fared in the market. Actual results are compared with expected results Development Commit Stage Compile Basic Tests Kubernetes Container Orchestration If the build fails in production the deployment is rolled back and the previous version stays in production Product Market Validation 1 Container orchestration tools such as Kubernetes launch needed number of container instances using the selected versions of docker images in scheduled sequence networked to communicate with each other. Dev Container w/Jenkins+ +Docker daemon Commit stage: An automated script would run compilation, unit tests, , automated code review, code coverage analysis before the developer pushes the code into the repository. Use of container orchestration tools ensure that instances of new version are launched one by one to replace old versions. If health checks indicate problems with new version the process is reversed. 5 Test Containers QA Ops Roll Back Kubernetes rolling updates DevOps 10 6 9 API Contract validation/unit tests Dockerhub Pods 6 Docker Images v2 Docker Images v3 Docker Images v1 Development Test Production 7 8 Testers use automatically deployed version/build as detailed in step 5. At this stage automated user acceptance tests and performance tests are carried out in addition to few manual tests as required. Bugs if found in this process are assigned to development or the build/version is promoted to production. . Developers run the commit stage scripts finally before promoting the build to the test environment. . API test Stage UAT Manual Test Stage Performance & Security Release test Stage Bugs Reports

  19. Evolution of C/S Functional Team Dev QA Ops PO QA Dev UX PM Ops UX AGILE+DEVOPS 2010 WATERFALL MODEL 1990s AGILE DEVELOPMENT 2000s LEAN UX+AGILE+DEVOPS 2017

  20. THANK YOU!

  21. Subu Sankara VP, Software Services (SFO Bay Area) subu@synerzip.com 510.579.9673 • 21

  22. Synerzip Your trusted outsourcing partner for Agile software product development. • Accelerate the delivery of your product roadmap • Address technology skill gaps • Save at least 50% with offshore software development • Augment your team with optional on-site professionals

  23. Synerzip Clients

  24. Connect with Synerzip facebook.com/Synerzip @Synerzip linkedin.com/company/synerzip

  25. Next Webinar Webinar Presenter: Ron Lichty, Agile Coach & Consultant Software Development Dream Teams Gel as a Team – Become self-organizing, communicative, collaborative; whether co-located or distributed January 25, 2017 at Noon CT

  26. TEXAS | SILICON VALLEY | INDIA

More Related