The Business Analysis Doctor - IIBA Certification
The Business Analysis Doctor - IIBA Certification
  • 56
  • 4 803 259
Agile Methodology Explained from a Business Analyst Perspective
Agile Methodology from a Business Analyst's perspective can be pretty complex! In this video, we'll cover the core aspects of Agile basics, we'll answer what is Agile and the various Agile frameworks such as Scrum, eXtrem programming, and SAFe that implement the Agile methodology, and the structure of Agile teams.
Agile is a collection of values and principles despite often being referred to as a Methodology. Discover where the Business Analyst fits into Agile, learn how to define your role in Agile teams, and understand the key responsibilities of an Agile BA. Whether you're new to Agile or looking to enhance your skills, this video provides valuable insights and practical tips to help you succeed.
The Agile framework is a development method in which requirements and solutions evolve in cross-functional teams through a collaborative effort. Agile is used to develop products and execute projects that require flexibility and speed.
SUBSCRIBE for more high-value business analysis content: ua-cam.com/channels/0MgfX0-FkINpUaKFUbGRnw.html
Also, for more details on the day-to-day functions of an Agile Business Analyst, check out this video: ua-cam.com/video/JIqjms832yM/v-deo.html
Below is the outline of the presentation:
What is Agile?
Where did Agile come from?
Waterfall vs Agile
Hybrid Approach
Agile Frameworks
Agile Team Structure
Key Shifts in Agile
Placement of an Agile BA
How to Define Your Role
Common Agile BA Activities
Check out the BA Career Tips Playlist here: ua-cam.com/play/PLLUaS2hPOTH6oU_zrBhoNvXh23EhurIUE.html
#agilemethodology #agile #businessanalyst #businessanalysis #scrum #SAFe #eXtremeprogramming #agileanalyst #agileanalysis #productowner #iiba
In the video we will answer What is Agile? | Agile Methodology | Agile Frameworks - Scrum, Kanban, Lean, XP, Crystal | Edureka, not What is Agile? Mark Shead, but What is Agile? Telusko, and The Role of Business Analysts in Agile Scrum? - Quick, Simple, and Very Important
Simplest Explanation of Agile Methodology Ever! - Business Analyst Training with Agile Methodology Tutorial for Beginners | Jira Tutorial | Agile Methodology Explained. Also Agile Model | Agile Methodology | Scrum Process | Step By Step Practical Approach. Then we will address How the agile methodology really works and What is Agile Methodology | What is Agile | Intellipaat, but not Agile project management methodology explained (with burgers?!). Then What Is Agile Methodology? | Introduction to Agile Methodology in Six Minutes | Simplilearn. Enjoy the video by The Business Analysis Doctor
Переглядів: 951

Відео

