Category Archives: Defects classification

1. Cloud Defects:How the Cloud Professionals can Create the costly defects and the reasons ?

With reference to the booming Cloud Market [refer to some of my videos/blogs] and the Conversions to Cloud by different business organizations; Globally millions of IT professionals were mandated to learn the Cloud technologies to sustain their jobs in IT.

When we talk about these converted IT Professionals, they were forced to move into Cloud due to the sustainability of their job.

At the same time their employers are also enforced by their management to accelerate the cost savings for IT infra.

So how they do the planning for Cloud ?

On top there can be a CTO/CIO plans it to convert into Cloud. And they have the complete knowledge of the infrastructure with reference to their technology being used for business systems.

There will be Cloud Architects, they are responsible to create the Cloud implementation design.

Then the plan and the design is released to the Cloud engineers by allocating the tasks.

In between due to lack of [turn around] time, the Cloud engineers are pressured to create the environments. Here everybody can find one point, the management did not plan the knowledge transfer perfectly to the low level people. Then they can create many costly defects as per their knowledge and experience. So there is no ‘uniformity was followed’ in this case. It need not be a cost effective solution the Cloud Architects or Cloud Engineers have done. And there was no review also done. Once the monthly Cloud bill is arrived they will realize on it. Then they can realize the costly burning/bill happened by comparing to their planned cost saving on Infra. So this way they are enforced to track the resources who created these costly defects.

The following picture has got this kind of analysis. And what are the basic reasons the Architects and Engineers are not able to understand the domain conversion scenarios, when the management plans and release it for implementation.

Here we need to remember, every IT Professional need to realize that one fine day the current size of the resources will not be there in any project due to Cloud and the automation implementation is happening.

So the self matured professional need to realize where they are lacking and step down to learn those from experts, on war footing basis to prove and safeguard their jobs in IT.

You can watch the discussion from:

5. Cloud Defects:What could be the Reasons for traditional networks design defects – towards conversion into VPC ? [A video Discussion]

3. Cloud Defects:What kind of defects/extra work can be created without bootstrapping or IAC followed ?

2. Cloud Defects:What kind of defects can be created without session management in ELB/Cloud ?

4. Cloud Defects:What could be the reasons for Costly defects ? [A video Discussion]

If you want to learn the details, I have discussed in the below video with the relevant coaching on AWS-SAA course also.

Also go through the below blog to know the Cloud and DevOps Roles:

To know the real practices lacking and the root causes towards creating these costly defects, visit the below video based blog. It can show the ways to improve your Cloud projects ROI.

Also visit my video on How to Initiate Cloud Conversion with some best practices:

How the ambiguities can be resolved for defect clarity in a mini project ?

Sometimes many teams in a project get confusion on the test cycles process and the importance of the testing teams, and support to them. This situation might create ambiguities within them.

In this blog I would like to elaborate different operational roles during the test cycles planning/performance [Since the offline requests were received].

In any project, apart from the development [SDLC] teams there are testing teams and the user groups. Sometimes the user groups can have Business Analysts [BAs] also. Now, let us go through the typical process required for test planning and the execution.

Assuming the environment is a mini project, having an independent tester and the BA along with the developer and all are reporting to the one single Project Manager.

The following points can be useful for the healthy testing environment:

  1. The BA collects the user requirements and transfers the requirements to the technical teams. The BA also needs to make sure the relevant tester is in the review meeting to be aware of the latest release requirements.
  2. Once the developers complete the GAP analysis on the new requirements with the existing applications, they can come up with the feasible or allowed requirements for the iteration or the current project.
  3. Then the BA needs to seek user approval to go-ahead with the new release.
  4. Once the approval is given, the Development team needs to share the GAP analysis information along with the approved new requirements to the tester for their clear understanding.
  5. The testers need to understand the requirements and also conduct the presentation on the test scenarios to the BA. If development team attends this session it can benefit them to understand the future defects faster and fixes them ontime.
  6. Once the test scenarios are agreed by the BA, the tester need to keep working on the test planning, test strategy and the approach of the testing. This information need to be shared to the BA and the development team. Once the development team and the testing team agrees on the reviewed contents, the tester need to plan for writing the test cases, data, test cycles and the environment planning.
  7. The test cases and the data need to be reviewed by the BA and the development team needs to be aware on the test coverage.
  8. Once the test execution schedule is arrived, the tester needs to execute the test cases as per their sequence and the schedule. If they find the defect, it needs to be simulated number of times to the developers [as needed]. This way it can give clarity to the developers on the raised defect to understand and fix faster to save the project cycle time or to meet the schedule. The BA need to monitor the defects and their status.
  9. By following the above series of steps the ambiguities can be nullified among the teams for smooth functioning of the project delivery on time.