Anand Nataraj

Posts Tagged ‘case study’

Always i rejoice days where i worked with full satisfaction. I carry that happy moments along with me & will funny & accommodating.

But I don’t know what happened today. I wanted to be calm, silent & serious. Without me realizing I had a wonderful day at work and i did following tasks today;

• Browsed Cogzidel.in & collected around 20 things which were bugs, suggestions & feedback for improvement.
• Wrote a case-study for Cogzidel Consultancy Services Pvt. Ltd.
• Coordinated with Madurai folks who made me Happy by launching new product for CogzidelTemplates.Com.
• Had a productive meeting with my CTO where we discussed;
  • Speeding delivery of projects.
  • Road map for Sales Improvement.
  • Ideas for new products.
  • Plan for Development for Internal Framework.
• Had meeting with my CFO to discuss about;
  • Status of fun raising.
  • Collected tough cases faced to write case studies.
• Even before writing this blog finished writing one another case study.

This is supposed to be a fulfilling day for anyone and anyone must feel high. But for me everything looks normal and I’m not that excited. I normally go out to watch some movie when I’m sad or very much excited. Today i got a call from my friend to go for a movie which i turned down.

But i feel happy because the new change in me is only taking me in the right path.

At Cogzidel we have never documented all the solutions we solved for every challenge. I wanted to press folks in writing a case study and I wanted to lead from the front and wrote the first case study. There are more to come in future;

Challenge: We as a company didn’t believe on having a separate testing team to test our products. Because the projects were of short duration we always felt a testing team would make sense only after the development team unable to deliver results in spite of doing unit testing. But we were facing lots of challenges because of poor unit testing and many times we get a positive test report from our unit testers and our managers would pass the product to the client believing the words of their subordinates.

Most of the cases client comes back irated as there would be obvious bugs.

Solution: After doing a lot of counseling and giving reprimands nothing worked out as this thing got continued. We finally thought and got a suggestion from out CTO that;

• Every unit tester must be given a target to find bugs in a product and we must have the bug report before sending to the client.
• Team leaders must also be given a specific target for testing.
• Team Managers also given a target on testing.
• Final report goes to the CTO before sending project closure to the client.

Based on the number of bugs and size of the project CTO will analyze will recommend if the project can be sent for project closure.