Product Manager

Giriş

Product Manager kullanılan yazılım geliştirme yöntemine göre farklı şeyler yapabilir

1. Scrum Açısından 

Epic'leri Kim Oluşturur
Açıklaması şöyle. Product Owner Epic'leri oluşturur. Epic'ler daha sonra Story'lere bölünür.

Product Managers had provided the requirements which Product Owner had broken into Epics

Yani Product Manager gereksinimleri sağlar

2. Scaled Agile Framework (SAFe) Açısından

Açıklaması şöyle. Benzer şekildedir ama açıktan gereksinimleri sağlar denmiyor.

The Safe Agilist and Product Manager define and break up larger pieces of work (often inherited from the portfolio process above) and then pass the pieces into the teams.

3. Esas Ne Yapar

Product Manager uzun soluklu bir bakışa sahiptir. Açıklaması şöyle.

Contrary to a project, that can comprise a temporary slot in time, a product itself is more long term. In essence, product management revolves around the product, i.e. anything that can be offered to a market to solve an issue or cater to a need (or want).

The Product Manager is responsible for a product’s success through the whole product lifecycle. Focusing on the “what” more than the “how,” a Product Manager holds a high-level view and steers the growth and progress of the product.

Bir başka açıklama şöyle

Product management is not about:

 

- Asking customers about the requirements

- Writing detailed specifications

- Creating prototypes instead of designers

- Instructing developers on what to do

- Verifying and accepting the work of others

- Obsessing over velocity, deadlines, and roadmaps

- Mastering the role of the Scrum PO to perfection

- Acting like the CEO of the product

Anyone can do that.

It's about:

 

- Understanding the market and the business in depth

- Focusing on customer's problems, needs, and desires

- Collaborating closely with engineers and designers

- Identifying opportunities, ideating solutions, and tackling the risks together

- Marrying customer goals and business goals

- Influencing others to work toward the common goal

- Being humble (it's ok not to be the smartest person in the room)

- Leading without authority

 

Start with those questions:

 

- Why are we building this thing?

- Why are we building it now?

- For whom are we building it?

- What's the unique value of our product?

- How is it aligned with the company's vision?

- How is it aligned with the business strategy?

- What does success look like? How can we measure it?

- What are the critical customer jobs (functional, emotional, social)?

- How will it affect our customers and users?

- How will it create value for the business?

- Can we buy it instead of building it?

- How can we make sure that our customers would love it?

- Can our business support it (e.g., legal, finances)?

- How can we bring it to the market? Do we have the required channels?

- Is it feasible? Can our engineers implement it?

- Should we do it at all? Are there any ethical considerations?

- What are the other risks? How can we mitigate them?

- What are the riskiest assumptions? How can we validate them?

Roadmap Nedir?

Açıklaması şöyle. Bir fikirler listesidir. Fikirler de farklı farklı kaynaklardan keşfedilir

Roadmap is not a backlog of tasks.

It is a list of ideas that need testing to enhance your product to delight your customers.

Ideas are discovered via data analysis, customer feedback, research, or plain ideation.

Great ideas can not be predicted :) Assumptions need to be tested.

After discovery, Continuous Delivery puts minimum viable product improvements to production.

Tests bring new data, which is used to discover new ideas, and this product enhancement loop continues forever.