Datopian product "wiki" with strategy and plans for our products and infrastructure.
Move fast, release often, share publicly
Terminology
This document is about the kind of stuff we make and sell. The following definitions make discussion clearer.
- Stacks 📚 vs offers 🛒: stacks are stuff we "make", offers are stuff we "sell".
- Domains 🪣: categories for the kinds of stuff we make and sell. We'll distinguish three domains:
- 🌀 Portals
- 📦 DataHub (Next)
- 🛎️ Data Services.
- Offers fall into two classes: products and services.
- 🍎 Products are standardized in terms of features, pricing etc. Like an apple at a store.
- ✂️ Services are bespoke and vary from client to client like a haircut.
- 🚩 when we use the term Product it is a product offer. Product is an overused term. Going forward, reserve product for this specific case at least internally.
Product Overview as of 2024-01-11
Current Focus: DataHub Cloud 📦☁️
TODO: shape a plan of work.
Appendix: Stacks
Appendix: Historical Materials
Plans
- Product Plan Spring 2023 🚩 this is was a breakthrough moment where we got clear on most of the new stuff
Workflow
Created/Updated: 2024-04-09
This is an outline of the workflow of our product team.
Job stories
- Capture idea/bug: i have an idea, found a bug etc … what do i do?
- Shaping: …
- Shipping: I want to see what to work on next as the lead developer?
- Overview of backlog I am the product lead / CEO i want to see what is in the backlog and what progress we have made …
General shape-up process
Our Process
- What's missing here?
- difficult to know where we are in terms shipping etc. ✅2024-04-09 suggest we adopt terminology and concepts of https://basecamp.com/shapeup/3.4-chapter-13#work-is-like-a-hill re "scopes" and "hill diagram". And don't formally track given how small we are, just ask (or maybe use some emojis …)
- At present, don't have a shaped backlog ahead of a ship cycle …
- difficult to know where we are in terms shipping etc. ✅2024-04-09 suggest we adopt terminology and concepts of https://basecamp.com/shapeup/3.4-chapter-13#work-is-like-a-hill re "scopes" and "hill diagram". And don't formally track given how small we are, just ask (or maybe use some emojis …)
- Who selects for shaping? Daniela with Rufus mentoring and consulting
- Who does shaping? Depends on item e.g. is it tech or not. Generally, Ola with Rufus support on tech.
- Who does betting? Daniela with Rufus mentoring and consulting people
- Pattern: Inboxes rather than issues
- Everything goes into an inbox by default (or even your own inbox!)
- inbox for immediate issues/bugs with current release
- inbox for "ideas"
- we do NOT open issues for ideas or bugs immediately unless we are going to fix them right now …
- only when something is pulled from inbox for shaping does it get an issue (at that point a shaping issue)
- May separate bugs from features (inside the inbox, but the basic rule is dump first, process later!)
- it is also ok to periodically just throw stuff out. If it is important it will come back …
- Everything goes into an inbox by default (or even your own inbox!)
- 🚩 can have a prioritized ideas subsection of inbox (to save having to wade through everything everytime …)
- Where are things right now?
- Inbox? https://github.com/datopian/datahub-next/issues/246
- To Shape backlog? in the epic in "Shaping section" https://github.com/datopian/datahub-next/issues/276
- Where is to ship backlog? in the epic in "Implementation section" https://github.com/datopian/datahub-next/issues/276
- Don't worry about forgetting things
- If you really need to, put it in an inbox