Fishbone Diagram EXPLAINED - Root Cause Analysis Techniques
Переглядів 6 тис.4 місяці тому
The Fishbone Diagram for Root Cause Analysis (RCA) is one of the most essential methods of problem-solving and process improvement. In this tutorial, I'll guide you through performing Root Cause Analysis using this powerful Diagram. A fishbone diagram is also known as the Cause-and-effect diagram and the Ishikawa diagram. Business Analysts often use this diagram as an essential input to a compr...
Business Case Example (How to Write a Business Case)
Переглядів 11 тис.7 місяців тому
A business case is often the first project document created by the business analyst. In this video, you will learn how to write a business case that gets approved. A project business case is a pre-project document that is used to justify the approval of a project or initiative. It should be clear, concise, and compelling, and it should outline the benefits of the project, the costs, and the ris...
Sequence Diagram Tutorial and EXAMPLE | UML Diagrams
Переглядів 18 тис.10 місяців тому
A sequence diagram is a Unified Modeling Language (UML) interaction diagram that represents the logic of how objects within a system interact with each other to execute a scenario. This diagram is used in business analysis and software engineering as it can be illustrated at various levels including for a single scenario or an entire system. A key feature of the sequence diagram is that it demo...
Mind Map Tutorial (How to Take Notes for Projects)
Переглядів 4,6 тис.Рік тому
A Mind Map is a powerful visual note-taking tool that stimulates creativity, enhances problem-solving, and encourages holistic thinking. Whether you're a business analyst, project manager, or someone looking to improve your organizational skills, this video tutorial has tips to help you effectively use 5W and 1H, which is one of the most well-known mind mapping techniques for project or busines...
Software Requirement Specification (SRS) Tutorial and EXAMPLE | Functional Requirement Document
Переглядів 23 тис.Рік тому
Software Requirement Specification (SRS) is the number one document that ALL business analysts must master to properly document functional and nonfunctional requirements in software engineering, regardless of whether you are in an Agile or Waterfall environment. This is because most agile documentation is some variation of the different elements that comprise the SRS document. The software requ...
Business Requirement Document (BRD) Tutorial and EXAMPLE
Переглядів 44 тис.Рік тому
Creating a Business Requirement Document (BRD) is a crucial step to ensure your team understands what needs to be delivered when starting a new project or initiative. In this tutorial, I'll show you how to create an effective and comprehensive business requirement document that covers all the essential aspects of your project. First, we'll define what a Business Requirement Document is and why ...
Business Analyst Resume - 6 CRITICAL Tips
Переглядів 6 тис.Рік тому
The right Business Analyst Resume tips can dramatically increase the response to all of the job applications that you’ve submitted for business analyst jobs. In this video, I’m sharing my top 6 Business Analyst Resume Tips for More Interviews! Some of these tips go beyond what to include on your resume. I’m also going to be providing some key resume and job search statistics that will blow your...
Business Analyst Interview Questions and Answers | 35 Essential Questions
Переглядів 60 тис.Рік тому
Practicing business analyst interview questions and answers are a key part of BA interview preparation. In addition to researching the industry and companies you will be interviewing with, being equipped with sample interview questions that are likely to be asked will be your biggest asset toward landing your next business analyst job. In this video, I’ll be sharing my list of the 35 essential ...
Entity Relationship Diagram (ERD) Tutorial and EXAMPLE
Переглядів 42 тис.Рік тому
Entity Relationship Diagram (ERD) Tutorial and EXAMPLE
Requirements Workshop - JAD Session (Example workshop agenda)
Переглядів 12 тис.Рік тому
Requirements Workshop - JAD Session (Example workshop agenda)
BPMN Process Map Tutorial and EXAMPLE
Переглядів 30 тис.Рік тому
BPMN Process Map Tutorial and EXAMPLE
Data Flow Diagram EXAMPLE [How to Create Data Flow Diagrams]
Переглядів 78 тис.Рік тому
Data Flow Diagram EXAMPLE [How to Create Data Flow Diagrams]
How to Perform a SWOT Analysis - Strength, Weakness, Opportunity, Threat
Переглядів 123 тис.2 роки тому
How to Perform a SWOT Analysis - Strength, Weakness, Opportunity, Threat
Use Case Description EXAMPLE [ Use Case Tutorial and Best Practices ]
Переглядів 24 тис.2 роки тому
Use Case Description EXAMPLE [ Use Case Tutorial and Best Practices ]
Use Case Diagram Tutorial and EXAMPLE ( UML Diagram )
Переглядів 17 тис.2 роки тому
Use Case Diagram Tutorial and EXAMPLE ( UML Diagram )
User Stories and Acceptance Criteria EXAMPLE (Agile Story Tutorial)
Переглядів 179 тис.2 роки тому
User Stories and Acceptance Criteria EXAMPLE (Agile Story Tutorial)
BABOK Study Group Clip Solution Evaluation
Переглядів 1,6 тис.2 роки тому
BABOK Study Group Clip Solution Evaluation
Facilitation Skills: The10 Pillars of Effective Facilitation
Переглядів 86 тис.3 роки тому
Facilitation Skills: The10 Pillars of Effective Facilitation
Change Management from a Business Analyst Perspective
Переглядів 8 тис.3 роки тому
Change Management from a Business Analyst Perspective
Risk Management: Top 10 Risks BAs Need to Know About
Переглядів 4,9 тис.3 роки тому
Risk Management: Top 10 Risks BAs Need to Know About
BABOK Learning Loops in 3 Steps
Переглядів 20 тис.3 роки тому
BABOK Learning Loops in 3 Steps
Gap Analysis in 5 Steps.
Переглядів 82 тис.4 роки тому
Gap Analysis in 5 Steps.
Requirements Elicitation: Framework for Requirements Gathering
Переглядів 53 тис.4 роки тому
Requirements Elicitation: Framework for Requirements Gathering
How to Become a Senior Business Analyst in 7 Steps
Переглядів 19 тис.4 роки тому
How to Become a Senior Business Analyst in 7 Steps
BABOK Study - Requirements Analysis and Design Definition
Переглядів 6 тис.4 роки тому
BABOK Study - Requirements Analysis and Design Definition
BABOK Study Group - Strategy Analysis (CBAP, CCBA, or ECBA training)
Переглядів 2,4 тис.4 роки тому
BABOK Study Group - Strategy Analysis (CBAP, CCBA, or ECBA training)
BABOK Study Group Session 4 Clip - Requirements Life Cycle Management
Переглядів 3,7 тис.4 роки тому
BABOK Study Group Session 4 Clip - Requirements Life Cycle Management
On-Demand IIBA Certification Course (CBAP, CCBA, and ECBA)
Переглядів 20 тис.4 роки тому
On-Demand IIBA Certification Course (CBAP, CCBA, and ECBA)
BABOK Study Group - Session 3 Elicitation and Collaboration
Переглядів 4,8 тис.4 роки тому
BABOK Study Group - Session 3 Elicitation and Collaboration

