- WHY CLOUDQA
- ABOUT US
Solve Business Problems by being Agile-Checked! Would you?
Kinkar brain was cluttered, being a technical head he was committed to delivering a project within six months, and after working for five months on a project when they were ready for first UAT, the code refused to float because of incompatibility of browsers.
Had he been Agile-Checked; he could have avoided the last-minute pressure. Seems unbelievable? Let’s run through some facts.
What is Agile Checked?
The two things that drive a business are
Rest all are supporting parameters like skills, logistics, monetary fund’s, etc.
Being a business owner, you do not have much control over “What customers want” as they can demand a “Trip to Moon.”But being a businessman you do have a control on how quickly you present “A Trip To Moon” with Assured Quality! That’s where Agile Manifesto #AgileManifesto comes into the picture.
Being Agile-Checked is all about
To be educated about SCRUM/Agile is easy as many courses and certifications could help you, but all that learning can only be put into practice when you know the “Best Practices” to be followed –
The short Answer is Absolutely YES, and the long answer is let me explain with an example.
Koovy, the head of the development team, is working on the new product that needs to be delivered within six months, they bagged this project because they bid less time against their competitors. So now Sales team has done their job it’s time for the Tech-heads to prove themselves. Let’s compare the three models under different parameters -
|Expected Met Actual|
If we pick Waterfall, model –
It could be risky, as considering we devote 4.5 months to designing, developing and unit testing we would need another months’ time to test and fix the bugs, now if there are any changes to the code or design changes that would not have enough time to set. So, could lead to uncertainty!
If we Pick V-Model –
With flexible requirements, V-model could prove to be a timely affair, as the verification and validation happen in parallel, any change would also need to be reworked. Just for example if there is a change in the login screen, the parallel task of user manual also needs to be redone, and as we have limited time, this model may not prove to be effective.
If we structure the work and divide it into deliverable modules, we could complete the work within the estimated time, would be ready for any surprises and clients could review the work in parallel, helping them to know what’s being cooked and if it matches their expectations.
Well, there are no clear ground rules defined as which methodology should be picked up under which circumstances, however with ever evolving technology it's highly recommended to be adaptive to changes and mark your application/software as Agile-Checked. Would you?