Product Owner: Difference between revisions

From Secure Group Wiki
Jump to navigation Jump to search
No edit summary
 
(37 intermediate revisions by 2 users not shown)
Line 1: Line 1:
In order to progress in our development path and Level Up or Step Up, our Product Owners must:</br>
The Product Owners are accountable for managing our product lifecycle, from evaluating and prioritizing requirements to aligning with Engineering teams to make sure features are delivered, and everything related to the go-to-market process is properly supported. They also make sure that the product roadmap, task prioritization, and backlog are efficiently managed.
* Meet the criteria of the Level & Step Chart for the chosen path ([[How_we_ensure_people%E2%80%99s_growth#Individual_Contributors_Path|Individual Contributors Path]] or [[How_we_ensure_people%E2%80%99s_growth#Management_Path|Management Path]])
*  Score at least a grade 4 in the [[KAI]] of the position in order to reach Level 3.</br>


In order to progress in Secure Group, it's essential that all the work done by them ensure alignment between our product vision, customer's needs, and business goals. To achieve that, they are also responsible for setting and monitoring product success metrics.


= [[KAI]] of the position =
Product Owners need to have a strong orientation for market trend analysis and the capability to translate them into product goals. Besides that, they need to ensure go-to-market readiness of new features and provide customer-side insights for our UX/UI processes.


<!-- JOB FRAMEWORK -->
= Progression=
<div class="grid two-columns">
In order to progress in our development path and Level Up or Step Up, our Product Owners must:
<div class="">
* Meet the criteria of the Level & Step Chart for the [[Management|Management Path]]
  <div class="box-header center">
* Demonstrate proficiency in the Product Owner Realm
== General Knowledge ==
 
  </div>
</br>
  <div class="box-content framework">
 
    <div class="center">
= Salary Grid =
{| class="wikitable"
All mentioned salary ranges represent the monthly income in Bulgarian Lev after taxes and deductions.
!rowspan="6"|'''Concepts'''
<div class="center">
|[https://en.wikipedia.org/wiki/Agile_software_development Agile]
{| class="wikitable"  
! rowspan="2" colspan="2" | Product Owner
! colspan="4" | Step
|-
|-
|[https://en.wikipedia.org/wiki/Balanced_scorecard Balanced Scorecard]
! 1
! 2
! 3
! 4
|-
|-
|[https://en.wikipedia.org/wiki/Planning Planning]
! rowspan="6" | Level
!1
|2.800
|3.100
|3.900
|4.800
|-
|-
|[https://en.wikipedia.org/wiki/Technology_demonstration Product Demo]
!2
|3.300
|4.600
|5.400
|6.300
|-
|-
|[https://en.wikipedia.org/wiki/Technology_roadmap Software Roadmap]
!3
|8.500
|8.800
|9.600
|10.500
|-
|-
|[https://en.wikipedia.org/wiki/Technical_writing Technical Writing]
!4
|-
|11.500
!rowspan="5"|'''Frameworks'''
|11.800
|[https://code.tutsplus.com/tutorials/android-sdk-common-android-components--mobile-20873 Android Components]
|12.600
|-
|13.500
|[https://en.wikipedia.org/wiki/Android_software_development#SDK Android SDK]
|-
|[https://en.wikipedia.org/wiki/Application_programming_interface API]
|-
|[https://en.wikipedia.org/wiki/Kanban_(development) Kanban]
|-
|[https://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]
|-
!rowspan="1"|'''Languages'''
|[https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-14 JQL]
|-
!rowspan="2"|'''Protocols'''
|[https://en.wikipedia.org/wiki/XMPP XMPP]
|-
|[https://en.wikipedia.org/wiki/Session_Initiation_Protocol SIP]
|-
!rowspan="15"|'''Softwares/Tools/Platforms - Usage'''
|[https://en.wikipedia.org/wiki/Android_Studio Android Studio]
|-
|[https://en.wikipedia.org/wiki/Bamboo_(software) Atlassian Bamboo]
|-
|[https://en.wikipedia.org/wiki/Bitbucket Atlassian Bitbucket]
|-
|[https://en.wikipedia.org/wiki/Confluence_(software) Atlassian Confluence]
|-
|[https://en.wikipedia.org/wiki/Jira_(software) Atlassian Jira]
|-
|[https://en.wikipedia.org/wiki/BambooHR BambooHR]
|-
|[https://marketplace.atlassian.com/apps/1212259/bigpicture-project-management-ppm?hosting=cloud&tab=overview Big Picture]
|-
|[https://count.ly/ Countly]
|-
|[https://crowdin.com/ Crowdin]
|-
|[https://docs.docker.com/engine Docker Engine]
|-
|[https://en.wikipedia.org/wiki/Kibana Gerrit]
|-
||[https://www.elastic.co/products/logstash Instabug]
|-
|[https://openstf.io/ OpenSTF]
|-
|[https://www.small-improvements.com/ Small Improvements]
|-
|[https://thycotic.com/ Workable]
|-
!rowspan="4"|'''Softwares/Tools/Platforms - Configuration'''
||[https://en.wikipedia.org/wiki/Bamboo_(software) Atlassian Bamboo]
|-
|[https://en.wikipedia.org/wiki/Confluence_(software) Atlassian Confluence]
|-
|[https://en.wikipedia.org/wiki/Jira_(software) Atlassian Jira]
|-
|[https://crowdin.com/ Crowdin]
|-
!rowspan="2"|'''Softwares/Tools/Platforms - Server Administration'''
|[https://en.wikipedia.org/wiki/Jira_(software) Atlassian Jira]
|-
!rowspan="1"|'''Languages (Idioms)'''
|Advanced English
|}
|}
  </div>
</div>
  </div>
</div>
</div>


<!-- JOB FRAMEWORK -->
= Realm =
<div class="">
[[File:PO_Realm.png|700px|center]]
  <div class="box-header center">
== Specific Knowledge ==
  </div>
  <div class="box-content framework">
    <div class="center">
{| class="wikitable"
!rowspan="9"|'''Concepts'''
|[https://en.wikipedia.org/wiki/Design_pattern Design Patterns]
|-
|[https://en.wikipedia.org/wiki/Version_control Version Control via Git]
|-
|Highload projects
|-
|[https://en.wikipedia.org/wiki/Integrated_development_environment IDE]
|-
|[https://en.wikipedia.org/wiki/Object-oriented_programming OOP]
|-
|[https://en.wikipedia.org/wiki/Content_management_system CMS]
|-
|[https://en.wikipedia.org/wiki/Representational_state_transfer REST]
|-
|[https://en.wikipedia.org/wiki/Web_performance Web Performance Experience]
|-
|[https://en.wikipedia.org/wiki/Internet_security Web Security]
|-
!rowspan="6"|'''Frameworks'''
|[https://en.wikipedia.org/wiki/Bootstrap_(front-end_framework) Bootstrap]
|-
|[https://en.wikipedia.org/wiki/PHPUnit PHPUnit]
|-
|[https://en.wikipedia.org/wiki/Selenium_(software) Selenium]
|-
|[https://en.wikipedia.org/wiki/Symfony Symfony]
|-
|[https://en.wikipedia.org/wiki/Vue.js Vue.js]
|-
|[https://en.wikipedia.org/wiki/Yii Yii]
|-
!rowspan="13"|Languages
|[https://en.wikipedia.org/wiki/Bash_(Unix_shell) Bash Script]
|-
|[https://en.wikipedia.org/wiki/PhantomJS#CasperJS CasperJS]
|-
|[https://en.wikipedia.org/wiki/Cascading_Style_Sheets CSS]
|-
|[https://en.wikipedia.org/wiki/HTML HTML]
|-
|[https://en.wikipedia.org/wiki/JavaScript JavaScript]
|-
|[https://en.wikipedia.org/wiki/JSON JSON]
|-
|[https://en.wikipedia.org/wiki/Less_(stylesheet_language) Less]
|-
|[https://en.wikipedia.org/wiki/PHP PHP]
|-
|[https://en.wikipedia.org/wiki/Python_(programming_language) Python]
|-
|[https://en.wikipedia.org/wiki/Sass_(stylesheet_language) SASS]
|-
|[http://thesassway.com/editorial/sass-vs-scss-which-syntax-is-better SCSS]
|-
|[https://en.wikipedia.org/wiki/SQL SQL]
|-
|[https://en.wikipedia.org/wiki/XML XML]
|-
!rowspan="6"|Libraries
|[https://en.wikipedia.org/wiki/Ajax_(programming) Ajax]
|-
|[https://faker.readthedocs.io/en/master/ Faker]
|-
|[https://en.wikipedia.org/wiki/Guzzle_(PHP_library) Guzzle]
|-
|[https://en.wikipedia.org/wiki/JQuery JQuery]
|-
|[https://en.wikipedia.org/wiki/React_(JavaScript_library) React.js]
|-
|[https://en.wikipedia.org/wiki/Twig_(template_engine) Twig]
|-
!rowspan="2"|Protocols
|[http://www.bubblecode.net/en/2016/01/22/understanding-oauth2/ Oauth2]
|-
|[https://en.wikipedia.org/wiki/JWt_(Java_web_toolkit) JWT]
|-
!rowspan="3"|Softwares/Tools/Platforms - Usage
|[https://en.wikipedia.org/wiki/Docker_(software) Docker Compose]
|-
|[https://en.wikipedia.org/wiki/MySQL MySQL]
|-
|[https://en.wikipedia.org/wiki/Nginx NGINX]
|-
!rowspan="4"|Softwares/Tools/Platforms - Configuration
|[https://en.wikipedia.org/wiki/Apache_Tomcat Apache Tomcat]
|-
|[https://en.wikipedia.org/wiki/Microsoft_Azure Microsoft Azure]
|-
||[https://en.wikipedia.org/wiki/MySQL MySQL]
|-
|[https://en.wikipedia.org/wiki/Nginx NGINX]
|-
!rowspan="2"|Softwares/Tools/Platforms - Server Administration
||[https://en.wikipedia.org/wiki/MySQL MySQL]
|-
|[https://en.wikipedia.org/wiki/Nginx NGINX]
|}
   </div>
   </div>
   </div>
   </div>
  </div>
  </div>
</div>
</div>
<!-- JOB FRAMEWORK -->
<div class="">
  <div class="box-header center">
= IT Knowledge =
  </div>
  <div class="box-content framework center">
    <div class="">
{| class="wikitable"
!System Administration
|-
!System Administration - Day to Day Ops
|-
!Android Development
|-
!Networking concepts
|}
  </div>
</div>
</div> <!-- grid -->
<!-- JOB FRAMEWORK -->
<div class="">
  <div class="box-header center">
= Secure Group Knowledge =
  </div>
  <div class="box-content framework">
    <div class="center">
{| class="wikitable"
!colspan="1"|Secure Group Knowledge
!rowspan="1"|What's Expected
!rowspan="1"|Impact
!rowspan="1"|Product
!colspan="1"|Minimum Grade
|-
!rowspan="6"|User Documentation
|rowspan="6"|Good, user-level knowledge regarding the product and its functionalities. From the user documentation, all employees across the company are required to be well aware of our solutions’ core features and functions such as the Password Advisor or how to send an automatic crash report.
|rowspan="6"|This knowledge helps us facilitate a user-centric approach internally, which we believe is essential to develop our business and solutions. The user documentation helps team members understand user behavior and needs more thoroughly and feel the impact of their everyday efforts.
|Secure OS
|4
|-
|SAS
|4
|-
|Secure Chat
|4
|-
|Secure Email
|4
|-
|Secure Vault
|4
|-
|Secure Manager
|4
|-
!rowspan="6"|Sales Documentation
|rowspan="6"|Employees should gain significant knowledge regarding the business side of '''Secure Group'''. They need to be aware of commonly used concepts in our day-to-day activities such as our business and distribution model, value proposition, selling prices, key selling points, and target audience.
|rowspan="6"|The information in the Sales Documentation supports employees in their daily routine. It conveys the overall business vision within the company. This documentation contributes to making employees aware of how our solutions are distributed, who are our key partners and target market to know exactly the people towards whom team members’ efforts should be aimed. Alignment on company-wide priorities is also achieved through clear communication of our value proposition and key selling points, helping everyone understand the things that matter most.
|Secure OS
|3
|-
|SAS
|3
|-
|Secure Chat
|3
|-
|Secure Email
|3
|-
|Secure Vault
|3
|-
|Secure Manager
|3
|-
!rowspan="6"|Support Documentation
|rowspan="6"|People within the company need to be aware of commonly occurring problems with our solutions. From the Support Documentation, employees should also extract general level knowledge regarding support processes, the issues that we’re currently having product-wise, and the approach to troubleshooting them.
|rowspan="6"|o The Support Documentation helps employees understand short-term priorities more clearly and communicate more openly why they’re needed. It also gives them general knowledge of how to spot and report a problem, which helps us facilitate a company-wide contribution to product development. Last but by no means least, it helps team members understand customers pains and behavioral patterns to strengthen our user-centric approach.
|Secure OS
|3
|-
|SAS
|3
|-
|Secure Chat
|3
|-
|Secure Email
|3
|-
|Secure Vault
|3
|-
|Secure Manager
|3
|-
!rowspan="6"|Functional Documentation
|rowspan="6"|Through the Functional Documentation, employees should get a thorough understanding of the solutions and their multiple features. People that work closely with the products must understand exactly how they function, how users interact with them, how to configure different settings, and what’s the expected behavior of different software solutions.
|rowspan="6"|o The information in the Functional Documentation helps employees whose work is closely connected with our solutions, to gain significant in-depth knowledge into their functionalities that far exceeds users‘ understanding. Such thorough product expertise helps us remain objective, evaluate market data more adequately, and constantly increase our internal expertise.
|Secure OS
|4
|-
|SAS
|4
|-
|Secure Chat
|4
|-
|Secure Email
|4
|-
|Secure Vault
|4
|-
|Secure Manager
|4
|-
!rowspan="6"|Technical Documentation
|rowspan="6"|Employees concerned with the Technical Documentation and more concretely - software development, must gain complete mastery over all solutions. Such people are regarded as technical experts and need to be well aware of data structures, relational databases, algorithms, programming languages, models, etc.
|rowspan="6"|The Technical Documentation is used to make sure people that are technically involved in product development have the required knowledge to perform their day-to-day tasks, optimize our solutions more easily, and support other teams with their in-depth expertise.
|Secure OS
|4
|-
|SAS
|4
|-
|Secure Chat
|4
|-
|Secure Email
|4
|-
|Secure Vault
|4
|-
|Secure Manager
|4
|-
|}
  </div>
</div>
</div> <!-- grid -->
= Salary Grid =
<div class="center">
{| class="wikitable"
!colspan="3"|Web Development
!colspan="4"|Step
|-
!rowspan="11"|Level
|-
!Individual Contributor Path
!Management Path
!1
!2
!3
!4
|-
!1: Web Developer
!-
|2.000 lv
|2.150 lv
|2.300 lv
|2.450 lv
|-
!2: Sr. Web Developer
!-
|3.000 lv
|3.150 lv
|3.300 lv
|3.450 lv
|-
!3: Software Engineer
!Manager
|4.000 lv
|4.150 lv
|4.300 lv
|4.450 lv
|-
!4: Sr. Software Engineer
!Sr. Manager
|5.000 lv
|5.150 lv
|5.300 lv
|5.450 lv
|-
!5: System Architect
!Head of
|6.000 lv
|6.150 lv
|6.300 lv
|6.450 lv
|-
!6: Sr. System Architect
!Director
|7.000 lv
|7.150 lv
|7.300 lv
|7.450 lv
|-
!-
!Sr. Director
|9.000 lv
|9.400 lv
|9.800 lv
|10.200 lv
|-
!-
!Chief of
|11.200 lv
|11.600 lv
|12.000 lv
|12.400 lv
|-
!-
!VP
|13.400 lv
|13.800 lv
|14.200 lv
|14.600 lv
|}

Latest revision as of 08:34, 2 May 2023

The Product Owners are accountable for managing our product lifecycle, from evaluating and prioritizing requirements to aligning with Engineering teams to make sure features are delivered, and everything related to the go-to-market process is properly supported. They also make sure that the product roadmap, task prioritization, and backlog are efficiently managed.

In order to progress in Secure Group, it's essential that all the work done by them ensure alignment between our product vision, customer's needs, and business goals. To achieve that, they are also responsible for setting and monitoring product success metrics.

Product Owners need to have a strong orientation for market trend analysis and the capability to translate them into product goals. Besides that, they need to ensure go-to-market readiness of new features and provide customer-side insights for our UX/UI processes.

Progression

In order to progress in our development path and Level Up or Step Up, our Product Owners must:

  • Meet the criteria of the Level & Step Chart for the Management Path
  • Demonstrate proficiency in the Product Owner Realm


Salary Grid

All mentioned salary ranges represent the monthly income in Bulgarian Lev after taxes and deductions.

Product Owner Step
1 2 3 4
Level 1 2.800 3.100 3.900 4.800
2 3.300 4.600 5.400 6.300
3 8.500 8.800 9.600 10.500
4 11.500 11.800 12.600 13.500

Realm

Retrieved from "https://managementmodel.info/index.php?title=Product_Owner&oldid=3529"