📖 Refinement Questions

Technical issues

• scope of the change
• if you e.g. add new field to an Entity - how many endpoints POST/GET will be affected? how easily you could test each of that path?
• how the new flow will be started? 
• by POST endpoint/AMQP event: what will trigger it (external/internal/our system; api/frontend)
• by CRON/manual script execution - how often? can we call it an "import"?
• which data from the current database are required to perform that functionality?
• in a case of happy path 
• in a case of error path (if there is any difference)
• does process need to be ASYNC POST? because someone from the other side needs to accept something manually and then the other system can send to us call through http endpoint.
• do we need to store new data? 
• should it be a new column in a existing table? Ask business if the new entity as a whole really is the same thing as previously saved in that table? (if the new data is something like a "type") 
• do we need then fill all historical data by db migration or CLI script/SQL update?
• should be a new table?
• do we need to do something in others team repository? do the faso making CR?
• do we need to ask DevOps team to do something with infrastructure? (e.g. SQS Queue, CRON)
• does it require Frontend/NoCode/Dashboard works? 
• does integration other Service (Internal/External) is involved in that feature?
• is it ready to integrate or we need to wait for the other team (e.g. has endpoint, is emitting events to the queue right now)?
• if it's not - they're blocked by something?
• it will be Query or Command (respectively getting data through endpoint or rather sending something to other service via HTTP/AMQP message)?
• Query - do we want to cache the response to increase response time? 
• do we have already done similar integration with that service that we could "copy/paste"?
• if not we need to: 
• get credentials,  
• get documentation, 
• prepare SDK to set up connection with that Other Service,
• have some Sandbox environment to testing
• cache Authorization key (optional),
• testing
• do we need to writes an e2e for that feature?
• if within the scope of the flow is communication with external service then at this point we got to have mocked that communication (endpoints) to write working e2e
• can we test it manually? When we think that we can do that can we throw some ideas for future tests?
• we may have a problem with request body encryption
• when feature in it's scope has connection with External Service we couldn't be able to restore specific state of that service even it's sandbox
• modifying endpoint POST/GET - it's contract change so if it's used by external client we need take consideration to versioning 
• documentation - do we need update:
• public API
• OpenAPI
• PostMan
• C4
• Notion/Confluence company pages which describes the flow of the new feature
• deployment
• could we split that feature into few MR?
• do we need blue/green deployment?
• do we need feature flag?

Business concerns

• who will use that feature? (internal or external users/system [e.g. CRON])
• who will benefit from this feature?
• how often it will be used (once per second/minute/day/month)?
• if it's once per hour we don't need to optimize it
• how will the user know about this functionality? do we need to learn users how to use that?
• which Domain Entity/Resource will be changed after execution this new flow (internal DB/external services)
• how we can call that new process?
• can we implement it now or we are blocked by
• work that we need to do in the first place 
• work of the different team (internal/external)