Skip to main content
Project Management

Return to Answer

type fixed
Source Link
Ashok Ramachandran
Ashok Ramachandran
  • 11.1k
  • 1
  • 22
  • 50

Our organization relies heavily on GA asset development (we create simulations), so we include them in the daily scrums. Some are technically inclined (i.e. understand code) while others are not. Nonetheless, the GA work needs to integrate with the code so there are dependencies, technical constraints, etc. that need to be communicated and vetted.

It is not uncommon for other non-technical talent to be included in the daily scrums, such as content developers and QA. My rule of thumb is that if an individual ashas a card in play on the scrum board, they're included in the daily scrums.

Our organization relies heavily on GA asset development (we create simulations), so we include them in the daily scrums. Some are technically inclined (i.e. understand code) while others are not. Nonetheless, the GA work needs to integrate with the code so there are dependencies, technical constraints, etc. that need to be communicated and vetted.

It is not uncommon for other non-technical talent to be included in the daily scrums, such as content developers and QA. My rule of thumb is that if an individual as a card in play on the scrum board, they're included in the daily scrums.

Our organization relies heavily on GA asset development (we create simulations), so we include them in the daily scrums. Some are technically inclined (i.e. understand code) while others are not. Nonetheless, the GA work needs to integrate with the code so there are dependencies, technical constraints, etc. that need to be communicated and vetted.

It is not uncommon for other non-technical talent to be included in the daily scrums, such as content developers and QA. My rule of thumb is that if an individual has a card in play on the scrum board, they're included in the daily scrums.

Source Link
5280Angel
5280Angel
  • 11
  • 3

Our organization relies heavily on GA asset development (we create simulations), so we include them in the daily scrums. Some are technically inclined (i.e. understand code) while others are not. Nonetheless, the GA work needs to integrate with the code so there are dependencies, technical constraints, etc. that need to be communicated and vetted.

It is not uncommon for other non-technical talent to be included in the daily scrums, such as content developers and QA. My rule of thumb is that if an individual as a card in play on the scrum board, they're included in the daily scrums.