Skip to content

ETL to QE, Update 60, Project Management Strategy

Date: 2025-01-19

My documents and projects here in my personal wiki are not organized in a way that I can effectively understand let alone other people and that needs to change.

The Problem of Project and Task Documentation

I have recently come across the problem that any features get articulated in different places which cover the same functionality making it hard to know where to track where work is getting done.

For example Tickets are a great idea but when working on the Nostr Bot Daemon Framework there are many different parts,

And their corresponding tickets,

When it takes 5 minutes to figure out where your task is articulated we have a problem so let's fix that.

Remembering how the Nostr Chat bot project all started

Sometimes we Losing the forest for the trees. The road map, from before DDaemon 2025 Roadmap Rev. 0.0.1 was supposed to be something along the lines of,

To put things in Context we tried to put together a Nostr NIP05 Bot multple times

Ordered from most recent to oldest attempt * dentropy/nostr-nip05-server * dentropy/nostr-nip05-server-failed-POC * dentropy/cgfs * My old CGFS Tutorials repo I deleted * dentropy/ipfs-cid-tutorial * dentropy/Deterministic-IPNS-Generation-JS

The problem I had was Scope Creep, rather than making a simple NIP-05 POC that just worked I wanted to create an absolute provenance functional state machine that could track the input and output of every function and run in the browser or on a server then develop the Nostr NIP05 Bot as an application on top of that.

I ended up running into problems Losing the forest for the trees when it came to database in browser database selection. The choice of SQL verses LevelDB verses IndexedDB, verses, SQLite, verses RxDB, verses pglite became a never ending conversation that stopped any work from getting done.

It's funny that, here we are, 10 months later, and we now finally have a Nostr NIP05 Bot MVP. Knowing this fact 10 months ago would have scared me.

Moving Forward

We need some new behaviours moving forward if we want to cultivate what mememaps.net is all acount.

We should be deploying the Nostr NIP05 Bot on a regular basis.

We should have a roadmap and feature matrix for each Product, such as

Project Concept Hierarchy

  • Philosophy / Vision / OS
    • DDaemon
  • Protocol / Specification / Framework
    • CGFS
    • QE
  • Products / Set of Features / User Experience / Complex User Story / Complex User Journey
  • Epic / Features / User Story / User Journey
    • Slash Commands
  • Tickets

Outline

  • Is NIP05 Bot a Product?
  • How do we integrate User Journeys in there?
    • There should be a complexity threshold, for example QE requires an entire token system. A Token System itself is a product.
  • Where do User Stories Belong?
  • User Stories verses User Journeys
    • User Journeys are just more specific user stories
  • What is the difference between a Protocol and a Product?
    • One has a Specification that people can implement the other is just implemented and people interact with it.