Please enable JavaScript.

Coggle requires JavaScript to display documents.

The professional product owner (Strategy (Value: means money for the…

- - - - Attention points to measure
        
        Efficiency according to your needs, not the other's practices
        
        Vision to be clear to everybody
        
        Incenvite to be value based, non corruptible
      - Metric types
        
        Delivery metrics:operational efficiency
        
        Owner metrics: business/value efficiency
    - - Current value
        
        Revenue per employee
        
        Product cost ratio
        
        Employee satisfaction
        
        Customer satisfaction: net promoter score see p 72
      - Time-to-market
        
        Release frequency: see the chart p.74
        
        Release stabilisation: as short as possible
        
        Cycle time = development + release stabilisation (Lead time from the customer asking to product being delivered)
        
        On-product index: Time developers work on the same initiative. switching brings delay and dissatisfaction
      - Ability to innovate
        
        Installed version index: How many of the customers are at the latest version: High absorbtion cost (time to install, new HW, training, data migration, pilot) hinders
        
        Usage index: which features used and HOW? see p 79
        
        Innovation rate: attention to technical depth. caused by non-automated tests and bad code quality. This blocks innovation. See p 82
        
        Defects
      - Measuring KVMs
        
        Track metrics: spider or scoreboard style
        
        Where your money goes (ROI): innovation rate, on-product index, usage index, installed version index
        
        Negative value see p. 88
        
        visible: buggy software, down time, low performance
        
        invisible: feature not being used
        
        Value neutrality: challenge your metrics not to be corrupted (Cobra effect)
  - - - stakeholder feedback
        
        Engage: implement stakeholders feedback to the process
        
        Correcting course: give space to corrections by showing the product as much as possible
        
        Create accountability with transparency
      - marketplace feedback: market response is the final validation
        
        minimum value product validation
        
        Technical: is it technically feasible?
        
        Market: are they willing to pay? Go fast and see. attention to sunk costs
        
        Kano: Basic, performance and excitement features must be present in an MVP
        
        MVP types
        
        Promotional: UI mock-ups, videos, viral campaigns
        
        mining MVP: survey, PoC, disposible data collection methods
        
        Landing page
        
        Wizard of OZ: feels functioning to user, handcrafted in reality
        
        Single feature MVP: Release a function and experiment