What are the cardinal sins in Software Development Life Cycle (SDLC)?
Rule 1: Never forget to support and maintain your existing active products. The first priority should go for supporting your existing product over the new committed release. Supporting your existing products should have much importance even though your company strategy is to move to the new product and technology. If you cannot service and support your existing products, how would you expect the same customer to buy your new product and use it.
Rule 2: Never create any regression bugs between the old version and the new versions. Customers remember and never forgets the bugs that you have introduced in the new version.
Rule 3: Never forget to merge the hot-fixes or bug-fixes or patches into the next immediate main release. Customers do not like to face the same issue that they faced in the previous version in the new version also.
Rule 4: Never add additional features without the permission of Product Owner or Product Manager. Never over complicate the code base to create a fancy or cool feature. Oftentimes, such code is overworked immediately after the release and not removed. It is easy to add code, but very difficult to remove code as you never know if any customer is using that feature. Remember that you can never release a software bug free product in your life. This is mainly due to the fact that many software products are used in various other use cases other than it is designed for. So write simple code which is easy to scale and maintain.
All the above mentioned rules are very important to have a successful product satisfaction for the customer. Do always remember to view or empathize from the view of your customer.
Rule 1: Never forget to support and maintain your existing active products. The first priority should go for supporting your existing product over the new committed release. Supporting your existing products should have much importance even though your company strategy is to move to the new product and technology. If you cannot service and support your existing products, how would you expect the same customer to buy your new product and use it.
Rule 2: Never create any regression bugs between the old version and the new versions. Customers remember and never forgets the bugs that you have introduced in the new version.
Rule 3: Never forget to merge the hot-fixes or bug-fixes or patches into the next immediate main release. Customers do not like to face the same issue that they faced in the previous version in the new version also.
Rule 4: Never add additional features without the permission of Product Owner or Product Manager. Never over complicate the code base to create a fancy or cool feature. Oftentimes, such code is overworked immediately after the release and not removed. It is easy to add code, but very difficult to remove code as you never know if any customer is using that feature. Remember that you can never release a software bug free product in your life. This is mainly due to the fact that many software products are used in various other use cases other than it is designed for. So write simple code which is easy to scale and maintain.
All the above mentioned rules are very important to have a successful product satisfaction for the customer. Do always remember to view or empathize from the view of your customer.
