New answers tagged

3

I would strongly suggest you ask the team. The team understands the domain, the way they work, the personalities involved and the nature of your organisation. They are in a much better place to determine the team structure than anyone outside of the team. This is what we mean when we talk about self-organising teams. Also, don't be afraid of making the ...


0

I would suggest considering very carefully how exactly you want the projects to be "split," and then along those lines designate "assistant project owners" and "assistant designers." (My terms ...) Effectively, these roles focus on one of the "splits," treating each as a "sub-project" with one eye while focusing fully on the "main project" with the other. ...


-1

Here's my admittedly-informal use of the term: The "product owner" represents The Almighty Customer, and is often the team's most direct liaison to them, usually reporting directly to them. This role is very specifically focused on what the product will do and for whom it will eventually do it, and for ensuring that the whole thing actually does meet the ...


0

The origin is... Certain methods were developed at software companies and not for IT groups (companies such as Easel or Borland). Thus Turbo Pascal was a "product" that they sold -it was not a brand, Borland was the brand- thus if you lead the Turbo Pascal group you "owned" the product. Marketing did not have a concept of product owner, they centered ...


Top 50 recent answers are included