Get Your Payment Receipt Sample for Quality Assurance with airSlate SignNow

Payment receipt sample for Quality Assurance

of Testament okay cool so translation is already on uh web so we can start um today I'm going to tell you a little bit about my most powerful tool it's create audit the store I was using in all the companies I was working after the Commodore where I created this uh tool and I think will be very useful and uh perspective for every key so today I'm uh streaming on a Channel of Testament it's a great test management tool I would say better than test Trail or x-ray if you know so I'm happy to be here and I was written some article about Kay auditor here I'll share you the link on that and you will be able to go through the um article and use my template okay let's say few words about me so my name is Yuri Mali currently I am CTO also I was on position of head of Pak manager at the key department head of case stream in different International companies and during this 12 years I've got a lot of experience in QA sphere and I like to share my knowledge so I'm leading some classes on impm to a group and Academy so Manuel key course also I've graduated at uh International Management School in Kio on prayer MBA business class so I like to learn some something new and sure I like to share my knowledge so if you will have some question you can easily find me on social networks on Messengers I'll share all the contexts in the end of the presentation okay so let's start we are talking about K audit so what is kod as it's written on a testament blog about Kodi checklist template that is independent evaluation for every software and development process you can use it for any product for any project for any company so it's fully documented performed and planted with objective operations the problem by requirement and acceptance criteria so you will see on this template this file like number of points which you are checking to understand is it compliant or not uh so what it's uh in general it's uh just understanding how is going your process how it's going your project uh maybe it goes pretty well but we don't know if it's good or not we should compare it with something and in this case you will have uh objective 2 for measurement all details and measurement of problems so it's about K audit what is it why do we need it really uh first its problem with application quality maybe you have some bugs on production maybe you have something with uh stability something with uh environments and so on so this will help you to Define these problems because when the project manager of a configuration manager or devops or head of QA okay lead will check it he will easily understand is it working or not maybe you have some software testing process issues for example some box not been fixed in time uh something with uh passing uh from development to QA for example we had interesting situation in a company Commodore where QA spent a lot of time for understanding is it working on you build or not so I introduced processing like uh Handover where I put developer and qkqa to add together and developer during 10-15 minutes shows the QA what it was done in this feature and this is working so this process was fixed and Pa saved a lot of time for this investigation maybe you want to grow and need some unification so you should have a base where you stand on and how will you invite your uh process around all the projects and all the teams for example income company Commodore where I grow this scale it I started with six team six projects and finished with 15 teams and 15 projects so we had it lead on the all projects in company and it was unified for every project maybe want to grow and work better you will find some bottlenecks you will find some problems and solve it and you will have this highlighted so after the uh finding this problem you will start working with that and grow and work will be better generally when company became uh higher and more bigger fire in expertise and when company want to be more mature uh some certification boards required to understand is this process works well so they have a lot of different checking but you can based on this K audit you can easily prepare for such certification or Improvement of maturity of your projects so understand that it's go well and smoothly so if you pair with anything from this list you can easily try to use the skod template okay who could run it so everyone understands that it should be some special auditor some special guy or a tall or expert who will run this Theory so this audit can be internal and external uh really you can build it in your company inside so any QA could run with any manager or team lead some coordinator everyone who related to create sphere can work with that pretty well and the main purpose to catch the project manager to catch guys responsible for all the processes for all the tools and lead this list with them and fill it in after that it will be a planned for improvement so any person who wants to be responsible for other quality could drive it easily even project managers yeah uh what are the main areas for checking I defined five errors first is project management how project goes what processing that and so on second is uh scrum process or we can call it methodology model how it goes my favorite methodology is Scrum agile so we uh in all the companies where I was working SK manager I was uh in detail in the process and I built up proper scrum process when I was working in company locksoft during uh 2010 uh I was working with a project where all the processes were built up by Craig larma one of methodologists and there was ideal scrum because it was set from UBS but from the client side it's the best uh scrum I've seen forever uh in my career that's why I introduced all my knowledge from uh this experience in another companies so sure when we murder it goes properly ing to the scrum process so we will see what should be improved uh third and one of the most important it's quality assurance for sure it's tasting it's create its responsibility for the quality uh we should understand our level of quality you should understand all the details on that and how we should improve with test plan test strategy test cases bug reports and so on everything should be absolutely clear and checked and fourth is configuration managements uh right now it's uh more wide known as devops so development operations and I call it regression management because it's all the configuration of servers of continuous integration systems and so on and the fifth is product management so project management it's like working with project inside these processes and product management is high levels how this product works uh in production how it's uh fill in uh customers needs and does this customer happy with this solution and thus he have Vision or some road map and so on so this part is pretty uh good for understanding our validation if we create proper product uh so that's main areas which will be checked in this kld template what effect should we expect after this audit and first it's for sure transparency transparency Improvement will be the first result because you don't know really is it good is it bad is it grows is it fail will we have some problem or not we doesn't know it at all so this transparency will be really uh improved and you will understand how it's going ing to your list uh what second point is understanding of real situation we don't know how it goes right now but when we complete this audit we understand the current cut so what is uh going right now and we understand that really it's working working and these parts are not good and we should improve it we Define system of Matrix in which we will be measuring our progress and our results so this defines system already created and working so you can just use it by taking and updating that's all a result analysis after the uh completing of audit you will have all the results with all the commands what should be done here does it important or not if it's important we should improve it uh why it's not so important or why it's bad and we discuss it we update understand and continue to grow so after this results we can analyze it and update properly we every audit so this audit leads I recommend personally read it at least once per month because this is pretty good period for uh creation of this uh Improvement plan and defines the growth Zone so we have some zones which we will be improving and after the Improvement we can add some new zones and so on that's why this Grow Zone will be selected ing to the priority Matrix of results so we have a result and we measure it and we have this indefined Matrix and if we are talking about some old projects some complex projects we should be sure that it's not degraded so we measure not the gradation level uh it's uh working as previous and we don't have regress in this process and in this product so all these points will be effect of QA audit how will be presented to this result of Kodi you will have some date after feeding ill in all the details you will have uh this bar chart for one date for example AIDS of ah June and in one month on 8th of June we will see uh the uh some improvements in every Zone and we have total score so we see his bars its project managers grew up from 50 to 73 scrum process was updated from 42 to 75 quality assurance from 35 to 68 configuration to the smallest because it was 61 and up to 63 and product management from 61 to 66 so in general we have overall draws for 21 from 49 to 70. the most interesting thing is that you can run all the results in parallel because a responsible persons who will be defined for every Zone uh separate so uh project manager will be responsible for project management and maybe for scrum process QA lead will be responsible for quality assurance uh devops responsible for configuration management and maybe some product owner will be responsible for product management and we properly discuss it and put some tasks on Improvement we will see the growth in one month and this audit can be run every month and you will see that in a few months you will grow up to 80 85 percentage and so on and sure after that you can extend your audit with some points imported justfully okay so we have here linked to the template and I can move to the uh Testament EO it's received just article so you can read it down in details uh so to check and so on and this thing which I put down it's real template on Google Docs so it's my key audit you can see here everything pretty simple so uh I said that it can be done initially from the scratch just by using this template and no complex formulas no aggregation nothing and we see the uh simple since first part it's our aggregation view so report uh under this we have checklist items for project management and you see here the traceability risk register iteration plan project vacation plan prepared release notes creating and so on you see all these points if we check the number of them is 38 38 points but uh initially when I created the first version of this Kodi it was uh just yes or no comply you see a column C it's compline yes no and if it's comply so we can uh put yes if not no but I understood that different points have different uh well you have different importance on that and different priority and if we uh are talking about product features like ethics it's most important because it should be done properly in jira and risk register is important too and it should be created for every relief but risk register a review with steam regular it's not so important and it can be put through this just needle and for example vocation plan in and procurement plan it's not so important for this broad product because we don't have often some procurement and our vocations can be done without any plan so it's not important so for example project has organized page all links on this page are today and we see that every point every item have different value so different uh importance from one to five the most interesting thing if some point is not applicable you put here zero and I'm not sure if I put zero somewhere in template but you can put it as zero yeah I didn't put it so you can put it like zero and put instead of no and a and Slash a so it's not applicable uh yeah and uh after checking you see this uh result for example yes maybe it's full maybe it's partly and you see the progress so in total uh uh of uh 38 points we have 109 uh total points after uh the calculation we have maximum level it's 108 you can make you can change every item ing to importance in your project but in general it will have total sum and if we check the result of our audit on uh age of June we see that all these values uh have 55 55 points out of 109 and we have here such a simple formula which shows the sum of possible and some of real uh achieved points so we have 55 divided for air 109 and in percentage U we have 50 percent if you have a little more than 50 percent compliant on that and here we have command that risk register should have lean uh some training needs should be gathered from development do we need uh some uh trainings for development team some project specification up to date new info adding so we have new information added to the specification so all the information didn't change maybe it's not up to date and it should be added for example location plan we should discuss is it needed or not maybe it's not so important you put here after the Rune you put it all the com all the commands and see the leaves you even can ask project has an organized page so uh what is this project who is working on that what are the contacts well releases were releases history uh release notes boost box and so on so we you can just ask project manager to put the link here and he will put it here and you can easily you can easily check this uh Point uh by uh opening this link that's it so after the uh in a selection of points which should be added uh which should be improved in one month you see that uh we have Improvement created risk register this register was created an updated weekly yes we started updating weekly we create a meeting and every week we review project risk register we start attributing with the team we created integration plan uh we had integration plans so here nothing changed but we created uh uh training needs gathered from the development team and so on so in total we have uh after the Improvement after the Improvement we updated all the marks to 80. we had 55 in one month we improved it to 80. so 80 points and it shows us 73 percent in total so you can easily do the next and next points so it's regarding project management uh similar scene with scrum model we call it just the scrum model SM and we see that for scrum we have um 38.2 so uh the same value as for uh project manager management but if we check total numbers of that we have 93 so it's less there are not so important point no certain not so important points as uh in project management for example so in total we have smaller uh number General and you can easily update it so we have daily scrum meetings on scrum we have Sprint line in part one meetings we have spring plane part two meetings and regular dreaming regions and so uh but we don't have work on regular base uh Sprint playing part one so we should improve it but if when we improve a regular Sprint playing part one uh yes but we decided that we don't need a Sprint providing to uh with the team in this project so we joined it in that project which all uh spring planning part pump and speed plane in part two and we run it as one and update it you see it's not applicable and it's zero so uh when it's not applicable here we put 0 and it's not counted in uh overall view so person for accept user story identified so product internal dependency well-defined definition of done so all this point you should discuss and understand what uh the main meaning of this and you see that for uh first audit it was uh 39 out of 90 out of 90 because I removed number three and its scrum model with all the detail of scrum and uh so we have a code review for new feature developments we have unit tests we have one time called trees one tasks take no longer than one day but you see that we didn't improve it it's uh not uh we didn't achieve it and so on so you can select some points and choose them for improvement at all quality assurance every user story have user acceptance test they were in development were so not only every user story but in development so in development you should have acceptance test uh in testing it should be done without any doubts so defects have summer it has descriptions preconditional environments operation systems and steps everything in detail how we should write defects defects release version priority components so everything is checked so how we use this Trail how we use the stomat for example and this case is created for each user story uh okay so we didn't create test cases but we create checklist and in one month we started creating test cases that it will be documented for functionality test cases executed in Define test run for industrial and estimate we have test run and we can assign test cases there and it's working some old test runs are typed case strategy or k approach is up to date it should be reviewed because you know that K strategy it can be done once a year and no one takes a look on that we are working at it's okay no problem but really we need to see it uh updated and we should use it so test plan is up to date we should run analysis of bugs from production environment and even from stage why we missed it on stage and so on so in total we have for QA uh 69 points total but 28 points so 28 points here and in total 69 and we have uh compliant uh 24 of them and we can continue on here uh wall changing for the last View yeah so in general we have Improvement for uh 50 core so we improved everything because this K process was pretty easy to fix the update and to start working properly and we see very good result after the review so out of 69 configuration management development environment ready Source control environment radio git breaking model adapted so development in their Branch releases in master Branch continuous integration up and running test environment rates running unit tests and continuous interaction running integration test functional tests so everything which created by develops on environment is listed here some monitoring system creating and work properly so access to every system is Personnel personalized so everything is uh in order and we have uh 64 points uh in 20 are 28 units so it's uh 20 27 points uh in some we will have total possible achievement 64. so we have achievement in uh 39 but after the selection of areas to grow we have 40 so we have Improvement here and the last one is product management we have it product division here we have product roadmap it's confirmed and public maybe it's written somewhere on site like contestamod we have some features and you can see it just on site product robot up to date with a product owner participate in grooming meeting in review meetings he accepts he accept uh user stores created we have a list of five main competitors of the product described in details five main users built in some goals and initiatives initiative described ing to smart and invest mnemonic so we have portal of ideas created in aha so it's another system where we can create this ideas and Link them to all ideas up to date we had created a slain critical errors and we have planned for six months ready so here we have uh 56 points in total uh and 21 row uh so and after first months we had 34 and here we have 37 so not a big Improvement but we have it so in total and uh pretty easy to uh gather all this project management here for a charge uh it's just equals to the top one on audit and we can see all these values from here we can we we are taking just from here and put it on one place for gender because when you see at K audit chart you will see that it took uh data to data uh from this chart uh okay so we just take this uh items to bar chart and we see this overall view so when you run K audit next time you just could audit date so you copy all of this uh columns uh yeah you see there is one more column task link if we create something for improvement because it was not improved here uh yeah forever that's different person who will accept user uh story is identified so when we uh see this uh task that we are going to improve it we can easily put tasks in your task management system for example jira and put link here and you will see that this link uh you can go by this link and see the status or ask a command for example in a few weeks uh does something was done on this case and that's it and you can put here the staff after command so we just copy all of this uh columns and put it uh next after that and uh you put your date for example let's put today's date uh okay yeah 15 of uh uh February and uh you start going through all these points for example you have this yes and put it here yes yes and three five and uh and go through all the rows and with responsible persons put all the commands um and tasks task number yeah and you see that it's completed here and uh we have all these items uh all these numbers here uh you can just easily copy uh this into four rows if I'm not mistaken one two three four and here you have uh a view of the uh uh our two days audit for example you can see it uh 75 General Improvement and when you uh put it here just double click on that and return I remember it was a little bit easier so here it is or not okay let's double check I'm afraid it's another you know here it is uh a little bit confused because I remember that it was much easier to create uh in Excel I just selected this and inserted um diagram here it is configuration but uh with this one yeah [Music] something like this and you have similar diagram I think it can be done somewhere in settings but I don't remember where exactly and you see all this points uh it was a view language [Music] [Music] okay so we have it's pretty similar to this one yeah and it just can be updated uh with not so long on that uh okay so I'll remove everything I was changed so you can see it's pretty easy to do here yeah and we have initial view of this kld template it's shared to everyone you have this link and you can just copy it here copy it to your uh Google doc and update it for your company and for your projects so you can just go with project manager through all these points and for example decides that something is not important for the project something can be changed something can be removed and you can easily just put somewhere project Hazard on us page we don't need organized page on that so we put zero and put an hey and you have this result and it will change in general View so um in total that's it you see how it's working you see how it uh can be done and uh what will be benefit on uh your company and project after usage this gay audit it will show you areas for improvement and you will have some knowledge transferred from one side to another based on that it does customers satisfaction will be increased because it's pretty important uh quality cost and profitability control so as a side effect on that you will see the real cause and mitigation potential risk now you can see that here in uh article on it's written in details and what is benefit uh so uh you can easily uh dig into details to understand so why it's so good and why it's so important to use so everything is here described in detail and you will see uh some uh result in transparency and understanding what is happening on your projects and products that's it that's uh benefits from K Audi and to finish uh with my favorite uh phrase of Winston Churchill if you are going through the hell please go in just keep going and you will win set it from my side all my contacts here I would be happy to answer questions if any with this this uh we discussed with the team that they will share some question from uh you to uh my telegram chat and if everything is okay and if you have some question so I'm ready to see it and to uh answer for your question anyway please join my Facebook please sign to my Instagram and to add to LinkedIn I would be happy to connect with you and uh if you have any questions uh on QA uh sphere on product and so on you can easily to write me down and usually I'm answering in one day not longer so my team said that right now we don't have question uh so let's have a little bit uh time to uh wait maybe there will be some question uh if not you can uh write me uh anytime uh in any messenger so I accept uh I'm accessible in mobile phone in Ukraine uh also WhatsApp Messenger telegram messenger uh Viber and so on uh can you pause TG Channel and yet I can post my GG channel uh it's not my channel it's um sorry I would say that I am not I didn't create it my uh telegram Channel uh I'm on the my uh beginner way of this so you can just write me direct let me uh send you uh my uh telegram because I noticed that uh not every uh one can find me in telegram by mobile phone it's pretty strange but it's true uh so I put it here and uh you will see uh it's from our team so I think it's good idea to create my telegram Channel and to share some interesting points from my professional life from some professional hints and so on so thank you for the idea I think I will create telegram channel in a few weeks or months and sure I will share it okay maybe you have uh more question right now I guess yeah no question okay let's wait a little bit so in general what I would say is that this tool it's uh where uh could we need to use it's nothing complex you just should uh run with your project manager or uh some QA lead and so on and you can easily run suite and to start using it and to update and see how your process will go better and smoother okay my team say that no question right now so I think that a few minutes we can wait and if nothing you can easily find me in social networks and uh in Telegram in Viber in the any Messengers and we have found uh uh it's interesting information great I am happy that it's usable information and I hope you will try to do it to run it to try and we'll get some good results so if you will have any question on implementation onset you just can write me down and I'll help you no problem okay so we have 50 minutes uh run our translation and I think we can finalize with that thank you very much for your time uh that this time on Wednesday you decided to spend with me to see something new and something interesting I hope it will be useful for you and we'll be happy to answer questions on implementation that's it okay um great that uh you join me and uh have a good time and have a effective implementation and growth in your projects in your teams and in your companies get connected see you bye bye