cloud:产品经理需要具备什么样的能力?如何培养?
by zghyk
当一个企业从单一产品线向多产品线跨越的时候,必须突破的一个瓶颈就是公司产品经理的培养,因为产品经理是公司价值链中最重要的一个环节,是直接面向客户、带领团队创造价值的领军人物,因此产品经理个人及其所率领的团队的能力往往决定了该产品在市场上的竞争力。然而,很多发展中的企业在构建产品管理体系和培养产品经理的过程中却面临很多困惑,比如:
1.产品经理该如何定位?其职责是什么?
2.产品经理需要具备什么样的能力?如何培养?
3.如何与客户有效沟通,从而发掘客户的隐性需求?
4.如何从大量的需求信息中提炼出核心的客户需求?
5.如何策划有竞争力的差异化产品?
6.如何确保策划的核心需求在开发过程中被充分实现?
7.如何把新产品成功的推向市场?
8.如何避免产品经理沦落成“问题经理”?
9.如何实现产品经理从“单挑”模式向“打群架”模式的转变?
10.如何构建适合产品经理成长的优良土壤?
2016-7-1812:28:16 tc1eqm
7 years, 8 months
Minutes from 7/13
by Josh Berkus
==================================
#fedora-meeting-1: fedora_cloud_wg
==================================
Meeting started by jberkus at 17:03:15 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-07-13/fedora_clou...
.
Meeting summary
---------------
* roll call (jberkus, 17:03:36)
* Availability of Atomic Host 24 (jberkus, 17:08:34)
* Action Items (jberkus, 17:14:53)
* Availability of F24 Atomic (jberkus, 17:17:51)
* Action Items (jberkus, 17:28:35)
* LINK: https://fedorahosted.org/cloud/ticket/136 (jberkus,
17:32:15)
* LINK: https://github.com/dotless-de/vagrant-vbguest (jbrooks,
17:37:07)
* ACTION: imcleod, dustymabe, jbrooks to look into #136 (jberkus,
17:38:03)
* ACTION: discuss Post-GA Cadence first thing in 7/20 meeting
(jberkus, 17:43:04)
* open floor (jberkus, 17:49:38)
Meeting ended at 17:52:37 UTC.
Action Items
------------
* imcleod, dustymabe, jbrooks to look into #136
* discuss Post-GA Cadence first thing in 7/20 meeting
Action Items, by person
-----------------------
* dustymabe
* imcleod, dustymabe, jbrooks to look into #136
* imcleod
* imcleod, dustymabe, jbrooks to look into #136
* jbrooks
* imcleod, dustymabe, jbrooks to look into #136
* **UNASSIGNED**
* discuss Post-GA Cadence first thing in 7/20 meeting
People Present (lines said)
---------------------------
* jberkus (56)
* dustymabe (40)
* maxamillion (24)
* zodbot (18)
* imcleod (7)
* jzb (6)
* jbrooks (5)
* jsmith (2)
* tflink (1)
* scollier (1)
* rtnpro (1)
* coremodule (1)
* sayan (1)
--
Josh Berkus
Project Atomic
7 years, 8 months
Update about Autocloud deployment
by Kushal Das
Hi all,
Below are the notes about Autocloud update happened last week. There
were few things which went bad, few points worked well. I am trying to
list them here, and how do we plan to make sure that the bad things
never happen again. I am ccing patrick in this mail as he was the
contact point from fedora infrastructure (read: he did all the work).
## deployment using ansible to the newly installed systems
We only had to change yum to dnf, and also had to remove the old hotfix
part from the roles. The current playbooks, roles seems to be stable,
and can help us in the future too.
## fedmsg-hub on the backends double enqueue
We had to restart fedmsg-hubs few times in the backends servers. In
between we also found that fedmsg-hub service was happily enqueueing the
jobs twice (for each compose), and then it got fixed automagically,
nothing was changed in our configuration or in code.
We are still not sure why this happened, but we are trying to dig more
on this.
## fedmsg-hub broke due to a faulty dependency
Even though we kept our code up and running for weeks, after the
production deployment we found one of the dependency (fedfind, adamw is
the upstream author) was broken with the fedora atomic image names, and
causing our fedmsg-hub instances go crazy. We have informed upstream,
and got a quick hotfix deployment in few hours after finding the issue.
For the next release we will make sure if keep it running for longer on
our internal hardware with messages from production fedmsg. This
dependency failure was something we should have caught, but could not.
## missing fedmsg(s) from autocloud on completing the testing of a compose
Now this was a known part of the whole development+release cycle. Sayan had
submitted the patch [1], but there was some slight miscommunication. In my part
i missed to track the state of this dependency.
For the next release, i will make a release/deployment checklist for
autocloud, and get it validated from everyone involved. Most probably we
will add too many minor details to this checklist, but that will help us
to keep things in track about any future deployment. sayan is currently
working to get that particular change in production so that we can send
out fedmsg(s) as required by adam.
## missing package dependency causing missing bridge on libvirt backend
We also found that a missing link in the dependency chain caused a
missing virtual bridge in the libvirt backend. Patrick helped to find
that adding libvirt as dependency for that particular box will fix the
issue in future.
We should test on clean installations while developing next time to make
sure this is not repeated. Plus we should think about getting better on
the stage environment.
## the new webfrontend is better
Sayan did a good job in making the new webfrontend. We can now point out
to the exact failures [2].
In future we should try to get more input about the features of the
webfrontend. Even though the whole service is made for automation, but
this frontend helps us to find, and point to the right issues found in
the tests.
## autocloud+tunir did what they are supposed to do
After fixing the hiccups, the autocloud service is doing what it
supposed to do, testing the images. We will push our effort in having
better test coverage in the coming months to take the advantage from
this new deployment.
Please comment/suggest whatever you think about the work. This will help
us to improve in the future releases.
[1]
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/386
[2] https://apps.fedoraproject.org/autocloud/jobs/66/output#290
kushal
--
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
7 years, 8 months