You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a PRD that leverages the existing work for this project and its planning to dive a level deeper on the technical aspects of the requirements
Create an architecture diagram that explains how the different interfaces, connections, and communication with the UI should work. There are some things we will have a good idea about and others that will be open questions. We need to clearly highlight where those open questions are.
🤔 Why it needs to be done
Before selecting a technical implementation we're going to take a step back and ensure we have thought through the needs and requirements first. Given that the spirit of overhauling orchestration is in reducing complexity the raison d'etre here is to not prematurely trade complexity for complexity of another kind.
🏗️ Acceptance Criteria
Given a technical consideration of solving problems with our tooling
When we've correctly identified and explicated its requirements
Then it is clearly laid out in a PRD and arc diagram
⚙️ Technical Notes
PRD to be produced
Arc diagram to be produced
📜 Additional context
None at this time
The text was updated successfully, but these errors were encountered:
🚧 What needs to be done
🤔 Why it needs to be done
orchestration
is in reducing complexity the raison d'etre here is to not prematurely trade complexity for complexity of another kind.🏗️ Acceptance Criteria
⚙️ Technical Notes
📜 Additional context
None at this time
The text was updated successfully, but these errors were encountered: