Roman:\u00a0When I began working with product managers in 2001 while introducing Extreme Programming at a healthcare company, product and Agile seemed worlds apart. The product management practices I encountered were very old-school and waterfall. I had a similar experience when I taught Scrum to product managers at a telco company in 2004. Back then I thought that product management would have to be reinvented to take full advantage of an Agile way of working. Luckily, this turned out to be unnecessary. But I still think that the profession has tremendously changed over the last ten years influenced by Scrum, Lean Startup, and Business Model Generation.<\/span><\/p>\n Q2. How can one be a balanced Product Leader instead of being a Feature Broker or Product Dictator? <\/strong><\/p>\n Roman:\u00a0A <\/span>balanced product leader<\/span><\/a> is someone who actively listens to and collaborates with the stakeholders but is not afraid to make a decision when no agreement can be reached. To put it differently, a balanced leader is neither a feature broker nor a product dictator\u2014neither a product person who relies on others to come up with ideas, mediates between different parties, and tries to broker a deal, nor someone who assumes that she or he knows best what needs to be done, makes all the product decisions, and expects others to fall in line.<\/span><\/p>\n Q3. Please share 5 myths about Product Owner\u2019s role existing in today\u2019s world. Why do you call them myths?<\/strong><\/p>\n Roman: Here are some common mistakes I see people make;<\/span><\/p>\n 1) The product owner is a tactical role responsible for managing the product backlog and working with the dev team. The strategic product decisions are made by someone else.<\/span><\/i> The opposite is true in my mind: To maximise the value a product creates, product owners should lead the strategic and tactical product decisions, should be outward and inwards-facing.<\/span><\/p>\n 2) A product owner is a type of project manager or team lead in Scrum.<\/span><\/i> Product owners should manage their products, not the team and process. Agile development teams should be self-organising, and every product owner should have a qualified <\/span>Scrum Master<\/span><\/a> or coach at her\/his side to support the team, teach the process, and facilitate organisational changes.<\/span><\/p>\n 3) You become a product owner simply by attending a two-day training course.<\/span><\/i> In reality, becoming a competent product owner is a learning journey that requires the individual to acquire and deepen <\/span>a whole range of skills<\/span><\/a>. This usually takes months and years, not days.<\/span><\/p>\n 4) A product owner asks the stakeholders for requirements and gets the dev team to implement them.<\/span><\/i> The opposite is true: Product owner and team are responsible for innovation. They regularly validate their ideas and collect user and stakeholder feedback and data on product increments.<\/span><\/p>\n 5) A product owner owns any type of asset ranging from a product portfolio to a component.<\/span><\/i> A product owner owns a <\/span>product<\/span><\/a>\u2014an asset that creates value for a group of users and for the company. It therefore must create a user benefit or address a user problem, and it must generate one or more measurable business benefits. Individuals who own parts of a product like a feature or component, or who own a product portfolio should not be called product owners. This avoids confusion and create clarity about the core responsibility of a product owner and the required skills.<\/span><\/p>\n Q4. What are the challenges you faced while leading through shared goals? How did you overcome the challenges?<\/strong><\/p>\n Roman: As the person in charge of a product, you are responsible for achieving product success. But to accomplish it, you usually rely on the help of the development team and <\/span>stakeholders<\/span><\/a>. At the same time, you can\u2019t tell the individuals what to do, and you are typically not in a position to offer a bonus, pay rise, or other incentives. This raises the question of how you can align people. Part of the solution is to establish a set of <\/span>shared goals<\/span><\/i><\/a>\u2014goals that people support and that help you progress your product. <\/span><\/p>\n The first trick with shared goals is to identify the right set of goals. I recommend using visionary, strategic, and tactical goals that are aligned and form a chain. The second trick is to get people\u2019s buy-in. Important goals\u2014typically visionary and strategic ones\u2014should be agreed upon. This means that everybody is happy to support them without reservation. Establishing such goals takes time, and it can be tempting to shortcut the decision-making process, set the goal, and ask people to get on with it. But this often leads to lack of support and difficult discussions later on. In the worst case, people follow their own, unaligned goals.<\/span><\/p>\n Q5. What inspired you to gather your thoughts and write a book? Tell us one thing that you enjoy most while writing a book and what is the one most taxing thing?<\/strong><\/p>\n Roman: Writing a book helps me reflect on my experience and consolidate my knowledge. At the same time, I hope that the readers will benefit from the contents! Before I started working on my last book <\/span>Strategize<\/span><\/i>, I felt that many product people lacked guidance on product strategy, and that there weren\u2019t many books available that focused on strategy and roadmaps for digital products. <\/span><\/p>\n I really enjoy the creative act of writing. But working on a book can be challenging\u2014just like any other bigger effort. There are difficult moments and setbacks such as slow progress, low motivation, an early review that indicates that more work is needed, to name just a few. These are great opportunities to learn and grow as a writer, product expert, and human being. But while experiencing these challenges, they don\u2019t feel particularly pleasant, and initially I am not very grateful for the experience!<\/span><\/p>\n Q6. According to you, what is the current state of Business Agility and Agile Product Management across globe? How the future looks like?<\/strong><\/p>\n Roman: I am not sure that my knowledge and experience is necessarily representative, but I think that many businesses still haven\u2019t fully realised what Agile and product are all about. In the worst case, project managers are rebranded as product owners, groups of people are called squads, and there are now chapters and tribes. <\/span><\/p>\n But when you take a closer look, little has changed. The product owners are not empowered and don\u2019t have the necessary skills; the organisation is still project-driven; and the teams are not cohesive, self-organising groups but collections of individuals.<\/span><\/p>\n Q7. Failure is an inevitable part of life. It is quite possible to fail while innovating. How can one cope up with failure and accept it?<\/strong><\/p>\n Roman: The solution is to stop seeing failure as something bad, and embrace what some people call a <\/span>growth mindset<\/span><\/i>. Unfortunately, that\u2019s easier said than done. I find that we can become very attached to success, to achieving and winning. Failure, then, is something we try to avoid, an unfortunate accident, rather than a mandatory part of the journey. But without failure, we don’t learn and grow\u2014neither as individuals, nor as organisations.<\/span><\/p>\n Q8. Share 3 things you wish for Agile Community.<\/strong><\/p>\n Roman: a) Kindness b) collaboration, and c) an open mind.<\/span><\/p>\n Q9. One question you think I should have asked you. Please answer that question too. <\/strong><\/p>\n Roman: A question I often get asked is, how can someone working as a product owner or product manager be more empowered? While part of the answer is to get management support and possibly establish a product management function in the company, there are two things you can do on your own: <\/span><\/p>\n First, you can improve our expertise and acquire the relevant knowledge and skills. Knowledge is power as they say, and the more competent you are, the more likely are people to trust and follow you.<\/span><\/p>\n Second, you can increase our referent power, which is linked to how we are as a person. Being empathetic, kind, honest, patient, humble, acting with integrity and keeping an open mind will earn you the trust and respect of others. It will make it more likely that people will follow your guidance. What\u2019s more, strengthening these qualities will make you a happier person too. How cool is that?<\/span><\/p>\n <\/p>\n <\/p>\n Roman Pichler is one of the leading voices in Agile Product Management space, having expertise in digital products. He is an Author, Trainer & Consultant on Lean, Agile and Scrum. We interviewed Roman to know about his journey in Agile Product Management, myths about Product Owner’s role and what he wishes for Agile Community. Let […]<\/p>\n","protected":false},"author":2,"featured_media":5113,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[9],"tags":[17,813,815,816,18,187,19,259,814],"class_list":["post-5112","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-interview-series","tag-agile","tag-agile-product-management","tag-business-agility","tag-failure","tag-innoroo","tag-innovation","tag-innovation-roots","tag-product-management","tag-roman-pichler"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2018\/05\/Roman-pichler-Interview-banner.png?fit=3125%2C1709","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8Rui8-1ks","jetpack-related-posts":[],"_links":{"self":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/5112","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/comments?post=5112"}],"version-history":[{"count":5,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/5112\/revisions"}],"predecessor-version":[{"id":6225,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/posts\/5112\/revisions\/6225"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/media\/5113"}],"wp:attachment":[{"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/media?parent=5112"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/categories?post=5112"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/innoroo.com\/blog\/wp-json\/wp\/v2\/tags?post=5112"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/i0.wp.com\/innoroo.com\/blog\/wp-content\/uploads\/2018\/05\/RomanPichler.jpg?resize=150%2C150\")
Roman Pichler is a leading product management expert specialised in digital products. He\u00a0has 15 years experience\u00a0in teaching product managers\u00a0and\u00a0product owners, and in helping companies improve their product management function.\u00a0Roman\u00a0is the author of the books\u00a0Strategize<\/em> and Agile Product Management with Scrum<\/em>, and he writes a popular blog\u00a0for product professionals.<\/p>\n","protected":false},"excerpt":{"rendered":"