{"id":12088,"date":"2014-03-17T10:14:01","date_gmt":"2014-03-17T08:14:01","guid":{"rendered":"http:\/\/mozaicworks.com\/?p=6488"},"modified":"2022-02-01T17:58:35","modified_gmt":"2022-02-01T15:58:35","slug":"learning-resources-for-product-owners","status":"publish","type":"post","link":"https:\/\/mozaicworks.com\/blog\/learning-resources-for-product-owners","title":{"rendered":"Learning resources for Product Owners"},"content":{"rendered":"
A few days ago I published a blog post with resources for ScrumMasters<\/a>. I was saying how, since it\u2019s a relatively new role, it requires new skills to get it right, so people often ask me for learning resources. Well, the same goes for the Product Owner role.<\/p>\n In the past, things were clear: we had product managers and business analysts. All of a sudden, Scrum brought into the spotlight a new role for managing a product, the Product Owner<\/strong>. And it too requires additional skills. To help you overcome the initial challenge, in this post I share a few resources that you\u2019ll hopefully find useful.<\/p>\n We\u2019ve got a few workshops where you could learn more about the Product Owner role:<\/p>\nThe Product Owner Role<\/h2>\n
\n
\nThe role, as described in the Agile Atlas.<\/li>\n
\nA view by my colleague Iuliana.<\/li>\n
\nA very good video, highly recommended.<\/li>\n
\nA broader view of the role. Comes with a nice poster.<\/li>\n
\nThe role in depth, managing the product, working with the team.<\/li>\n
\nIs it advisable to combine the two roles?<\/li>\n<\/ul>\nManaging the product<\/h2>\n
\n
\nHow to write stories, work with users, estimate and plan work.<\/li>\n
\nReduce the product risk by investing in minimum viable products.<\/li>\n
\nA recent approach to specifying requirements, that emphasizes collaboration and automation.<\/li>\n
\n\u201cUse personas\u201d, \u201climit story size\u201d and others.<\/li>\n
\nStories should be independent, negotiable, valuable, estimable, small and testable.<\/li>\n
\nLearn how to make stories small enough to fit into a sprint.<\/li>\n
\nSplit your features into user stories based on priority and coherence.<\/li>\n<\/ul>\nWorking with the Scrum Team<\/h2>\n
\n
\nHow the PO role is viewed by a team member.<\/li>\n
\nThe grooming meeting is possibly the most important one for the Product Owner.<\/li>\n
\nHow to handle longer-range planning.<\/li>\n
\nHow to work on bigger projects.<\/li>\n
\nLearn the agile way of structuring teams.<\/li>\n
\nThe project management side of the role.<\/li>\n
\nDetails about the two meetings that start and end the sprint.<\/li>\n<\/ul>\nWorking with Customers<\/h2>\n
\n
\nMake decisions during interactive activities with your customers (\u201cserious games\u201d).<\/li>\n
\nModel your users needs, for a more relevant product.<\/li>\n
\nGather data to better understand your users.<\/li>\n
\nUse mental models to understand your customer\u2019s worldview.<\/li>\n<\/ul>\nUser Experience<\/h2>\n
\n
\nA classic on product design and a precursor of the usability movement.<\/li>\n
\nThe key to a consumer product\u2019s success is making it intuitive to use.<\/li>\n
\nA new discipline combining agile, lean startup and user experience.<\/li>\n
\nThe title says it all.<\/li>\n<\/ul>\nOther resources<\/h2>\n
\n
\nThe guide is written by Scrum\u2019s creators: Ken Schwaber and Jeff Sutherland.<\/li>\n
\nOne of the reference books about Scrum and Agile.<\/li>\n
\n\u201cWhy do some products make the leap to greatness while others do not?\u201d<\/li>\n
\nI\u2019ve created a list of books for Product Owners on Amazon.<\/li>\n<\/ul>\nOur services<\/h2>\n
\n