Flow

In this article, we discuss how the evolving technologies and ways of working impact the development of full stack engineering skills.

Explore the challenges faced in measuring end-to-end lead time, the importance of classifying different types of work, and the benefits of adopting a structured and scalable work classification model for product delivery.

Meet our perspective and tips on how to explain what DevOps is and its impact on organizations in a way most non-tech executives appreciate and understand.

In this article, we will explore how Machine Learning (ML) and Artificial Intelligence (AI) models improve the efficiency and relevance of notifications.

Design is how it works. What part of your product and service needs the most attention based on how it works? How would you re-design it to make it great?

Mark Zuckerberg built Facebook on the philosophy of 'moving fast and breaking things', believing the opportunity cost for not moving fast enough far outweighs the investment in tools.

Do you always need to discover how to do something? Well, the answer is no. Sometimes we do know enough to just move ahead. Sometimes we have so little knowledge, it’s best not to jump to experiments.

The digital economy comes with demands and expectations, or rather assumptions. One assumption is that we can’t operate a business the way we have in the past.

One of the hardest parts of product management is saying no and it’s related quite closely to stakeholder management and prioritisation.

Creating products and services that are simple is hard. Designing experiences that just work for users in a satisfying way takes skill and deliberate practice.

Value. Flow. Quality. These three ideas weren’t just chosen because they make for a nice acronym; they’re the guiding principles that we live by and champion.

One mistake teams new to Agile development make is an overeagerness to always work on the highest value items. But what about the value missed out on over time?

The second principle of VFQ is to optimize the flow of work end to end. This means we need to think about the moment a new idea comes into existence to when it is in the hands of a user.

You only know if a requirement was right when you built the thing and a user and customer says it’s correct. Spend time creating an approach that defines the important feedback loops for better results.

We explore an article about software development and it's focus on two types of laziness - good laziness and bad laziness.