Домой United States dc3 United States software in english pdf The Product Mindset

The Product Mindset

258
0
ПОДЕЛИТЬСЯ

If you are filling a position for a Product Owner in your organization, you may find the following interview questions useful to identify the right candidate.
Join the DZone community and get the full member experience. If you are looking to fill a position for a Product Owner in your organization, you may find the following 82 interview questions useful to identify the right candidate. This 8th set of Product Owner interview questions addresses the product mindset. The questions are derived from my sixteen years of practical experience with XP and Scrum, serving both as Product Owner and Scrum Master, and interviewing dozens of Product Owner candidates on behalf of my clients. So far, this Product Owner interview guide has been downloaded more than 10,000 times. According to the Scrum Guide, Product Owners have a vital role in the value creation process of the Scrum team: Source: Scrum Guide 2020. (The aggregation is taken from the Scrum Guide 2020 Reordered.) There is a reason why some refer to the Product Owner role as the “Achilles heel” or the “single wringable neck” of the Scrum team. Take out the Product Owner, either by organizational design or choosing the wrong candidate, and Scrum mutates into a pretty solid Waterfall 2.0 process. Becoming an agile, learning organization focused on creating customer value is about developing a product mindset everywhere, from the individual to the C-level. Employing Scrum can be a major stepping stone on this journey when the management empowers Product Owners and is not merely regarding Scrum as a delivery means to ship more features, products, and services within the constraints of the iron (project) triangle. Again, a fully formed and empowered Product Owner is crucial for a transformation success at that level. The following set of questions regarding the product mindset is designed to better understand a candidate’s perspective: Do they probably have what it takes to fill the shoes of the Product Owner role? «Looking back at your professional experience, can you name some first principles of a Product Owner with a product mindset?» This question allows the Product Owner candidate to reflect on their core beliefs of product management in general and the Product Owner role in particular. My top three choices of the first principles of the product mindset are: «You have worked with Product Owners (and product managers) in the past. How did the successful ones master the challenges of the role? Moreover, where did the less successful ones fail?» In my experience, successful Product Owners manage to split their time between different responsibilities and stakeholders without getting lost in details or failing to communicate appropriately while guiding everyone in the right direction, accomplishing the product vision. The key to achieving this level of alignment among the critical stakeholders is that they know how to delegate decisions while being transparent about the underlying system. Moreover, they include everyone at a meaningful level in the subsequent communication and collaboration, respectively, using the “vision, validation, value” approach. A less successful PO typically fails to have a product mindset and act as a team player. They fail at being product leaders. Instead, they are typically stuck in the scribe mode, refusing to delegate work that others can perfectly handle for them. For example, there is no reason why a PO would create and write all Product Backlog items themselves. In my experience, Developers can author PBi very well. Also, they tend to shield the rest of the Scrum team from communicating with stakeholders, namely customers and users. Establishing these team-internal functional silos (developers develop and do not talk to customers) often lowers innovation and productivity. Generally, they tend to create a bubble for themselves where falling victim to confirmation bias is not uncommon. They start loving their solution instead of the customers’ problem. Additionally, less successful Product Owners also tend to invest less in creating a product mindset throughout the organization. For example, they rely less upon joined work sessions with stakeholders like user story mapping, value stream mapping, or impact mapping. Also, they are less transparent about the status quo and where the Scrum team is heading. «Your new product proves to be very desirable in the market, and your organization—and hence the number of Scrum teams and stakeholders—is increasing rapidly in size. So, how do you preserve a product mindset as the responsible Product Owner?» Here, the candidate should point at the importance of embracing empiricism, self-management, and autonomy to deliver value to customers within the constraints of the organization while creating a sustainable return on investment for the latter: «In what ways can you support your personal growth as a Product Owner if your organization is still stuck in the old ways and far from developing a product mindset?» Even the longest journey starts with the first steps. If the “Product Owner” position is currently that of a glorified scribe taking requirements from stakeholders, and you aim to move to the entrepreneur level, I would at least explore the following steps: «How can you help other Scrum team members, namely the Developers, develop a product mindset?» Speaking with John Doerr, you want missionaries, not mercenaries on your team. To achieve that state, I would recommend taking the following steps: Please note that not all Developers feel comfortable with the idea of investing much time in communicating or collaboration with stakeholders while neglecting to build the product or service. (Some just like to solve puzzles all day long — which is okay as you cannot force people to get involved in these activities.) «So, embracing a ‘customer problem first’ perspective, thus developing a product mindset throughout the organization, seems to be a good bet to create value for everyone. How would you engage with different groups of stakeholders in the process? How have you done so successfully in the past?» The question is designed to provide the Product Owner candidate with room to share their experience and shine. Also, it is about understanding whether they have a holistic approach to stakeholder communication and what drives a stakeholder to interact with a Scrum team. Interacting comes in many different forms, from exercising control to pursuing goals (probably also personal agendas) to being kept in the loop. The candidate should have explored some of the following approaches to stakeholder engagement: Scrum has always been a pragmatic business, and to succeed in this mindset, candidates need to have a passion for getting their hands dirty. While the basic rules are trivial, getting a group of individuals with different backgrounds, levels of engagement, and personal agendas, to continuously deliver value by creating a great product is challenging. The larger the organization is, the more management level there are, the more likely failure in one of its many forms is lurking around the corner. The Product Owner interview questions are not necessarily suited to turn an inexperienced interviewer into an Agile expert. However, they support figuring out what candidate has been working in the agile trenches and who’s more likely to be an imposter. (You should avoid inviting candidates from the latter category to a trial.) Therefore, it’s probably a good idea to look for a pragmatic veteran who has experienced failure—and success—in other projects before and the scars to prove it. Published at DZone with permission of Stefan Wolpers, DZone MVB. See the original article here. Opinions expressed by DZone contributors are their own.