Comments on: Agile/Scrum and Product Management (part 3a)

By: Vote For Us! ComputerWeekly IT Blog Awards | On Product Management

Vote For Us! ComputerWeekly IT Blog Awards | On Product Management — Tue, 06 Jul 2010 14:26:16 +0000

[...] and Product Management (parts 1, 2, 3, 3a, and [...]

By: Andrea Lewicki

Andrea Lewicki — Tue, 09 Mar 2010 04:49:09 +0000

RE http://onproductmanagement.net/blogroll/: Thanks to everyone who contributes to these blogs. You're full of awesome! #prodmgmt

By: Happy (belated) birthday to us (again)! « On Product Management

Happy (belated) birthday to us (again)! « On Product Management — Thu, 18 Jun 2009 02:26:34 +0000

[...] and Product Management (parts 1, 2, 3, 3a, and [...]

By: The Cranky Product Manager never fails to disappoint, plus a blog you should read | The Cranky Product Manager

Thu, 04 Dec 2008 18:36:36 +0000

[...] and Product Management – Parts 1, 2, 3, 3a, and 4. (whew! lots of reading, but worth [...]

By: Agile/Scrum and Product Management (part 4) « On Product Management

Agile/Scrum and Product Management (part 4) « On Product Management — Sat, 11 Oct 2008 05:05:09 +0000

[...] (part 4) So, here it is, finally, part 4 of this series. Sorry for the gap since part 3 (and 3a), but work and life have a habit of keeping me [...]

By: Steve

Steve — Sat, 11 Oct 2008 01:41:29 +0000

My concern with the Product Owner being part of the Development group is that there may be too much pressure on them to make decisions that are best for the schedule/easier for the developer or more fun for the developer – and not what is best for the customer or the market. Their allegances could lie more towards Development and the person that manages them – not necessarily the product.

By: saeed

saeed — Wed, 24 Sep 2008 23:57:10 +0000

Rich

For ISVs, not having Product Management (or at minimum someone filling in for that function) for any extended period of time is the kiss of death regardless of the development methodology. PO is a Scrum construct and should be staffed independently.

In all but the smallest companies, there should be no excuse not to have both. People will hire developers regularly but don’t always think about the surrounding functions that need to be staffed appropriately to ensure the developers are focused on optimal tasks.

Saeed

By: Rich Mironov

Rich Mironov — Wed, 24 Sep 2008 17:33:26 +0000

The crunch is when there’s not enough money (or staff or attention) to have both a Product Manager and a Product Owner. Fine to segment roles, but having only a PO and no PM is (IMHO) a recipe for very bad outcomes, especially when a sales & marketing team is assigned to bring in revenue based on the result. PO is narrowly defined by the Dev organization…

By: Alan

Alan — Wed, 24 Sep 2008 09:59:18 +0000

It is very very confusing. We need more roles for the Agile approach. Can I say that this is a disaventage of the Agile approach becasue the team grows bigger and it would be more difficut to communicate effectively and owners and managers. Are their indenpendent like shareholders vs executives in a trading company.

By: Agile/Scrum Software Development and Product Management « On Product Management

Tue, 23 Sep 2008 02:16:14 +0000

[...] comments Agile/Scrum and Product Management (part 3a) « On Product Management on Agile/Scrum and Product Management (part 3)Chris on Agile/Scrum and Product Management [...]