 Baiklah. Nama saya Yulin. Saya telah mempunyai beberapa program mentah. Saya telah mempunyai beberapa pertanyaan. Atau beberapa pertanyaan yang sama. Jadi, saya memutuskan untuk menghubungi mereka bersama. Saya akan melakukannya. Jadi, kami tahu apa yang dephops adalah. Tetapi, terutamanya penyelesaian penyelesaian tidak dapat mengahwini kenapa mereka patut berhati-hati dengan dephops. Kenapa mereka tak patut berhati-hati dengan dephops. Dan tidak ada apa-apa yang lain. Tetapi, saya rasa ia tidak berlaku begitu. Kenapa banyak syarikat sangat berhati-hati dengan dephops. Kerana, kami perlukan penyelesaian. Kami perlukan semua orang untuk bekerja untuk perkara yang sama. Kami perlukan semuanya untuk menghubungi. Mereka menghubungi secara mudah. Semua orang sebenarnya tahu sebuah kata-kata perniagaan, perniagaan, perniagaan dan sebagainya. Jika kita tidak faham, jika kita tidak faham bagaimana perniagaan lain, bagaimana perniagaan lain, kita tidak dapat pastikan kita sebenarnya berhati-hati bersama. Okey, mari kita lihat. Apa kita percayakan dephops? Ada banyak deskripsi perniagaan di luar sana. Banyak kata-kata perniagaan di luar sana. Bukan penting. Bagaimana kata-kata perniagaan kita tidak dapat. Bukan penting. Kenapa? Atau apa-apa pun. Jika kita melakukan kerja yang sama, Mereka mungkin ada beberapa keputusan di sini dan di sana. Tapi ada banyak keputusan. Bukan penting pada akhir. Pada akhirnya. Tapi kita perlu faham bahawa kita perlukan semua ini untuk mempunyai perniagaan. Bagaimana? Sebagai perniagaan, kita tidak mempunyai perniagaan. Tidak ada perkara begitu. Kita perlu faham apa perniagaan. Dan bagaimana untuk faham apa perniagaan? Kita perlu faham perniagaan, atau perniagaan. Mereka mungkin ada seorang yang sama. Dan itu sebabnya anda mempunyai dephops. Walaupun anda mempunyai perniagaan, walaupun anda mempunyai perniagaan, perniagaan, apa-apa pun. Bukan penting. Dan semua kita perlu mempunyai perkara yang sama. Semua orang kita perlu mempunyai perniagaan. Jadi bagaimana kita melakukan ini? Semua dephops, walaupun anda mempunyai perniagaan, apa yang kita peduli tentang di perniagaan, sebab semua orang adalah perniagaan di perniagaan. Kita tidak membuat perniagaan, walaupun anda bukan perniagaan, walaupun anda adalah perniagaan perniagaan, kita tidak sangat peduli. Perniagaan perniagaan yang saya menemukan dalam pengalaman saya adalah juga sangat penting. Jadi ini adalah perkara yang kita tidak mungkin mempercayai apabila kita mempercayai perniagaan pekerjaan. Tapi apabila anda mempercayai beberapa tahun di sana, anda melihat bahawa anda memang perlu peduli tentang perniagaan perniagaan. Dan anda perlu peduli tentang perniagaan. Okey, jadi ini adalah beberapa perkara yang anda tidak mungkin mempercayai apabila anda mempercayai perniagaan dan mempercayai perniagaan setiap hari. Jadi ini adalah, awal-awal saya meletakkan PM di depan, tetapi tidak selalu, ia bukan selalu perniagaan perniagaan atau perniagaan perniagaan perniagaan yang mempercayai perniagaan ini. Sebenarnya, apa yang berlaku adalah bahawa anda dapat perniagaan perniagaan perniagaan, jadi anda mempunyai perniagaan perniagaan atau perniagaan perniagaan, dan perkara-perkara yang terkenal bukan perkara-perkara yang terkenal, tetapi yang terkenal ketika anda mempercayai perniagaan adalah perkara-perkara ini. Perniagaan, perniagaan dan perniagaan. Jadi ini adalah apa yang mereka panggil perniagaan perniagaan, jadi jika anda mempercayai perniagaan, maka anda dapat mempercayai perniagaan atau perniagaan perniagaan, dan sebagainya. Sebenarnya, ia cukup mudah. Sebenarnya, apa yang berlaku adalah bahawa mereka akan masuk, mereka akan tanya anda atau, tolong beri saya istimewa. Dan perkara-perkara ini yang mereka akan mempercayai. Kemudian anda akan mulai mempercayai perniagaan, anda akan mulai mempercayai perniagaan perniagaan, anda akan mulai mempercayai perniagaan, atau jika anda mahu semua ini, kemudian anda akan mulai mempercayai perniagaan. Bagaimana anda mempercayai perniagaan dan lupa mengapa dan kemudian anda akan memberikan perniagaan. Baiklah. Ini semua orang yang berbeza-beza yang berlaku, ini sebenarnya dalam. Ini sangat dalam, anda akan mempercayai apa yang menjadikan perniagaan. Apa yang anda perlukan untuk mempercayai, apa yang anda perlukan, bagaimana perniagaan yang saya akan mengambil keadaan yang saya akan perlukan untuk projek ini dan sebagainya. Dan ini adalah perniagaan yang berlaku. Anda perlu mengikuti apa yang pelanggan perlukan, apa yang pelanggan perlukan untuk pelanggan lebih banyak tentang kualiti, apa yang pelanggan perlukan, apakah anda perlu membuat kejadian besar atau anda boleh mempercayai dengan mudah, dengan mudah. Perniagaan perlukan besar, tentu saja untuk perniagaan, kompetiti, apa yang anda perlukan perniagaan, anda tahu. Semua ini adalah perniagaan yang berlaku kepada perniagaan. Dan semua ini juga berlaku dengan perniagaan anda. Kerana perniagaan perniagaan yang berlaku boleh berlaku. Perniagaan yang berlaku untuk perniagaan untuk perniagaan, perniagaan untuk perniagaan, adalah dari semua ini. So, salah satu perkara yang bagus untuk digunakan adalah, apabila anda bercakap tentang perkara ini dengan permainan anda, perniagaan anda dan sebagainya, anda bercakap tentang perkara ini. Memang menggunakan perniagaan. Jadi sebabnya, bagaimana perniagaan yang digunakan untuk perniagaan? Apabila anda melihat perniagaan perniagaan, anda melakukan perniagaan anda. Sebenarnya, apa yang berlaku apabila anda melihat perniagaan perniagaan, anda tidak memiliki perniagaan yang berlaku. Anda tidak memiliki yang anda perlu membuat perniagaan untuk perkara ini, sesuatu seperti itu. Apabila anda memuliki perniagaan, anda akan memiliki perniagaan untuk perkara ini. Dan kadang-kadang perniagaan anda akan dapat mengagumkan perniagaan yang berlaku. Maksudnya, lebih banyak duit dari perniagaan atau lebih banyak duit dari perniagaan. Jika tidak, perkara ini akan menjadi perkara anda dan anda perlu menerima. Untuk memenakkan perkara ini, båatnya berlaku untuk untuk memiliki semua perniagaan. Memiliki segala-galanya yang yang termampu perniagaan perniagaan anda. Memiliki segala-galanya yang perniagaan anda mahu, jadi anda membuat cara-kira antarik dengan perniagaan anda. Jadi ini adalah hal untuk anda berkomunikasi dengan perniagaan anda. Dan anda melakukan berkomunikasi dengan mereka, ataupun pelanggan atau diri anda, anda membuat cara-kira antarik What are the types of things that are required? What exactly does the customer want? What exactly does the user actually need? What would they use? So I prepare here a couple of... Let's see. So this is just one of the open source project that we play Wave, right? So basically I just very quickly just flush out. So we have our users. What are the users? Then we have our user stories. I'll just create the user stories. I'll just list down what the user stories of doing a split build. And then I prepare the techniques based on the user stories. So very simply, and this is not something that you should be doing by yourself, right? When you're doing these things by yourself, basically there's always blind spots. There's always things that you have not considered. That's why we do brainstorming. So we write this all out on post-it notes, usually. We don't do this online. So it's very good if it's everybody is in the same room. You do this on post-it notes so that you can actually move all these cards around. So similar, the blue ones are the user stories. The pink ones, purple ones, or pink ones are the technical stories, so to speak. So you line them up. You know, these are simple ways that you can easily tell if it's... because we read English from left to right. So you can easily tell the sequence of what is going on. So you have your user stories. And then as soon as somebody, if you haven't considered this, write it in another post-it note, take it on. Move the cards around. Similarly, if somebody haven't considered this particular technical bit that we might need. So just move it around, move the cards around. So this is what we do, user story mapping. Okay, so other types of things that you might not know. Okay, so sorry if I'm a bit jumping around. If you have any questions at any point in time, raise your hands if you are unsure of why I'm talking about something. So all these are tools and processes that I've explained. And basically a couple of things that the upside of a business might use the common terminologies, the things that they do that affects us as developers. Okay, so training is basically... customer training is a percentage of customer that is swapped out basically when customer switch to a different, let's say telco, for example, right? Whether it's a telco or a different network whether it's a TV network, your credit cards or it's customer training. So for most business, customer training is a big point in terms of your user base and user base that translates to your profits. So this is also one of the tool sets basically one of the processes that they try to understand what is going on with their customers. So you map out a customer journey. So how do we do that? First thing you look at the entry point of a customer. So the first awareness of the customer the first time the customer come across your brand. So awareness, interest, how does the customer know about us very easily, you know, a lot of the ways you ask how do you know about us, right? This is why. And this is where they map. So from which platform it is which channel did they know about the brand the perception of the brand the risk opportunities and then it comes to decision agreement basically you look at it if you look at a brand often enough if you are happy about the brand and you know your perception of the brand is good enough then you agree to buy in, right? The service delivery how is the customer's feedback in terms of the service delivery how many stars they give you delivery feedback so companies, banks, whatever companies or any business at all, right? They pay a lot of attention in here, right? Delivery to feedback so banks also not just banks, any companies they spend a lot of money going through customer feedback and this here this is where all your data size, machine learning all comes in ready, right? because you're scraping you're going through text analysis of your own customer's feedback or even Twitter Twitter what do you call that? analysis of your your yes, yes, your Twitter impressions all these come in we spend so much money on machine learning just to understand customer behaviour so all these basic voice down to customer behaviour how do companies understand their own user behaviour and relationship strengthening and basically they spend some of the companies they spend months tons of money basically to come out with at the end a business analyst report for example and all this comes down to once they have a report then they start the project and then once the project roll down to software or data scientist or whatever, right? so by understanding these sort of processes that how the business work and how the DevOps actually operate it also helps us understand that we need to be able to align ourselves that this is where the business requirements come in and this is how we can help them understand what is required in terms of the technical aspects so there are different other ways to measure the customer satisfaction right? there's always the ways that do these feedback forms customer chat groups focus groups customer forums ratings these are just different ways to measure customer satisfaction and depending on what your your business analyst comes up with and whatever suggestions comes out of whoever who's consulting with the business and you get different type of projects okay so people think it's when the company makes a fundamental change to the product for the business and the thing is that if a company doesn't pivot most likely it basically in this time of day where technology changes so fast where customers, users are so fickle-minded today is this fair, tomorrow is another one so the companies need to pivot a lot of their business to keep up with changes in society so and what that means for our company product your company product will change so the key point here is that don't be surprised when your project changes because that is actually very very common and that's how your company can survive this is what we call bioframing so for any new product first thing you do, don't dive in that is the worst thing you can actually do design first plan first do your research first so this is one of the first steps mostly for not just for UI but because typically bioframing comes in for UIUX so you you draw this out on paper first because it's just faster, easier to see what exactly that is required for any project this is what we call bioframing so you can actually put your UI on the available space and basically you can showcase to whether your project manager or your software manager your team leader this is what you understand what the user will be doing so this actually maps out all the different functionalities the user will be going through and of course after that you have to this is just very very high level top level after that you have to also design what comes the missing parts basically all the missing parts so these are different types of UML diagrams available so UML is not a new term so been there for about 20, 30 years i guess so UML i think there's right now there's 13 or 14 sorry so there's about 13 or 14 types last like that don't worry last side there's about 13 or 14 types of UML diagrams so do a quick study of these diagrams so all the different UML diagrams actually portray a different segment basic of your entire software system and why do i emphasize on this so much these are the ways you can communicate to your product owner what you are doing what is actually involved in your software because we've talked all these how are you going to communicate your software to your product owner these are the two sets we can use we can utilize to do that and basically in a jauh or any deaf ops situation one of the key things that we always always focus on is communication so when i came out of uni is like seriously i had no problems with the technical parts i have absolute confidence in myself in terms of technical parts the one that i'm not actually confident in is this you know the communications part the office politics part right these are the things that you don't learn in school you basically have to go into workforce figure it out yourself and basically these are the things that i have just touched on is just the tip of the iceberg there's plenty plenty more everybody will end up finding their own ways of how to communicate but just make sure you give it this due diligence don't forget that communication is very important don't just bury yourself in front of your computer and code away so no software is done by just one person any successful software that i've come across all done by teams and teams of people whether it's past, present or now right and that's it thank you very much questions?