Content
View differences
Updated by Niels Lindenthal about 4 years ago
<figure class="image op-uc-figure" style="width:50%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/32745/content"></div></figure>
# User Problem
## User
_What persona, persona segment, or customer type experiences the problem most acutely?_
* Project manager
* Project member
* Product owner
* Open source community member
* User/customer
## Problem
_What problem or job does the user have?_
* It is difficult for the product owner to present their roadmap decisions. A work package list is not simply not a good way to present this information.
* The current roadmap view has some flaws and bugs.
## Pain
_What is the primary workaround that users perform that we could remove or replace? Why is it painful?_
* The roadmap information is manually copied over to other presentation tools like Powerpoint.
* Those exported information is always outdated.
# Business Case
## Reach
_About how many users, customers or potential customers currently have this problem? (Low / Worst Case)_
* Every project team that follows an iterative process.
* Product development
* System development
* Not really useful for traditional waterfall process models.
## Impact
_Among relevant customers or prospects, how much value do they get from a comprehensive solution to this problem? (Conservative case)_
* It does not really change people work with OpenProject.
* However it really changes the way the tool is perceived in the upper management (wow, now I really understand what is going on in my projects).
## Confidence
_What are the top risk factors that could inhibit our ability to deliver this solution? Please consider how we can mitigate these risks._
* Technically it seems pretty straight forward.
* We have all the API endpoints.
* We have all the admin views to edit the content
* Versions
* Work package
* Types
## Urgency and Priority
_What is the relative priority of this opportunity in your backlog? What tradeoffs must you make? Is there a hard deadline or could this wait?_
* It is not the most urgent topic. It is rather a relatively easy to implement project since most of the conceptual work is already done.
* Also a lot of the CSS already can be reused from the widget in the webpage.
## Solution
_How do we solve the user’s problem. What is our “pain killer”? What must we achieve in the first version of the solution in order to achieve value for the user?_
* We make the Roadmap a separate module which can be activated/deactivated by project <mention class="mention" data-id="40173" data-type="work_package" data-text="#40173">#40173</mention> data-text="#40173">#40173</mention>
* We replace the existing view.
## Out of Scope for the MVC
_What should NOT be in the minimal viable change, and can be considered for future iterations? Why? Please order them by importance._
* Read only (not create, update, delete)
* Drag and drop
* In-line editing of the content
* Creating new versions
* Adding work packages to versions
* Having target dates for versions such as Q3 2022.
## Differentiation
_What do you believe will differentiate us from the current experience or competitive experiences?_
* None of the open source tools have nicely styled view like this.
## Next iteration
_What is the next solution that would allow us to release meaningful customer value quickly?_
* Create, update, delete versions.
# Launch and Growth
## Measures
_How will you know you solved the problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the solution?_
* Number of projects that have the module activated.
* Number of projects that deactivate the module
* Number of page views compared to other views.
## Messaging
_If you were to write a press release, how would you describe the value to customers?_
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head">Headline</th><td class="op-uc-table--cell">OpenProject now presents project Roadmaps in a new module</td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head">First Paragraph</th><td class="op-uc-table--cell">Project teams can now easily create nicely style project Roadmaps to present their plans to a wider audience.</td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head">Customer Quote</th><td class="op-uc-table--cell"><blockquote class="op-uc-blockquote"><p class="op-uc-p">I can now easily inform my management and our customers about our Roadmap decisions. Before we had the new roadmap view I had to manually copy this over to Powerpoint and to our website. Now I can share the link and everybody has the latest information.</p></blockquote></td></tr></tbody></table></figure>
## Go to market
_How are you planning on getting this into users' hands?_
* E-Mail
* In app notifications
# User Problem
## User
_What persona, persona segment, or customer type experiences the problem most acutely?_
* Project manager
* Project member
* Product owner
* Open source community member
* User/customer
## Problem
_What problem or job does the user have?_
* It is difficult for the product owner to present their roadmap decisions. A work package list is not simply not a good way to present this information.
* The current roadmap view has some flaws and bugs.
## Pain
_What is the primary workaround that users perform that we could remove or replace? Why is it painful?_
* The roadmap information is manually copied over to other presentation tools like Powerpoint.
* Those exported information is always outdated.
# Business Case
## Reach
_About how many users, customers or potential customers currently have this problem? (Low / Worst Case)_
* Every project team that follows an iterative process.
* Product development
* System development
* Not really useful for traditional waterfall process models.
## Impact
_Among relevant customers or prospects, how much value do they get from a comprehensive solution to this problem? (Conservative case)_
* It does not really change people work with OpenProject.
* However it really changes the way the tool is perceived in the upper management (wow, now I really understand what is going on in my projects).
## Confidence
_What are the top risk factors that could inhibit our ability to deliver this solution? Please consider how we can mitigate these risks._
* Technically it seems pretty straight forward.
* We have all the API endpoints.
* We have all the admin views to edit the content
* Versions
* Work package
* Types
## Urgency and Priority
_What is the relative priority of this opportunity in your backlog? What tradeoffs must you make? Is there a hard deadline or could this wait?_
* It is not the most urgent topic. It is rather a relatively easy to implement project since most of the conceptual work is already done.
* Also a lot of the CSS already can be reused from the widget in the webpage.
## Solution
_How do we solve the user’s problem. What is our “pain killer”? What must we achieve in the first version of the solution in order to achieve value for the user?_
* We make the Roadmap a separate module which can be activated/deactivated by project <mention class="mention" data-id="40173" data-type="work_package" data-text="#40173">#40173</mention>
* We replace the existing view.
## Out of Scope for the MVC
_What should NOT be in the minimal viable change, and can be considered for future iterations? Why? Please order them by importance._
* Read only (not create, update, delete)
* Drag and drop
* In-line editing of the content
* Creating new versions
* Adding work packages to versions
* Having target dates for versions such as Q3 2022.
## Differentiation
_What do you believe will differentiate us from the current experience or competitive experiences?_
* None of the open source tools have nicely styled view like this.
## Next iteration
_What is the next solution that would allow us to release meaningful customer value quickly?_
* Create, update, delete versions.
# Launch and Growth
## Measures
_How will you know you solved the problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the solution?_
* Number of projects that have the module activated.
* Number of projects that deactivate the module
* Number of page views compared to other views.
## Messaging
_If you were to write a press release, how would you describe the value to customers?_
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head">Headline</th><td class="op-uc-table--cell">OpenProject now presents project Roadmaps in a new module</td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head">First Paragraph</th><td class="op-uc-table--cell">Project teams can now easily create nicely style project Roadmaps to present their plans to a wider audience.</td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head">Customer Quote</th><td class="op-uc-table--cell"><blockquote class="op-uc-blockquote"><p class="op-uc-p">I can now easily inform my management and our customers about our Roadmap decisions. Before we had the new roadmap view I had to manually copy this over to Powerpoint and to our website. Now I can share the link and everybody has the latest information.</p></blockquote></td></tr></tbody></table></figure>
## Go to market
_How are you planning on getting this into users' hands?_
* In app notifications