Comments on Scrum Product Ownership 3rd Ed - reply with your notes
Ned Horvath
Reneé Lasswell
* p. 169 in Chartering section - MMP, MMP and MVP in footnote was a tad confusing. p. 178 uses the MVP term again - fully defined.
* p. 177 under the image - I got a bit confused about what x-team and sprint-x-sprint meant.
Chapter 15 Scrum of Scrums
* p. 194 in bullet list - wasn't sure what 2nd level team was
Chapter 16 Scaling Considerations
* Some was read through quickly as I have very little experience with large scale scaling
Chapter 17 Product Organizational Dynamics
* p. 215 footnote - might want to add that swarming is an emergent concept in scrum but an explicit one in other agile approaches like Kanban.
* p. 215 - I believe the three in 3-amigos, does not specifically mean just or only three, but that was entirely clear to me in learning about this new reference.
Chapter 18 Implications of Architecture...
* p. 230 Technical User Stories Defined section - Consider moving this earlier in the chapter as all the Technical PO content expects the reader to be on the same page already for this definition.
* p. 231 - You would probably need to move this follow up section as well.
* p. 236 A Hybrid section - unlike the previous two sections, I could not quite visualize the new hybrid role. This area might need more in a specific example.
Chapter 19 Portfolio Level Planning
* No real feedback here. Again, a bit outside of my experience and interest.
Norma Antunano
Chapter 16:
P.166 last paragraph. It will help to find in the book how the Product Owner builds knowledge, skills, perspective to effectively address (overall) some of the typical forecast methods/approaches applied in the business and in other groups (with whom software development group(s) has dependencies) vs representative forecast methods/approaches in the software world. Will this be different for large enterprises versus small organizations?
Definition of of capability and capacity of the team will be helpful, including insight on how these attributes are measured and aligned to the overall organization.
p 166 foot note 61, is it missing content (last word "In")?
Page 167:
An application example of the tempo pattern will be helpful;the paragraph before last one can be confusing.
Foot note appears to be incomplete.
Page 168:
Any other example aside of Salesforce? Perhaps an example describing how small organization turning in high value software does it.
P.175: Estimate granularity section: “ amplify the size of the stories….” to have enough attention in planning.
Blitz planning has been used before in other contexts (including Building Democracy), author may want to add more context/ some interesting background (with the goal of complement the interest of the readers) in addition to Cockburn b(perhaps is a pioneer using it in software development). A good reference article is “ Building Democracy Anew” by Stefan Cuiperus, (Sage Journals, October 2016); the semantics of politics over neighborhood planning during and after WW II are interrogated (political engineering:”the conscious design of political institutions to achieve certain specific objectives” needs to be associated with neighborhood planning; interfere conceptions of popular democracy in the pedagogical & sociological thought in America).