Bilmek istediğin her şeye ulaş

Ürün Yönetimi

Ürün Yönetimi Ağı ile ilgili ilk açıklamayı siz girin.

Mayıs 2015

Ceyhun Cem Süsal  yeni bir  gönderide  bulundu.

Setting Up The Baseline

Developing a product, meaning end to end development, is a complicated process and its quality depends on your analysis as a product manager,STORIES. You set the baseline and everything is getting built on top of it. It's all about your ability of setting the baseline to the OPTIMUM level.

How does it work?

The first thing you will do is to gather requirements from business units, so it means that everything starts with listening to internal customers. You will have to listen carefully and question the messages passed from your internal customers simultaneously.

You will have the following algorithm on your mind
- Do we really need this?
- Is it feasible?
- What benefits will we have?
- How much effort needed?
- Can the problem be resolved with existing resources?
- Most probably you will be said that it is URGENT. Is it really urgent?
- What are the opportunity costs of doing this?
- What kind of changes needs to be done?
- What are the side effects of these changes?
- What kind of resources will be needed?
- Is there any 3rd party in the project?
- Do you need to design something?
- Do you have any other tasks?
- Is there any on going development causing delay for this requirement?
- How will you measure the success/failure?
- Is there any business unit getting effected by these changes?
- Who is the contact person for me? A single contact person is generally the best option :)

The second one will be passing the message to the development team. This is actually like a translation process. The quality of the answers will directly reflect the quality of the translation. You will also need to trigger another algorithm:

- What are the security concerns?
- How can I create a usable, functional and meaningful product from these requirements?
- The business asked for doing that. What else can I add to it?
- What are the test cases?
- Is there anything effecting the performance?
- How can I explain why we are doing this?
- Which technical details should be provided to the development team?
- Is there any data action?
- What is the priority on this?
- When can we start developing it?
- Can I split the requirements into pieces?
- Is there any legal process?
- Do I need to design something?
- Can these requirements be wireframed?
- How much test effort needed?
- How much development effort needed?
- How often should I communicate with the business owners?
Mart 2015

Ceyhun Cem Süsal  yeni bir  gönderide  bulundu.

Agile and Product Management: How they differ/engage

Agile is just a project management methodology.

"It does not give you perfect product. "

It helps you to develop faster with a better quality - if you implement it right : -)

Keep in mind that you will not have the best product in the market just because you are doing agile.
It's not that simple. You will need additional skills.

Let me give you an example :)

AGILE when you do it right:

Need Identification >
Requirements >
Planning and Prioritizing >
Analysis >
Development >
Test >
Demo >
Customers are using your product :)

It repeats the cycle given above periodically (generally weekly). -> SPRINT

AGILE when you fail:

Top management meeting (Other party saying we are doing this) >
Your manager - we should do it >
You were planning to do something now you have to change it >
You analyze your manager's request >
Developers were doing something you need to stop them >
OHH GOD you had a road map forgot to update it >
Deadline is too close test it fast >
Ignore some bugs it is not important >
Where is my Kanban Board >
You saw that the product does not fit your needs >
Pushed it to live because your manager wants to see it

Note: Actually the scenario above is limitless.

What does product management do with AGILE then?

AGILE ease the job of product management. Most of you heard about the MVP (Minimum Viable Product) concept.

AGILE supports this concept because it is iterative and incremental (that's the keyword) which means you deliver something in each sprint (generally every week) to your customer.

It helps you to test your product before fully implementing it and you/your customer start benefiting it at an early stage.

I suggest you to set your metrics to monitor your product. You will be able to identify your mistakes earlier.

AGILE is open to changes at any stage of the development.

"You can change anything any time. "

It does not support something that your audience does not like.

Daily stand ups will help you to understand what is the progress and you will have an idea about what your team is doing.

You will estimate the effort with your team. They will question your product and help you to make the decision whether it is feasible?

What other skills you need?

You need a very good understanding of who your customer is and what does he/she need?

This means analysing/testing/monitoring.

You will need to have an idea about what your business is doing?

Observation is the key for success.

You will also need to split the whole into right pieces. Not so big not so small :)
Ağustos 2012

Thecrazyhands, bir soruya yanıt verdi.

Günlük fırsat siteleri sattıkları ürünlerin tedariğini nasıl hangi şekilde gerçekleştiriyor? Peşin para ile stok mu yapıyor ürünü satıp daha sonra alıp mı kargoluyor?

Bu sitenin büyüklüğü ve sermayesi ile ilgili bir durumdur.Ciddi bir sermaye ile piyasaya giren site ürünü toptan alarak adet maliyetini düşürür ve üyesine de daha düşük fiyattan satar ve böylece rakiplerinden sıyrılır.

Bir diğer yol ise stok yapmadan sipariş üzerine tedarik etme yöntemidir.Sitede satılan ürün sitenin arka planındaki bir yazılım sayesinde tedarikçi firma tarafından algılanır ve kargolanır.Böylece site hiçbir işleme karışmadan sadece komisyonculuk görevini üstlenir.

Temmuz 2012

Gonca Köse, bir soruya yanıt verdi.

İyi bir ürün yöneticisi nasıl olurum?

iyi bir ürün yöneticisi olmak için yönettiği ürünün:
  1. Ürün stratejisi hazırlamak
  2. Hedef kitleyi belirlemek ve bunun doğrultusunda çalışmak
  3. Yenilikleri takip etmek
  4. Rakiplerini sürekli yakından izlemek
  5. Reklam kampanyaları için strateji belirlemek
  6. Maliyeti düşürücü çalışmalar yapmak
  7. İnce detayları düşünebilmek
  8. Müşterinin gözüyle bakabilmek
  9. Eleştirileri dikkate almak
  10. İnsanlarla ilişki kurma yeteneği yüksek olmak gereklidir.

11 kişi

Konunun Takipçileri

Alt Konu Başlıkları

Henüz bu konu başlığı ile ilgili konular bulunmuyor.