|
|
|
|
|
by NearAP
2804 days ago
|
|
It depends on the company. For some companies, the PM is responsible for "what" should be built and "how" (functional how) it will behave. Developers then try to implement the PM's "how" and then there's a back and forth between Dev and PM. For example, Dev might say - there's a better way to achieve this but it will change the functional behavior; or if we implement what you want, the page load time will be slow so is it OK if we do it this other way... At the end of the day, the PM's focus is - how will the average user use this product, what does the average user expect this product to do. That is generally not Dev's focus. Dev's focus is typically - what is the best way to get this done so that application loads quickly, doesn't place undue stress on the server, etc. Sometimes, Dev doesn't pay attention to how the UI looks, they just care that the code runs efficiently |
|