Category: Product Development

The role of the product owner comes with a lot of responsibility and things you supposed to do. However, there are also things that you shouldn’t do. This post brings attention to 5 Product Owner anti-patterns that you should avoid as they either harm your product or your team. Not being able to make decisions This is probably the number one anti-pattern for a product owner. As the product owner, it is your responsibility to make decisions that will move your product forward. This includes making tough calls and sometimes disappointing stakeholders. If you are not able to make decisions, you will quickly find yourself bogged down in analysis paralysis and your team will lose confidence in you. Making decisions …

5 Product Owner anti-patterns to escape from Read more »

Product Owner vs Project Manager, what’s the difference? Seems there is none, as many orgnizations just rename roles from one to the other. The cases of renaming that I’ve seen, were one way from Project Manager to Product Owner. That’s a pity as both are distinct roles which require different profile to fill the roles with quality.

Technical debts are part and parcel of the software development process and no matter how careful we approach the development process, there will always be possibility that we may encounter them along the way. Technical debts imply that a developer, at some point applied the easiest route to a solution instead of using a better approach to a problem that would take time. The most vulnerable time for making these haste decision is when the deadline for release of a software product is nearing and there is still work to be done.  These debts can also be incurred during bug fixing. A lot can go wrong during debugging, and removing a minor bug on a large projects sometimes can cause …

How to avoid and deal with technical debt Read more »

As my last post was about how to write good User Stories, this post is about good structures for them. When developing products that require several team and stakeholders to collaborate, it is beneficial to have a common User Story structure so that everyone can focus on the product instead of struggling with information and requirements about it. With all the points below please remember that a User Story should be a place holder for conversations. So avoid adding all details and take away room for negotiation and conversation.

As a Product Owner I would like to know how to write good User Stories So that I can provide ideal input to teams for turning requirements into a product increment. What is an User Story? An User Story is a brief description of a certain functionality or desired feature from a user’s perspective. In an User Story these pieces of functionality or features must relate to business value. As mentioned User Stories are very brief descriptions and with that become a place holder for conversations between business people and developers When this conversations take place, knowledge is spread across all involved people and a shared understanding is the result. User Stories focus on value to be delivered to an user. …

User Stories Well Done Read more »