Timeline for How to handle product manager that ignores others opinion
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19, 2020 at 22:46 | answer | added | Benjamin | timeline score: 5 | |
| Jan 19, 2020 at 20:40 | review | Close votes | |||
| Jan 21, 2020 at 15:32 | |||||
| Jan 19, 2020 at 20:14 | answer | added | DJClayworth | timeline score: 4 | |
| Jan 19, 2020 at 19:07 | comment | added | estebarb | As we handle it: the PO is the one that writes stories, act as a proxy to the architect, and interacts with other teams (feature requests, etc). The PM manages the schedule, scope, resources and interact to higher level PMs. The scrum master manages what goes into the sprint. The architect designs and review. As the architect usually is shared between several projects usually the PO sometimes takes his place. The PO and the scrum master are developers in the team, the architect and the PM are not expected to develop code. All the team can review, but only some can approve code in. | |
| Jan 19, 2020 at 18:49 | comment | added | Benjamin | What's your role compared to the PM? What are the PM's rights/duties as defined by your organisation? The way I am used to this, the PM is a stakeholder, and the PO is the stakeholder manager. is this right? | |
| Jan 19, 2020 at 17:40 | review | First posts | |||
| Jan 19, 2020 at 17:50 | |||||
| Jan 19, 2020 at 17:40 | answer | added | gnasher729 | timeline score: 4 | |
| Jan 19, 2020 at 17:36 | history | asked | estebarb | CC BY-SA 4.0 |