Scribd Logo
Upload

Welcome to Scribd!

  • Product Development: Use Case of Ohanah v3, Event Management Extension For Joomla

    Uploaded by

    Тања Миња
    12 views11 pages
    This document discusses strategies for developing an event management extension for Joomla called Ohanah v3. It recommends focusing on weaknesses rather than competitors, spending time on core flows and optimizing for novice users. Estimates will likely be wrong so it's important to accept errors, stay within 70% of resources, and ask for help. Key performance indicators should track progress towards the vision, and feedback should target quality over quantity for in-depth insights.

    Original Description:

    Original Title

    Product-Development_Bojan-Popic.pptx

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document discusses strategies for developing an event management extension for Joomla called Ohanah v3. It recommends focusing on weaknesses rather than competitors, spending time on core flows and optimizing for novice users. Estimates will likely be wrong so it's important to accept errors, stay within 70% of resources, and ask for help. Key performance indicators should track progress towards the vision, and feedback should target quality over quantity for in-depth insights.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pptx, pdf, or txt
    12 views11 pages

    Product Development: Use Case of Ohanah v3, Event Management Extension For Joomla

    Uploaded by

    Тања Миња
    This document discusses strategies for developing an event management extension for Joomla called Ohanah v3. It recommends focusing on weaknesses rather than competitors, spending time on core flows and optimizing for novice users. Estimates will likely be wrong so it's important to accept errors, stay within 70% of resources, and ask for help. Key performance indicators should track progress towards the vision, and feedback should target quality over quantity for in-depth insights.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pptx, pdf, or txt
    of 11

    Product development

    Use case of Ohanah v3, event management extension for Joomla

    Competitive Research
    1. Concentrate on weaknesses
    2. Dont think too much about competition

    Product Roadmap

    nobody

    never

    WHEN
    all the time

    WHO
    everybody

    Features that some uses all the time


    Cost you development time
    Cost you testing time
    Cost you support time
    Cost you performance
    Bad UX for others

    nobody

    WHO
    everybody

    never

    WHEN
    all the time

    Product specification and development plan

    Spend time on flows


    Optimize for idiots (future yourself
    included)
    Dont be afraid of repetition

    Estimations

    You will be wrong - accept it


    Never go over 70% of your resources
    Ask for help

    KPI

    Are we closer to the vision?

    Feedback - who to ask?


    Quality over quantity
    Go for the depth and not the width

    Thanks :)

    You might also like