So ito yung canvan board no. So again, yung canvan board ginagamit siya na visual tool para ma-manage at ma-track yung workflow. So yung mga people involved in the software project can see yung progress nung mga task at pwede nilang mabawasan or ma-limit yung mga work in progress para mas maging efficient no? So yung anong tawag dito yung idea behind it nanggaling sa leaniscuss ko ba kanina yung lean methodology? binanggit ko ba dito alam ko nabanggit ko siya dito no maximizing value for the customer ah na merong mas konting waste yun yung lean methodology so dito sa yung canban boardive siya d sa practices from lean and agile especially because yung lean methodology ata is parang from Toyota din if I'm not mistaken okay so kanina na ayan ako lumipat kay na binanggit ko or hindi ko ata nabanggit or nasa isip ko lang yung canband board typically meron lang siyang talagang tatlong rows okay so the to do to do list or the prioritized backlog so ito yung mga task na hindi pa nasisimulan pero kailangang magawa in progress or work in progress ito yung mga tasks that are currently being worked on or yung mga currently ine-execute and then 'yung done or complete. So ibig sabihin tapos na 'to, nagawa na. So kagaya ng sabi ko kanina, bawat task sa canban board is represented by a card. So yung canban board at 'yung mga cards pwede siyang physical or digital. So it moves from left to right across the board. Now, you might be wondering, "Mamahal ko ba tatlo lang yung columns? Bakit po dito may validate?" So yung validate column dito ano siya custom na workflow stage na probably ay specific to the team or project kasi nakita ko lang ong picture na to randomly nung nag-Google search ako no. So yung validate column probably is a column para um ito yung way para ma-mark as done or completed yung task. Kumbaga iche-check muna or ico-confirm if completed na ba talaga technically. Simple show explains Lisa is a project manager in the IT department of a large company. She wants to optim the work processes used in her department that has to handle several projects at the same time. Her friend Max recommends KB, a tried and tested method of agile working. Khban was originally developed to optimized production management. The method controls what, how much and when things are produced. However, these days, Max usually uses Carbon to plan his work, teamwork or projects. Here's how. In the first step, he visualizes the value chain with its different process steps depicted from left to right on a whiteboard, the so-called carbon board. Next, Max divides all upcoming projects into smaller subtasks and attaches these cards to the bun board. The tasks now move across the board from left to right through the various process steps. To make sure that work in progress stays lean, he restricts the number of active tasks per step. Max can thus quickly see where bottles form. No card is allowed to skip a process step. This way existing cards are completed before a new step is begun. Khban emphasizes a team's ability to be self-organized. They hold regular meetings to evaluate and discuss the progress made on the board. The team members are expected to propose their own improvements to identify problems and to rectify these. In this way, KHB creates a culture ofous improvement. Lisa thinks this agile method is brilant. She only needs to apply a few simple principles and she will soon find the task of organization much easier. Another agile framework is the dev ops which was created by Patrick Dosas hindi ko sure iyung pronunciation to combine development and operations. So dev ops attempts to apply agile and lean development principles across the entire supply chain. Ah naglagay ako ng video para mas madaling ma-explain kung ano iyung DevOps. Right from the start, software development comprise two different departments. The development team that develops the plan, designs, and builds the system from scratch and the operation team for testing and implementation of whatever is developed. The operations team gave the development team feedback on any bugs that needed fixing and any rework required. Invariably, the development team would be idle awaiting feedback from the operations team. This undoubtedly extended timelines and delayed the entire software development cycle. There would be instances where the development team moves on to the next project while the operations team continues to provide feedback for the previous code. This meant weeks or even months for the project to be closed and final code to be developed. Now what if the two departments came together and worked in collaboration with each other? What if the wall of confusion was broken? And this is called the DevOps approach. The DevOP symbol resembles an infinity sign suggesting that it is a continuous process of improving efficiency and constant activity. The DevOps approach makes companies adapt faster to updates and development changes. The teams can now deliver quickly and the deployments are more consistent and smooth. Though there may be communication challenges, DevOps manages a streamline flow between the teams and makes the software development processful. The DevOps culture is implemented in several phases with the help of several tools. Let's have a look at these phases. The first phase is the planning phase where the development team puts down a plan keeping in mind the application objectives that are to be delivered to the customer. Once the plan is made, the coding begins. The development team works on the same code and different versions of the code are stored into a repository with the help of tools like get and merged when required. process is called version control. The code is then made executable with tools like Maven and Gradle in the build stage. After the code is successfully built, it is then tested for any bugs or errors. The most popular tool for automation testing is selenium. Once the code is passed several manual and automated tests, we can say that it is ready for deployment and is sent to the operations team. The operations team now deploys the code to the working environment. The most prominent tools used to automate these phases are Ans Docker and Kubernetties. After the deployment, the product is continuously monitored and Nagios is one of the top tools used to automate this phase. The feedback received after this phase is sent back to the planning phase and this is what forms the core of the DevOps life cycle that is the integration phase. Jenkins is the tool that sends the code for building and testing. If the code passes the test, it is sent for deployment and this is referred to as continuous integration. There are many tech giants and organizations that have opted for the DevOps approach. For example, Amazon, Netflix, Walmart, Facebook, and Adobe. Netflix introduced its online streaming service in 2007. In 2014, it was estimated that a downtime for about an hour would cost Netflix $200,000. However, now Netflix can cope with such issues. They opted for DevOps ops in the most fantastic way. Netflix developed a tool called the Siman Army, that continuously created bugs in the environment without affecting the users. This chaos motivated the developers to build a system that does not fall apart when any such thing happens. Today more and more companies lean towards automation with the aim of reducing its delivery time and the gap between its development and operations teams. To attain all of these, there's just one gateway, [Musika] Devops. Ayan. So, ito yyung illustration of the dev ops cycle. So, in-explain na kanina sa video yung ah bawat faces pero ito ulit sila. So the first is yung plan. Um so dito dine-define yung project scope and requirements kung ano yung mga kailangang i-develop kung ano yung system requirements at ano yung sakop nung gagawin nila. And then yung code or develop. So minsan sa ibang figures nakikita siya na code ah tinatawag siya na code minsan naman develop. Pero in this phase, kung ano yung na-define na project scope at yung system requirements, kino-convert into codes. Pero this is done in small increments. And the next phase is build. Take note of the word automate. Automate code. Automate code compilation and integration. After ma-automate yyung compilation and integration, tine-test siya. So again, automated ulit yung testing pero syempre meron pa ring manual testing. And then after that is the operate or release. Again, different sources, different terms iyung mga alternately ginagamit. So in this phase, dine-deploy iyung software to production environments. And then after deployment, nagkakaroon ng last phase monitoring wherein continuously in-observe yung application performance at kapag nakakakita ng issues inaayos nila. So through the dev ops, mas nae-enhance yung customer experience kasi kapag merong changes, mabilis silang nakakapag-react dun sa mga needs or mga gusto nung customers. So through this dahil na kumbaga na naki-cater kung ano 'yung needs nila or mga gusto nila, pwedeng mag-increase din 'yung loyalty of the customers to the brand and therefore increasing market shares as well. So yung mga lean approaches kagaya ng devops, um pwedeng magkaroon ng mas mataas na capacity yung organizations or yung companies to innovate or tama to innovate. kasi nababawasan yung paulit-ulit na ginagawa and um pwedeng mag-shift sila or naa-allow na magkaroon ng shift sa mga mas matataas na ah sa mga um activities which will provide higher business values. And syempre yung mga businesses hindi naman magkakaroon ng pera until magkaroon ng access yung mga customer sa kanila. So through devs nagkakaroon ng mas mabilis na deployment time production platforms at ibig sabihin non mas mabilis din naa-access nung consumers or nung customers yung products. Okay? So yung CICD naman is the continuous integration and continuous deployment. So individually itong mga to ay mga practices ng devops. Okay? So CICD is a set of automation practices used in software development. to streamline the process of integrating, testing and deploying code. So kung babalikan natin yung life cycle kanina, makikita natin 'yun dito ano yung automated na ah integration, testing and deploying. So ito yun no? Okay. Anyway, so CICD ensures that software is developed, tested and released quickly, reliably and with minimal human intervention. So individually explain natin siya no. So yung continuous integration. So dito yung mga developers um yung mga code changes na nagaganap depending dun sa mga changes sa requests or sa mga parang feedback nung customers ini-integrate nila. So dito frequently nagma-merge sila ng mga code changes into a shared repository tapos um nagkakaroon ng automated tests para ma-ensure iyung quality. So continuous integration ensures that code is frequently integrated and tested to catch bugs early. At the same time iyung CD naman or iyung continuous deployment, it automates deployment releasing updates instantly. So ' ba nag-test tayo dun sa continuous integration. So after ma-test, magkakaroon ng mga bagong versions yung software which will be automatically deployed to production at walang manual intervention. So through CICD, um mas mabilis nakakapag-develop at nakakapag-deploy ng software yung mga development teams with fewer errors at mas mataas yung kanilang confidence.