expand_less
For larger teams, I would add QA processes including acceptance testing in the lower right box and other contribution to the neighboring boxes. Also, a product manager often represents the users in the process rather than users interacting directly with users.
--[[Gerry]].....2017-02-15 11:28:15 UTC
There's quite a few peripheral boxes that could be added. Besides ATP, there's often a set of specialists one has to pull in -- Ui/UX experts, graphic (or more generally, media) designers, domain experts, network experts, tooling/dependency experts, release candidate management, revision after production management, etc. I think that's where a PM's facilitation really comes into play.
--[[Marc Clifton]].....2017-02-15 18:42:51 UTC
But then again, once we add more boxes, we move away from the question that the diagram was personally intended to answer, and more into the realm of complex systems of interaction, agility, roles, etc.
--[[Marc Clifton]].....2017-02-15 18:44:19 UTC
For larger teams, I would add QA processes including acceptance testing in the lower right box and other contribution to the neighboring boxes. Also, a product manager often represents the users in the process rather than users interacting directly with users.
--[[Gerry]].....2017-02-15 11:28:15 UTC
There's quite a few peripheral boxes that could be added. Besides ATP, there's often a set of specialists one has to pull in -- Ui/UX experts, graphic (or more generally, media) designers, domain experts, network experts, tooling/dependency experts, release candidate management, revision after production management, etc. I think that's where a PM's facilitation really comes into play.
--[[Marc Clifton]].....2017-02-15 18:42:51 UTC
But then again, once we add more boxes, we move away from the question that the diagram was personally intended to answer, and more into the realm of complex systems of interaction, agility, roles, etc.
--[[Marc Clifton]].....2017-02-15 18:44:19 UTC