Welcome to Siva's Blog

~-Scribbles by Sivananda Hanumanthu
My experiences and learnings on Technology, Leadership, Domains, Life and on various topics as a reference!
What you can expect here, it could be something on Java, J2EE, Databases, or altogether on a newer Programming language, Software Engineering Best Practices, Software Architecture, SOA, REST, Web Services, Micro Services, APIs, Technical Architecture, Design, Programming, Cloud, Application Security, Artificial Intelligence, Machine Learning, Big data and Analytics, Integrations, Middleware, Continuous Delivery, DevOps, Cyber Security, Application Security, QA/QE, Automations, Emerging Technologies, B2B, B2C, ERP, SCM, PLM, FinTech, IoT, RegTech or any other domain, Tips & Traps, News, Books, Life experiences, Notes, latest trends and many more...
Showing posts with label principles. Show all posts
Showing posts with label principles. Show all posts

Sunday, September 20, 2020

Why Digital is The Future! How to have a successful journey...

Why Digital is The Future! How to have a successful journey...

"Digital" and "digitization" or "online" has become a very common word in the recent past due to the C-19 pandemic situation, and yet, the digital transformation has been there in every industry more than two decades or so to create value-driven business opportunities for the organizations in their served customer segments with the right value proposition to fulfill their internal and external customers with amazing customer experiences (CX).

Some basics to know- The average IT spend across all industries was around 8 percent of their revenues as a magic number and yet it depends on many factors like industry, region, and age of the company, etc. Now, think about organizations spending between 4 to 24 percent based on the industry for their IT or digital goals, wherein the staff of IT and CIO or CDO would be bringing seamless and easy to use tools and solutions for the various businesses including sales and markets and other business functions in the company (plus external customers too). 

On a side note, usually, companies spend roughly around 10 percent as a magic number on sales and marketing, with a disclaimer that it depends on the size of the company and which sector it belongs to, etc.

With that, it's very imperative that you as a CTO or CDO or CIO or Digital IT Head need to have a very clear plan to create a successful journey towards it with the available budgets in place... 

Some of the key caveats for the success of any organization to become truly digital are:

  • Make sure to address the five domains of the digital strategy - customers, competition, data, innovation, and value
  • Create a comprehensive digital platform with digital products, and not siloed or isolated apps or customizations
  • Start with small to focus more on the CX, and then slowly evolve and improvise your design
  • How fast you pivot to digital is the clear caveat to bring more efficiencies and value to your businesses and their respective functions
  • Have a clear business architecture and enterprise architecture in place whenever your organization do any M&As and adapt as quickly as possible so that all the respective fulfillment happens seamlessly for the existing (for example, legacy apps) and newly acquired customers
  • Application and/or software modernization with the latest emerging technologies like microservices, cloud, machine learning, artificial intelligence, monitoring, cybersecurity, etc
  • IT architecture is very important to any organization, and yet, that needs to be refined every now and then to meet your business outcomes and demands
  • Having an application rationalization chart to know the right sunset and sunrise digital products based on your organization priorities so that it is easier to maintain and innovate faster while the systems and applications are co-existing with newer digital products; a clear winner to achieve improvements in business operations
  • Always, treat your data as the biggest asset to your organization to do any sort of transformation and decision making
  • Make sure to have highly available, reliable, and accurate data APIs/Services for the key source of truth from the various data stores, these can be called as DaaS (Data as a Service) to ease accessibility and minimize the data issues
  • A robust operational backbone is necessary but that certainly is not sufficient for an organization's digital future, an organization needs to adapt to the newer technologies and have to innovate faster to create newer digital products or try to leverage existing newer COTS (Commercial off-the-shelf) tools to create newer digital solutions to continue delight and address all of your customer behaviors
  • Always, have shared data analytics or insights from the data that you have collected from customers
  • Re-use, Re-design, and Re-create wherever and whenever required to save time and money
  • Have intelligent automation in place for automating some/many of the most used business processes
  • Promote continuous delivery and/or integration with DevOps and SRE (Site reliability engineering) principles, so that feedback loops/cycles are faster and teams can implement and address them in a nimble fashion
  • Promote co-creations and co-ownerships with the right internal and external accountability frameworks with faster pace decision making and approvals etc
  • "digital" is everyone's job to become truly a digital organization. For example, to have the right business owners or product owners and then create more collaborative and agile ways of working together to reduce risks and dependencies
  • Try to create a mindset where the customer is more important than anything, and providing seamless customer experience matters a lot
  • Treat your tech debt as an innovation aspect of the digital journey, and have the organizational culture as design thinking instead of leaner thinking to come up with innovative digital solutions
  • Having a digital product mindset instead of a project mindset
  • Also, an organization can focus mostly on their core foundations and innovation only by having a great powerful external partner and/or developer community who gives you early feedbacks and promote your organization with ever scaling digital platforms
  • Have resiliency aspects in your planned mission-critical releases, plan very well for the unplanned occurrences, and have architecture design for the next billion users

