I attended 2 workshops in the last 2 days on designing for a behavior. First from an internal expert at Cognizant who walked us through an approach which helps in understanding an user’s core motivations and the next was a workshop conducted by Neema Moraveji. I think they both go hand in hand and I have […]
Ron Jeffries’ Three Cs Card Stories are typically written on Cards. Cards can be annotated with notes, estimates etc. Now a days we have software to help with it. Conversation The main purpose of a story is to draw out a conversation with the product owner and development team. This is when the product owner […]
Confusing Customer Requirements with Product Requirements Confusing Innovation with Value Confusing Yourself with Your Customer Confusing the Customer with the User Confusing Features with Benefits Confusing Building Right Product with Building Product Right Confusing Good Product with Good Business Model Confusing Inspiring Features with “Nice-to-Have” Features Confusing Adding Features with Improving Product Confusing Impressive Specifications […]
When you are building a product, one of the first things you will have to do is begin recruiting potential customers. What do I mean? The worst that can happen to any product development company or team is for it to find that there are no customers willing to buy the product when it has […]
There is a great article available at the SVPG blog about how to develop a strong product manager. A self assessment is below. On the rating scale, 0 indicates not important (or not strong) and 10 indicates extremely important (or very strong). Knowledge: User/Customer Knowledge – Is the product owner the company acknowledge expert on […]
In an Agile development environment, one of the questions that is kept asked is how do you capture and solve Non Functional Requirements? As always we first note down the functional requirements as user stories and then we break it down in to smaller manageable user stories. How do you do that? For example a […]
There is a very succinct post on writing very effective use cases by Michael Shrivathsan. Although I prefer User stories to Use cases it still is a good post and well worth the time to read. It talks about how to capture a requirement that allows other members in the team (Engineers, Project Managers, Stake holders) understand […]
Both are means for capturing requirements and both can be very effective in doing so in comparison to traditional verbose requirement specification documents that runs through several pages. However there are some differences between them . Both can be used effectively depending on the your team’s structure, domain expertise and experience with that particular product. […]
As a product manager one of your most important responsibilities is to plan for tasks that should go in to a sprint/release. While doing so what is the rule that should guide your decisions? ROI is most commonly used as a purely financial metric: ROI = Financial Return / Financial Investment In this case it […]
Original article My companies founder and I had an interesting discussing about keeping the pay structure transparent. For others who are interested, there is a great post on an open system of compensation. There are a lot of benefits in following a transparent system. 1. It focuses employees on task at hand rather than worry […]
reddysblog 