Difference between Agile model and V model | LTS Group

Hello, guys! Welcome to our LTS Group channel. Our channel is aimed at sharing information and knowledge about Quality Assurance, Testing, and Data Annotation for AI development.
In this video, I'm going to talk about the difference between Agile model and V model. Let's find out what't the difference between Agile and V model!
⭕️Subscribe to our channel
bit.ly/31xPlDE
------------------------------------------------------------------------------------------------
🙌Watch more helpful videos!
[An Ultimate guide for AI Data labeling tool]
●5 Important Data Annotation Tool Features: bit.ly/2QxbXOB
●Should we buy or build the annotation tools?: bit.ly/3brURv0
[5 essentials of AI training data labeling work]
●Data Quality: bit.ly/2EjJvwY
●Scale: bit.ly/34rM1fh
[What makes a WOW Mobile App]
●Understanding Differences: bit.ly/2ErmgAW
●Choosing the right devices: bit.ly/3howEYH
●Ensuring Usability (UI/UX): bit.ly/2Qjg6W5
●Ensuring stability (No crash): bit.ly/2QlBQ3u
●Applying Automation smartly: bit.ly/3aRMed1
------------------------------------------------------------------------------
☎️contact us
●LTS Group Homepage: ltsgroup.tech/
●LTS Group Linkedin: / lts-group-vietnam
●LTS Group Facebook: / ltsgroupvietnam
#Agilemodel #Vmodel #LTSGroup

[@Guesswhokk]

1:11 I dispute this, you are look at "testing" as a 'process' and not as an end output.
1 - Remember the 3 classic conundrum for any given projects: "time" , "quality" and "cost"
2 - Agile is best suited to small org, when innovation / risks level are unknown and has not reach it "technological ceiling yet" (so no reference) and thus "time" and "cost" are harder to gauge as it need "iterative designs" (include testing) to achieve quality products, less appropriate in a large org with multi departments when traceability become difficult to manage.
e.g Intel chip design, This is why moores law cannot be adhered to using Agile.
3 - Vee is used in large systems if Agile couldn't handle it, when risks & innovation are "pre-determined" (but in real world risk is usually unknown) and thus "time, cost & quality" have clearer outcome if risks is pre-determined, but it only as good as your "risk prediction" and if large number of high risks issues start comes up during development, it will seriously mess up on project planning like protected cost, time and quality. This is why Vee is not often used especially the product want to achieve not innovation.
e.g. NASA TRL systems, using design iteration from good ole knowledge base aluminium and rocket technology borrowed from decades ago like space shuttle, rather than Space X using clean-slate material like Stainless for rocketry.
It possible for both system to exist in engineering capacity when an organisation is big enough to adopt both, when Agile can assign to "conceptual phase" once found the right rough mix for product launch, then it can be transfer to Vee in the "development phase" as NPD milestones"
It rare to find a company willing to merge Vee and Agile and doing it "effectively", usually out of necessity when limited resource was a factor (not based on size of the company), because it not easily understood or implement, because this mixed structure can be very specific to the product.
But once it found the right mix, it can work far better and more efficient than either of the two stock method. e.g. scrum process

[@thanhluudang4877]

is it true that 5 sprints in Agile be equal to 1 cycle of V model ? in reality, a project can have 10 cycles of V model from beginning til the end. can we say that 1 cycle of V model be equal to 1 sprint ?

[@maheshbabu637]

hi, is V model and Agile applicable for same project at a time?

[@danyeo1490]

I disagree with the majority of this video.

[@chandpriyankara]

This is wrong