Articles

I’ve just been appointed the CTO of a small company with less than 10 employees. Companies of this size typically don’t have the luxury of hiring a professional Project Manager, hence the role almost automatically goes to the CEO of the company, since he is the product owner – Which creates a problem for me, summarised in the ingress of this article. But as the CTO, I’m also responsible for all IT choices, including infrastructure choices, so let me go through all of my choices below – Since these have consequences for the process we must follow.

Cloudless first

Cloud systems such as Azure or AWS are amazing products, with a feature list covering everything you can imagine. However, they’re also ridiculously expensive, typically at least 10x as expensive as a simple VPS providing the same value from an application deployment point of view. At my last company we paid €5,000 per month for Azure, and probably something similar for our AWS account (Sigh, yes, we used both! Not my decision though!) – Let’s say €8,000 per month to make sure we’re within the boundaries and that I am not exaggerating. I told my developers back at that company that I could have ran the whole company on a handful of VPS servers from DigitalOcean paying no more than €200 per month in total. Nobody believed me until our CTO confirmed my numbers more or less by saying; « At my former company we ran a 300,000 EUROs daily profit FinTech company for some 200 EUROs worth of droplets from DigitalOcean. »

Source de l’article sur DZONE

Being an Architect, Product Owner, or a CXO of your organization has already purchased a brand new Anypoint platform subscription or planning to get one based on evaluation of the platform and now In dilemma which subscription model to go for?

This article will help you to provide a 1000ft overview of various deployment options available in Anypoint platform and which one to go for. 

Source de l’article sur DZONE

As a Product Owner, you are responsible for Product Backlog management, stakeholder management, and forecasting. Therefore, you will probably use a variety of tools and techniques to track progress, manage expectations, and keep people informed. One of the tools that may come in handy for you is a product roadmap. Applying product roadmaps effectively can be challenging, however. The concept of a product roadmap is that it is a high-level, strategic plan, that describes the likely development of the product over a given period of time. The roadmap should support the products’ purpose and vision and it helps the Product Owners to keep their stakeholders aligned. The roadmap also makes it easier to coordinate the development of different products and it fosters transparency in order to manage customer expectations.

In a lot of organizations, I see that Product Owners are focused mostly on developing features and therefore, a lot of roadmaps are also dominated by features and functionalities to be delivered. The disadvantage of focusing on features too much is that there are always too many features that would add value, therefore creating a lack of focus on the vision and goals. By focusing on the features too much, the roadmap will turn into an overloaded product backlog, instead of a high-level, strategic plan for the products’ future development.

Source de l’article sur DZone