{"id":29876,"date":"2023-12-01T10:11:22","date_gmt":"2023-12-01T09:11:22","guid":{"rendered":"https:\/\/scrum.sk\/product-owner\/product-owners-community\/"},"modified":"2024-01-30T10:38:11","modified_gmt":"2024-01-30T09:38:11","slug":"product-owners-community","status":"publish","type":"product_owner","link":"https:\/\/scrum.sk\/en\/product-owner\/product-owners-community\/","title":{"rendered":"Product Owners Community"},"content":{"rendered":"\n\t
\n\t\t
<\/div>\n\t\t\t\t\t
\n\t\t\t\"background-pattern\"\n\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t

Product Owners Community<\/h1>\t\t\t\t\t\t

Product Owners<\/h2>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t

Community<\/h2>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t

Professional education and preparation of internal standards for Product Owners. Customization of agile product ownership practices to the organization’s needs.<\/p>\n\t\t\t\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\tI am interested<\/a>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\tMore information<\/a>\n\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\"img\"\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t<\/section>\n\n\n
\n
\n
\n
\n\n
\n
\n
\n
\n \"icon\"\n <\/div>\n
\n
For whom<\/h5>
Organizations with communities of Product Owners.<\/h6> \n <\/div>\n <\/div>\n <\/div>\n <\/div>\n \n
\n
\n
\n
\n \"icon\"\n <\/div>\n
\n
Duration<\/h5>
Typically 12 meetings with community.<\/h6> \n <\/div>\n <\/div>\n <\/div>\n <\/div>\n \n
\n
\n
\n
\n \"icon\"\n <\/div>\n
\n
Form<\/h5>
Personal mentor support onsite and online at agreed-upon intervals.<\/h6> \n <\/div>\n <\/div>\n <\/div>\n <\/div>\n \n\n \n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n\n \n
\n
\n
\n
\n
\n
Our approach<\/h5>\n

\n Development \n \n Community of Product Owners <\/span>\n <\/h2>\n <\/div>\n <\/div>\n
\n
\n

Build an active community of Product Owners with the help of a community development program. We will add content focused on product strategy, ongoing preparation, and product delivery to your meetings.<\/p>\r\n\r\n

We will provide your community with pre-prepared materials for development, case studies, templates, tips for further education, references to literature, and videos.<\/p> <\/div>\n <\/div>\n <\/div>\n <\/div>\n<\/section>\n\n\n\n\n

\n
\n
\n
\n
\n \"roadmap\"\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n <\/section>\n \n\n
<\/div><\/div><\/div><\/section>\n\n\n
<\/div>\n\n\n\n

Product Owners Community<\/h2>\n\n\n\n

Thematic areas<\/strong><\/h2>\n\n\n\n
<\/div>\n\n\n\n
\n
\n

Topic<\/p>\n\n\n\n

Setting up<\/h4>\n\n\n\n

Role<\/strong><\/h4>\n\n\n\n

Setting the responsibilities of the Product Owner role in the organization. <\/p>\n\n\n\n

Identification of product types. <\/p>\n\n\n\n

Levels of product ownership. <\/p>\n\n\n\n

Minimum competencies of a Product Owner in the organization. <\/p>\n\n\n\n

Relationship to stakeholders, architecture, operations, management, team members, among Product Owners, and to the customer.<\/p>\n<\/div>\n\n\n\n

\n

Topic<\/p>\n\n\n\n

Process<\/h4>\n\n\n\n

Ongoing Requirement Preparation<\/strong><\/h4>\n\n\n\n

How to make the requirement preparation process transparent with a Portfolio Kanban board. <\/p>\n\n\n\n

Definition of the company’s requirement preparation process.<\/p>\n\n\n\n

Involvement of stakeholders in the preparation. <\/p>\n\n\n\n

Measuring delivery flow. <\/p>\n\n\n\n

Seven types of waste. <\/p>\n\n\n\n

Case studies. <\/p>\n\n\n\n

Setting up tools for project management.<\/p>\n<\/div>\n\n\n\n

\n

Topic<\/p>\n\n\n\n

Requirements<\/h4>\n\n\n\n

Requirements Breakdown<\/strong><\/h4>\n\n\n\n

Proper breakdown of requirements. Case studies from your organization. <\/p>\n\n\n\n

Collaborative requirement preparation and sharing within the community. <\/p>\n\n\n\n

Lessons learned. <\/p>\n\n\n\n

Building a case catalog.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

Topic<\/p>\n\n\n\n

Requirements<\/h4>\n\n\n\n

Requirements entry<\/strong><\/h4>\n\n\n\n

Meaningful requirements writing. User story, Job story formats <\/p>\n\n\n\n

Writing of acceptance criteria. <\/p>\n\n\n\n

How to identify epics. <\/p>\n\n\n\n

Tips for easier writing. What not to write in requirements.<\/p>\n\n\n\n

Collaboratively reframing your requirements into a more structured form increasing productivity for the whole team. <\/p>\n\n\n\n

Typical antipatterns and mistakes. <\/p>\n\n\n\n

How to set up JIRA for effective requirements writing. <\/p>\n\n\n\n

We’ll work with your specific requirements, not just examples.<\/p>\n<\/div>\n\n\n\n

\n

Topic<\/p>\n\n\n\n

Product<\/h4>\n\n\n\n

Product Definition<\/strong><\/h4>\n\n\n\n

How to properly prepare a product definition. <\/p>\n\n\n\n

Minimum Viable Product. <\/p>\n\n\n\n

Business modeling. <\/p>\n\n\n\n

Value proposition. <\/p>\n\n\n\n

Searching for requirements. <\/p>\n\n\n\n

Handling non-functional requirements. <\/p>\n\n\n\n

Personas.<\/p>\n<\/div>\n\n\n\n

\n

Topic<\/p>\n\n\n\n

Product<\/h4>\n\n\n\n

Objectives & Key Results<\/strong><\/h4>\n\n\n\n

Setting goals and key results. <\/p>\n\n\n\n

Hierarchy of goals at the organization, portfolio, program, product, team, and personal levels. <\/p>\n\n\n\n

Process of defining and evaluating goal status. <\/p>\n\n\n\n

Linking goals to the product backlog.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

Topic<\/p>\n\n\n\n

Product<\/h4>\n\n\n\n

Prioritization<\/strong><\/h4>\n\n\n\n

Prioritization perspectives. <\/p>\n\n\n\n

Rules and process of prioritization. <\/p>\n\n\n\n

Agreements on resolving potential conflicts of priorities. <\/p>\n\n\n\n

Various techniques for prioritizing requirements.<\/p>\n<\/div>\n\n\n\n

\n

Topic<\/p>\n\n\n\n

Case study<\/h4>\n\n\n\n

Dysfunctions of Product Owners<\/strong><\/h4>\n\n\n\n

Identifying your dysfunctions using a case study. <\/p>\n\n\n\n

Identifying areas for improvement, alignment, and defining standards.<\/p>\n<\/div>\n\n\n\n

\n

Topic<\/p>\n\n\n\n

Process<\/h4>\n\n\n\n

Metrics<\/strong><\/h4>\n\n\n\n

Selection and validation of metrics used. Adding meaning to metrics. <\/p>\n\n\n\n

Setting up electronic tools for metric automation. <\/p>\n\n\n\n

How to collect feedback and evaluate it. <\/p>\n\n\n\n

Customer and team satisfaction.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

Tool<\/p>\n\n\n\n

Setting up<\/h4>\n\n\n\n

JIRA<\/strong><\/h4>\n\n\n\n

Analysis and setup of JIRA. Simplification. <\/p>\n\n\n\n

Identifying incorrect or insufficient use of tools. <\/p>\n\n\n\n

Typical errors in tracking. Delivery tracking. <\/p>\n\n\n\n

Customizing JIRA.<\/p>\n<\/div>\n\n\n\n

\n

Topic<\/p>\n\n\n\n

Process<\/h4>\n\n\n\n

Budgeting<\/strong><\/h4>\n\n\n\n

Analysis and setup of JIRA. Simplification. <\/p>\n\n\n\n

Identifying incorrect or insufficient use of tools. <\/p>\n\n\n\n

Typical errors in tracking. Delivery tracking. <\/p>\n\n\n\n

Customizing JIRA.<\/p>\n<\/div>\n\n\n\n

\n

Topic<\/p>\n\n\n\n

Scaling<\/h4>\n\n\n\n

Portfolio Management<\/strong><\/h4>\n\n\n\n

Management of multiple products in the portfolio. <\/p>\n\n\n\n

Identifying value streams. <\/p>\n\n\n\n

Process of preparing the product portfolio. <\/p>\n\n\n\n

Monitoring implementation. <\/p>\n\n\n\n

Dependency coordination. <\/p>\n\n\n\n

Working with vendors. <\/p>\n\n\n\n

Portfolio status review. <\/p>\n\n\n\n

Planning program increments. Portfolio metrics.<\/p>\n<\/div>\n<\/div>\n\n\n\n

<\/div>\n\n\n\n
\n
<\/div>\n<\/div>\n\n\n\n
<\/div>\n\n\n\n
\n
\n
\n
\n\n
\n
\n

Arrange a personal meeting<\/h2>\n

Every business is unique, so we are committed to offering the most meaningful solution to your expectations.<\/p>\n <\/div>\n <\/div>\n\n

\n \n
\n

<\/p>