“I have an amazing idea, I’ve found a solution to a problem, I’ll open a startup company”! — So, this is not that easy in reality.
Finding a problem-solution fit is necessary, but it is not enough. The fact that we can solve a problem for some users doesn’t mean that it is possible to develop a product on this basis and establish a company. Evidently, we meet many issues every day and all the time, and no one has solved them to this day. …
The Sprint Planning meeting is a meeting where the product manager introduces the required capabilities to the development team and the QA teams. A good sprint planning meeting is a meeting where team members understand the feature, why it is essential to develop it, the production environment and product constraints, who the users are, and what characterizes them.
This article list the steps the product manager should perform before, during, and after the sprint planning meeting.
The product manager is responsible for writing the product requirements document (“PRD”). The PRD writing phase is made after completing a few pre-steps: description of the market opportunities, define the user’s problem, gathering the user’s needs, and analyze it. The product manager and the project manager also need to create separate documents regarding the project management and the quality assurance test plan, addressing schedule, cost, development methods, development phases, deliverables, and testing procedures.
This article describes what a product requirements document should include.
This section describes an overview of the…
In one sentence, the PM role definition: “Turning the company’s vision into tangible products that deliver value to the customer”. This article introduces the role characteristics of product managers:
This article presents a list of characteristics and traits that define excellent product managers from my point of view.
An excellent product manager has a passion for winning and succeed in the role. In practical terms, it means:
When the product manager begins the process of characterizing a new system or product, it is his responsibility to research and define a wide range of aspects — for example, understanding the company’s objectives and business goals, technological characterization, setting its technical principles, defining the user experience, and understanding the product’s cognitive principles.
I have been working as a product manager for two years. In this article, I want to share my insights and things that I’ve learned as a product manager.
My professional experience includes work as a systems engineer and project manager. When I started work as a product manager, I noticed many overlaps between the three roles.
As a systems engineer, I was responsible for analyzing the system’s requirements and defining how to build the product. Also, I was responsible for determining the system’s design, infrastructure, interfaces between different modules, interface to external systems, and data flow.
I’ve learned that…
The product manager is responsible for the customer value proposition when using the product and to improve it continuously. As our company, there are competitors in the market that provide the same value and aim to the same target audience. The following section explains which questions the product manager should ask to perform competitor research on a new idea.
The entrepreneurs at the initial have to answer various questions. Through the market and competitors analysis, they can be answered.
There are many definitions in the literature about what creativity is, but there are two common characteristics: creativity is to produce something new and beneficial.
It is not as trivial as it sounds; a creative action must meet these two requirements to be considered innovative. Not everything new is creative; instead, it needs to meet the requirement of being beneficial. Here I find the connection point to the product management role.
The product manager is responsible for defining the problem and thinking of a solution that benefits the user every iteration.
For example, to think regarding something that the product’s…
As a product manager, I have been working with a scrum development team for two years. I have noticed that in a development team that works on one product, each developer does his tasks, and there is a dependency between team members. For example, the backend developer has finished his work, and now he is waiting for the frontend developer to end as well or vice versa. I have also noticed that there is often more than one product manager in the same domain in large systems.
I believe that knowledge and practical tools are the keys to success in all areas of life. This is what I research, implement, train, and teach others to do.