КОМЕНТАРІ

  • @GalaxyCookies76
    @GalaxyCookies76 12 годин тому

    great video need the SRS template

  • @StellaVargas-n1i
    @StellaVargas-n1i День тому

    Thank you for this video! Failing to identify the right stakeholders can indeed lead to missed requirements, rework, and unwanted scope creep. I appreciate these tips and am glad I came across your video!

  • @GabriellaVargass
    @GabriellaVargass День тому

    Your video really helped me a lot! It's great to gain knowledge from an experienced and credible source. I'll keep these seven tips in mind as I delve deeper into understanding what Business Analysis is all about. Thanks!

    • @thebadoc
      @thebadoc 22 години тому

      You are very welcome! I hope the information serves you well!

  • @Bainhthanh-mc7jq
    @Bainhthanh-mc7jq 3 дні тому

    Ađn đl mmm đ

  • @phongyuuki6946
    @phongyuuki6946 3 дні тому

    ,,

  • @ntxhilee3489
    @ntxhilee3489 3 дні тому

    🎉🎉🎉🎉🎉🎉

    • @thebadoc
      @thebadoc 3 дні тому

      Thank you for watching!

  • @KajsiabMuaschannel
    @KajsiabMuaschannel 3 дні тому

    Ua tsaus ok ❤😂❤🎉❤😂

    • @thebadoc
      @thebadoc 3 дні тому

      It sure is! Thank you for watching!

  • @akeemalaro7037
    @akeemalaro7037 7 днів тому

    Thank u very much

    • @thebadoc
      @thebadoc 6 днів тому

      You are most welcome! I hope the information serves you well.

  • @Abhishek-zl5qv
    @Abhishek-zl5qv 8 днів тому

    very good explanation ..thanks

    • @thebadoc
      @thebadoc 8 днів тому

      You are very welcome! Thanks for the feedback!

  • @tokmansite
    @tokmansite 12 днів тому

    Hi there again! I've a comment about the 7th rule presented on "Rules and Best Practices" subsection. I thought that inside the required system there can be a process, which receives some datafrom one external entity, transform this data and send transformed data to another external entity - without the involvement of another process or data store. So, in such case there is no link to a data store or another process. Well, the case above doesn't meet the mentioned rule. Could you, please, comment the issue?

    • @thebadoc
      @thebadoc 10 днів тому

      Great observation. A process sending data to an external entity (or receiving data from it) is still considered a process. So rule number 7 just means that after processing, data must have a destination. It can be sent to another process for further manipulation, be sent as an output to an external entity (still a process), or it can be stored in a data store for later use. I hope that helps!

    • @tokmansite
      @tokmansite 10 днів тому

      Thx much for your help response 🤝

    • @thebadoc
      @thebadoc 9 днів тому

      @@tokmansite You are very welcome!

  • @tokmansite
    @tokmansite 12 днів тому

    Hi, there! Recently I faced with this video and with another source (you could find it by the next text in the google: "Data-flow diagrams (DFDs) model a perspective of the system that is most readily understood by users" (by the way, in that source SSADM notation is used). Well, in that source the way of diagrams and processes numbering differs with yours. They relate the first child diagram (its parent is a context diagram) to lvl 1, but in your video its lvl is 0. Well, the question is "Who is right?" Is there some standard or the primary source of DFD-notation (where the notation was born) where the correct diagrams processes numbering is shown? Thank you much in advance for the answer!

    • @thebadoc
      @thebadoc 12 днів тому

      Hello, DFD was generally originated by Larry Constantine, but there have been several other notations that have been popularized as well, such as Yourdon & DeMarco and Ganes & Sarson. I spoke on these different notations in the earlier part of the video. Also, the DFD examples in this video are using the Ganes & Sarson notation. So to answer your question, the variations between the different levels depends on the notation you are using. You can check out the book Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design by Edward Yourdon. That's one of the first publications that discussed DFDs. I hope that helps!

  • @morranjohansen3108
    @morranjohansen3108 16 днів тому

    Great video. I wish I could have my entire IT team watch this video on Agile. Thanks for all you do for the community.

    • @thebadoc
      @thebadoc 15 днів тому

      Wow, that is so encouraging! And you are very welcome! Also, feel free to share the video with your team 😁

  • @masonsingleton3037
    @masonsingleton3037 16 днів тому

    Amazing overview!!! Now I feel like I can get through an agile project without feeling clueless 😅

    • @tchatter40
      @tchatter40 16 днів тому

      I was in your shoes about 3 months ago...resources like this video were gold for me to find my place on the team!

    • @thebadoc
      @thebadoc 15 днів тому

      Excellent! I'm so glad this video will help you have a better experience as an agile analyst!

    • @thebadoc
      @thebadoc 15 днів тому

      @@tchatter40 Best of luck on your Agile journey. Thanks for watching!

  • @STRAIGHTEE
    @STRAIGHTEE 16 днів тому

    What advise would you give to me as a student who's going to be done with college and start my journey in the Business Analysis world. What should or can i do ? Do i need to rewire my brain 🧠 , change my approach to things as industry and theoretical lives are different? And also what are the things i should focus on to land my first internship.

    • @thebadoc
      @thebadoc 15 днів тому

      Hey, there! I would focus on understanding the day-to-day functions of a business analyst and the necessary skills needed to perform those functions. To land your first internship, you'll need to focus on creating a good BA resume and learning how to answer interview questions for business analysts. I recommend the following playlist to help with all of these recommendations: ua-cam.com/play/PLLUaS2hPOTH6oU_zrBhoNvXh23EhurIUE.html In terms of rewiring your brain, you will definitely want to focus on more of a hands-on learning experience since the BA industry relies heavily on professional experience. You will want to try to get experience executing BA functions such as writing requirements by creating a business requirements document (BRD), software/functional requirements document (SRS/FRD), or user stories in a product backlog. Check out the following playlist for these here: ua-cam.com/play/PLLUaS2hPOTH643f-z8BsgCm_8PxukFHfw.html Also, you will want to get familiar with creating the types of diagrams that BAs use such as use case diagrams, data flow diagrams, and ERDs. I have videos on all of these as well, so I recommend going through them and practicing them in your spare time. You can refer to this playlist to get started: ua-cam.com/play/PLLUaS2hPOTH5mwnpFrYFGQ6Chu2wfGAu7.html Also, for aspiring BAs trying to break into the market, getting your ECBA through IIBA is highly recommended to compensate for the lack of professional experience. When you are ready to look into a course for that, feel free to reach out to me, and we can discuss it further.

    • @poisonapple146
      @poisonapple146 8 днів тому

      I agree a new BA should definitely understand the importance of a BRD and FRD. In one of my first agile projects I realized these documents were basically contracts that defined which features were in-scope or out-of-scope and either won’t be delivered or will be delivered at a later release or for an additional cost. I wish a had a better understanding of this at the beginning of the project.

    • @thebadoc
      @thebadoc 8 днів тому

      @@poisonapple146 Absolutely! Those documents are key. Thanks for weighing in.

  • @thebadoc
    @thebadoc 16 днів тому

    To learn more about navigating Agile as a business analyst, check out our Agile Analysis Certification (AAC) Prep Program here: thebadoc.com/aac. Also, to learn more about the day-to-day functions of an Agile Business Analyst, check out this video: ua-cam.com/video/JIqjms832yM/v-deo.html

  • @awesowm_i_fit
    @awesowm_i_fit 20 днів тому

    Should have made some PPT.

    • @thebadoc
      @thebadoc 20 днів тому

      Thanks for the feedback and for watching!

  • @Maria-fi9hj
    @Maria-fi9hj 23 дні тому

    Literally, thank you so much! This helped me so much to study for an upcoming exam. I'll make sure to remember the theoritical basis you showed us and excel in that exam!

    • @thebadoc
      @thebadoc 23 дні тому

      Excellent! I'm glad I was able to assist you in understanding the concepts for your exam! Let me know how things go on the exam!

  • @Katiapunchh
    @Katiapunchh 23 дні тому

    I finally understood what a business case is. Thank you so much.❤

    • @thebadoc
      @thebadoc 23 дні тому

      You are very welcome! I'm so glad I was able to provide some clarity on the business case concept. I hope the information serves you well.

  • @somachowdhary3647
    @somachowdhary3647 26 днів тому

    Very precise and detail oriented.... Thank you....very helpful!

    • @thebadoc
      @thebadoc 26 днів тому

      You are very welcome! Thanks for the kind words and for watching! I hope it serves you well.

  • @amd9592
    @amd9592 Місяць тому

    Where can I learn more about this for a paper? I need to cite references 😢.

    • @thebadoc
      @thebadoc Місяць тому

      Oh my. Start with The Certified Six Sigma Green Belt Handbook. It talks about Fishbone Digram and Root Cause Analysis pretty in depth.

    • @amd9592
      @amd9592 29 днів тому

      @@thebadoc Thank you so much

  • @user-um2lz5vd2e
    @user-um2lz5vd2e Місяць тому

    🎉

    • @thebadoc
      @thebadoc Місяць тому

      Thanks for watching! Hope you found it useful.

  • @flickhunter8900
    @flickhunter8900 Місяць тому

    Your channel is a gold mine 😂

    • @thebadoc
      @thebadoc Місяць тому

      Excellent! Glad you are finding the content valuable. Thanks for the feedback.

    • @flickhunter8900
      @flickhunter8900 Місяць тому

      @@thebadoc wc.

  • @nickarrigo5540
    @nickarrigo5540 Місяць тому

    great content!

    • @thebadoc
      @thebadoc Місяць тому

      Thank you! Appreciate the feedback!

  • @Juicingwithmaddy
    @Juicingwithmaddy Місяць тому

    Thank you for the tutorial 👏

    • @thebadoc
      @thebadoc Місяць тому

      You are most welcome! I hope the information is useful to you.

  • @limeery6264
    @limeery6264 Місяць тому

    Larry Wheels if he never used steroids. Neat tutorial btw

    • @thebadoc
      @thebadoc Місяць тому

      Ha! I haven't gotten that one before. Glad you enjoyed the video!

  • @lovekushwaha7928
    @lovekushwaha7928 Місяць тому

    🎉

    • @thebadoc
      @thebadoc Місяць тому

      Thank your for watching! Hope you enjoyed the content.

  • @abdullahkhalid9581
    @abdullahkhalid9581 Місяць тому

    Tysm!

    • @thebadoc
      @thebadoc Місяць тому

      You are so welcome! I'm glad you enjoyed the content.

  • @shanabenjamin8945
    @shanabenjamin8945 Місяць тому

    Thank you :) ❤

    • @thebadoc
      @thebadoc Місяць тому

      You are very welcome! Thank you so much for watching!

  • @rodrigo13121962
    @rodrigo13121962 Місяць тому

    Awesome

    • @thebadoc
      @thebadoc Місяць тому

      Glad you enjoyed the content. Thank you for watching!

  • @cmmirikwe
    @cmmirikwe Місяць тому

    is it possible to get a sample?

    • @thebadoc
      @thebadoc Місяць тому

      Hi there! I currently don't have a ready-made sample. If you need help building out a customized resume, we can do this in a coaching session. Check it out here: thebadoc.com/services/ola/services/one-on-one-coaching-session

  • @YavorIvanov-nx4kx
    @YavorIvanov-nx4kx Місяць тому

    Which tool do you use to make the diagrams?

    • @thebadoc
      @thebadoc Місяць тому

      Hey! Thanks for watching! I generally use lucid chart.

  • @marciamason3773
    @marciamason3773 Місяць тому

    Thank you, great information and easy to follow and understand! I'm in an Advanced Accounting Information Systems online class and the book was not easy to comprehend.

    • @thebadoc
      @thebadoc Місяць тому

      You're very welcome! Glad the content resonated with you. I'm not sure of your information systems class covers ERDs, data flow diagrams, and UML diagrams but I have videos on those as well if you are interested. Best of luck with your class!

  • @davehunter6019
    @davehunter6019 Місяць тому

    Very informative video! What questions should be asked to understand the components of a sequence diagram?..

    • @thebadoc
      @thebadoc Місяць тому

      Glad you found it informative! When it comes to the questions to ask, think about it this way. The purpose of a sequence diagram is to visually illustrate various scenarios from a use case description. So the real question would be... which questions would you ask to understand the components of the use case. So when diagraming the sequence diagram, you would focus on understanding the actors, the flow/sequence of the interactions, the starts and end of particular scenarios, any conditions or repetitive events, alternate flows, exceptions, and what information is passed when the actions or events occur. That's pretty high-level but I hope that helps!

  • @swatjoshi577
    @swatjoshi577 Місяць тому

    Thank you so much

    • @thebadoc
      @thebadoc Місяць тому

      You're most welcome! I hope the information serves you well!

  • @user-lk3zh1wg6y
    @user-lk3zh1wg6y Місяць тому

    2/5/2024

    • @thebadoc
      @thebadoc Місяць тому

      Thank you for stopping by and watching the content!

  • @silverletsgo6344
    @silverletsgo6344 Місяць тому

    I wasn't expecting that accent 😂😂😂

    • @thebadoc
      @thebadoc Місяць тому

      Ha! I've heard that before. Curious what type of accent you were expecting.

  • @Aaravkids467
    @Aaravkids467 2 місяці тому

    X5

    • @thebadoc
      @thebadoc 2 місяці тому

      Thank you for watching!

  • @hillview2005
    @hillview2005 2 місяці тому

    Excellent tutorial!

    • @thebadoc
      @thebadoc 2 місяці тому

      Thank you! I'm glad you found it to be helpful.

  • @aneesasheraz5662
    @aneesasheraz5662 2 місяці тому

    If the system generates report and sends it to accounting department for approval in that case is the accounting department external? Its not inputting anything the system just send stuff for approval?

    • @thebadoc
      @thebadoc 2 місяці тому

      Yes, the accounting department would be external. Since it is a destination only, it would be called a sink external. I hope that helps!

  • @aneesasheraz5662
    @aneesasheraz5662 2 місяці тому

    Is bmp and bmpn the same?

    • @thebadoc
      @thebadoc 2 місяці тому

      No. BPM refers to business process management, which is a broader concept that involves activities for optimizing and re-engineering existing business processes. BPMN, on the other hand, is a specific business process modeling notation, with it's own set of rules and standards. BPMN can be used as one of the means to facilitate the execution of BPM. But many notations can be used such as BPMN, UML, or IDEF. I hope that helps.

  • @baruchben-david4196
    @baruchben-david4196 2 місяці тому

    thank you for this clear explanation.

    • @thebadoc
      @thebadoc 2 місяці тому

      My pleasure! I'm glad I was able to clarify the concept for you.

  • @danielchisala1196
    @danielchisala1196 2 місяці тому

    you explain so well sir with great simplicity, thank you very much, looking to more of such content

    • @thebadoc
      @thebadoc 2 місяці тому

      Thanks and you are most welcome! I'm glad I was able to explain the content in a way that resonates with you.

  • @dineshjaiswal9737
    @dineshjaiswal9737 2 місяці тому

    0:13

    • @thebadoc
      @thebadoc 2 місяці тому

      Thank you for watching! I hope the information serves you well!

  • @harip394
    @harip394 2 місяці тому

    ഇദ്ദേഹത്തിന് പാകിസ്ഥാനിലെ പ്രധാനമന്ത്രിയാക്കാൻ അവിടെയുള്ള ജനങ്ങൾ രക്ഷപ്പെടും

    • @thebadoc
      @thebadoc 2 місяці тому

      Sweet! Thank you for tuning in.

  • @bellatissiny403
    @bellatissiny403 2 місяці тому

    Your explanation was amazing! Thank you so much!

    • @thebadoc
      @thebadoc 2 місяці тому

      You're very welcome! And thank you so much for watching. I hope you gained a lot from the information.