Please enable JavaScript.

Coggle requires JavaScript to display documents.

Product Tech Core (Philosophy (Clean code is good code, write code that…

- - - - what was done yesterday
      - what will I do today?
      - is there any impediment keeping me from concluding a task?
      - 15 minutes long
      - dev team (PM optional)
    - - What were the increments in the product developed within the iteration ?
      - further clarification over business rules or functionality is needed?
      - 30 to 60 minutes long
      - Is there any change in priority?
        what is the new priority?
      - dev team + PM
      - output: PM/customer validation
      - when: at the end of a cycle
    - - what went well?
      - what needs improvement?
      - output: actions to take to improve.
        with person in charge and date to do it
      - 30 minutes long
    - - what is the main goal for the next cycle/iteration/sprint?
      - what are the stories/functionalities/use-cases to be developed during the cycle?
      - is there any additional setup?
  - - - High level business rules
      - PM is responsible for building it
      - low fidelity sketches
      - general product info
      - main timeline
    - - Ubiquitous language (should be reflected in every document or conversation related to the product)
      - Bounded Product Context
      - entities and value objects definitions
      - Use-cases logics (diagrams, etc)
      - tech stack definition
      - Services definitions (C4 Model)
      - what will be logged and when?
      - dev team is reponsible for building it
      - live prototyping (Figma, Marvel, Sketch, etc)
      - output: document per se, Stories, high fidelity model
  - - - 02 or more daily merges to dev/main is awesome
      - No daily merge to dev/main is already a potential problem
      - 01 daily merge to dev/main is fine