Posted on

Overruling the Product Owner?

There are plenty of failure possibilities with Scrum. Since Scrum is an intentionally incomplete framework with a reasonable yet short “manual,” this effect should not surprise anyone. For example, what if the stakeholders (who bring the budget that is funding your Scrum team) insist on calling the shots by overruling the Product Owner’s prerogative to define the composition and the ordering the Product Backlog? What if your stakeholders suffer from the “my budget, my feature” syndrome?

Join me and delve into the effects of overruling the Product Owner in less than 140 seconds.

Posted on

Building HTTPS Proxy With Anypoint API Manager and MuleSoft

Anypoint API Manager has capabilities of enabling the HTTPS proxy by using secrets stored in the Secret Group to build the HTTPS enabled APIs for Cloudhub and Hybrid implementation.

Secret Manager is basically used to store the secret like Keystore, Truststore and configure the TLS context, which can be used with Runtime Fabric and API Manager in Cloudhub.

Posted on

SOCKS5 Proxy and its Benefits

Like many other internet protocols, SOCKS channelizes packets between a server and a client with the help of a proxy server. The packets of information are transferred through a proxy server that generates an arbitrary IP address before the information reaches its destination.

SOCKS5 is the latest version that uses proxy servers to form User Datagram Protocol (UDP) or Transmission Control Protocol (TCP) through arbitrary IP addresses.

Posted on

Is My Product Backlog Just a Laundry List?

What's on your list?

In simple terms, a product backlog is a list of everything that needs to be done in relation to the product. This is the key artifact that helps in translating the high-level product vision and serves as the foundation to initiate the development of the product.

The product backlog includes features to be built, enhancements, fixes, quality attributes, etc. in the form of user stories.

This is beneficial in comparison to the waterfall approach of creating multiple pages of requirement documents because it provides prioritization so that the team has a direction, has the necessary details required by the team, and it keeps evolving and responds to change.