Closed saurabhsainani closed 1 year ago
The aim of the issue seems right, with the ability to interact with charts and key model @saurabhsainani, maybe change "non technical" to business stakeholders?
Estimation of effort:
It will involve quite a bit of re engineering and learning of some new concepts,
Acceptance Criteria:
The charts and key model outputs are presented in an interactive format.
[ Achievable, the first step will involve making a simple chart that works with interactive dropdowns]
Non-technical stakeholders can easily navigate and explore the charts and model outputs.
[That can happen once the plotly dashboard is hosted on a server. Can provide pngs/jpgs of the dashboard to preview in the coming few weeks. ] .
The charts and model outputs are visually appealing and effectively communicate the insights.
[ Yes, agree on this.]
The user interface is accessible and supported on various devices and screen sizes.
[ I am unable to comment on this point just yet, as I will have to test this and also learn on this works for plotly. In short, I dont have knowledge yet to make this happen.]
-The user interface has been tested and validated with representative non-technical stakeholders to ensure it meets their needs and expectations.
[Yes, agree on this. For this to work, I need to host the work and aligns with my previous point on hosting on a server. ]
Feedback from non-technical stakeholders has been incorporated to improve the usability and effectiveness of the charts and model outputs.
[ Yes, no issues with this going forward. It will also become clear whether plotly-dash is the right choice of tooling for this to work. We might have to pivot to a different tooling in case plotly -dash becomes too cumbersome to make it functional.]
- The aim of the issue seems right, with the ability to interact with charts and key model @saurabhsainani, maybe change "non technical" to business stakeholders?
Done
- Estimation of effort:
It will involve quite a bit of re engineering and learning of some new concepts,
- Specifically callbacks in dash (to allow interactivity). My estimation is 2-3 weeks of work.
- To enable sharing of the dashboard in dash involves hosting the app on a server. I estimate a further 2-3 weeks for this process.
We can do a relative estimating exercise using a concept of story points that might be helpful to estimate the effort required, not just for this feature but all user stories going forward. We can discuss this when we connect next?
- Acceptance Criteria:
- The charts and key model outputs are presented in an interactive format.
- [ Achievable, the first step will involve making a simple chart that works with interactive dropdowns]
- Non-technical stakeholders can easily navigate and explore the charts and model outputs.
- [That can happen once the plotly dashboard is hosted on a server. Can provide pngs/jpgs of the dashboard to preview in the coming few weeks. ] .
- The charts and model outputs are visually appealing and effectively communicate the insights.
- [ Yes, agree on this.]
- The user interface is accessible and supported on various devices and screen sizes.
- [ I am unable to comment on this point just yet, as I will have to test this and also learn on this works for plotly. In short, I dont have knowledge yet to make this happen.]
We can remove this from the acceptance criteria for now? As this is not an immediate priority?
-The user interface has been tested and validated with representative non-technical stakeholders to ensure it meets their needs and expectations.
- [Yes, agree on this. For this to work, I need to host the work and aligns with my previous point on hosting on a server. ]
- Feedback from non-technical stakeholders has been incorporated to improve the usability and effectiveness of the charts and model outputs.
- [ Yes, no issues with this going forward. It will also become clear whether plotly-dash is the right choice of tooling for this to work. We might have to pivot to a different tooling in case plotly -dash becomes too cumbersome to make it functional.]
We can do a relative estimating exercise using a concept of story points that might be helpful to estimate the effort required, not just for this feature but all user stories going forward. We can discuss this when we connect next?
Okay, sounds good to me.
We can remove this from the acceptance criteria for now? As this is not an immediate priority?
Yes, I feel we could do away with this for now.
User story :The charts and key model outputs are presented in an interactive format:
Attaching here a web capture:
**1. I have been able to host the output charts on a server now: https://marketingmixmodelling-example-v7cxq7rr2a-ts.a.run.app/
Estimation of effort
TBD
Acceptance criteria