References/books:

Enterprise Architecture As Strategy: Creating a Foundation for Business Execution

Designed for Digital: How to Architect Your Business for Sustained Success (Management on the Cutting Edge)

Why Digital Transformations Fail: The Surprising Disciplines of How to Take Off and Stay Ahead

The Lean Product Playbook: How to Innovate with Minimum Viable Products and Rapid Customer Feedback

https://www.amazon.com/Enterprise-Architecture-Strategy-Foundation-Execution/dp/1591398398

https://www.bmc.com/blogs/digital-transformation-books/

https://www.cnbc.com/2019/04/08/4-trillion-in-tech-spending-in-2019-heres-where-the-money-is-going.html

https://vtldesign.com/digital-marketing/content-marketing-strategy/percent-of-revenue-spent-on-marketing-sales/

https://www.flexera.com/blog/elo/2020-state-of-tech-spend-it-spending-benchmarks-and-trends/

https://www.flexera.com/blog/industry-trends/it-spending-by-industry/

https://blog.techvera.com/company-it-spend


Wednesday, January 1, 2020

I know, you know about Pyramid; but what is "Test Pyramid" then :)

A happy new year to all the readers out there, and yet another new decade with the 20s, and wish you all be happy, peaceful and healthier than ever before to take up challenges that are waiting for you in this decade. I started blogging a decade back and when I reflect on this irregular hobby, I feel great about it as time passes away so fast and this blog is of 10 years old now:)

Okay, I know, you know about Pyramid; but what is "Test Pyramid" then :)

You would be getting to know about the Test Pyramid only if you are serious about the Test Automation and how much you can actually do the test coverage with your automated testing for the developed software.

If a developer is writing the tests by himself for the piece of code/software that he has built: those are the unit tests as part of the Unit Testing. And if he is thinking about doing some sort of automated tests for testing the integrations with other services, then that would be the integration testing or services testing. If he is looking for even broader testing scope of the overall system, then that would be the End to Eng System Integration Testing. Even after all these, sometimes, he has to manually test the system to how it is working and those are nothing but the Manual Testing.

With the above in mind, Let's see what is the Test Pyramid and how it would look like in the below picture, and keep in mind that the time spent and the costs involved are more from bottom to top, and the tip of the peak at the pyramid comes with the manual testing(that we have not discussed above while providing the context).



So, what is your take on how much we can cover from the test pyramid? It is completely up to you and your engineering team on what are your priorities and how you wanted to see the return for the time and cost that you have spent on all the layers of your test pyramid.

Reference articles:
https://martinfowler.com/articles/practical-test-pyramid.html#TheTestPyramid



Saturday, November 30, 2019

Quite Interesting: 12 Steps to Better Code... and still valid!

Quite Interesting: 12 Steps to Better Code....and still valid!

It has been two decades or so, and this so-called "Joel Test" is still valid for the current situation of software development engineering practices

The Joel Test
  1. Do you use source control?
  2. Can you make a build in one step?
  3. Do you make daily builds?
  4. Do you have a bug database?
  5. Do you fix bugs before writing new code?
  6. Do you have an up-to-date schedule?
  7. Do you have a spec?
  8. Do programmers have quiet working conditions?
  9. Do you use the best tools money can buy?
  10. Do you have testers?
  11. Do new candidates write code during their interview?
  12. Do you do hallway usability testing?

Source: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/

All the above 12 criteria are valid except 5&6 based on a few situations like business demand or if-it-was-working then lets-not-change-behavior :)

Sunday, November 3, 2013

Quote of the day!

Every time your heart is broken, a doorway cracks open to a world full of new beginnings, new opportunities.

— Patti Roberts