logoChat01.ai

In this activity, students will have the opportu...

Criado em: 12 de setembro de 2025

Respondido usando GPT-5 Thinking por Chat01

Pergunta

In this activity, students will have the opportunity to hone their skills in effective feedback and
feedforward in a context related to the world of technology. They will be divided into pairs and will have
to interpret and be creative in scenarios related to the IT field, in which they will have to discuss how to
give feedback and feedforward. The goal is to apply theoretical knowledge about effective feedback and
feedforward practically, develop skills in critical analysis, and clear and concise communication, and
demonstrate reflective thinking. They will also be encouraged to maintain a respectful attitude and
openness to think about the feedback and feedforward, using it as an opportunity for personal and
professional growth. The main objective is to practice using these techniques, develop communication
skills, and promote the exchange of constructive ideas.
Learning Objectives
By the end of this task, the studentshould be able to:
● Apply theoretical knowledge about effective feedback and feedforward in a practical manner.
● Develop skills in critical analysis.
● Provide effective feedback by identifying strengths, positives, and negativesin a concise, clear,
and objective manner.
● Utilize feedforward, offering constructive suggestionsforimproving those pointsin the future.
● Develop communication skills, expressing ideas and suggestions clearly and concisely.
● Demonstrate reflective thinking by analyzing the feedback and feedforward.
● Participate in constructive discussions and exchange ideas with peers.
Task Key Objective: Understand the difference and importance of both feedback (focusing on past
actions) and feedforward (focusing on future improvements) in software engineering practices.

Instructions:
● Find a colleague to work with. Both students will think about the feedback and feedforward to give
to the person who needs it (from the scenario) and represent a good attitude of the one who
receives the feedback and feedforward.
● Choose ONE scenario from the list below.
● Both studentsshould provide feedback and feedforward based on the scenario, applying the
techniques learned during the theoretical class.
● After discussing each scenario, write feedback and feedforward and make a role-play.
● Perform and present THAT scenario to the class (1-2 min), briefly showing how to give and receive
feedback and feedforward.

FAZ O SCRIPT para 2 minutos mais ou menos e aplica as praticas que foram faladas na aula pfv
Em portugues os script

Cenario
Problem Situation: In the bustling startup 'TechDream,' Pedro was known to produce
results swiftly. However, Maria, his team lead, found it challenging to decipher his code.
While it was functional, the lack of comments and unconventional methods made it a
puzzle for everyone else.

Pergunta

In this activity, students will have the opportunity to hone their skills in effective feedback and
feedforward in a context related to the world of technology. They will be divided into pairs and will have
to interpret and be creative in scenarios related to the IT field, in which they will have to discuss how to
give feedback and feedforward. The goal is to apply theoretical knowledge about effective feedback and
feedforward practically, develop skills in critical analysis, and clear and concise communication, and
demonstrate reflective thinking. They will also be encouraged to maintain a respectful attitude and
openness to think about the feedback and feedforward, using it as an opportunity for personal and
professional growth. The main objective is to practice using these techniques, develop communication
skills, and promote the exchange of constructive ideas.
Learning Objectives
By the end of this task, the studentshould be able to:
● Apply theoretical knowledge about effective feedback and feedforward in a practical manner.
● Develop skills in critical analysis.
● Provide effective feedback by identifying strengths, positives, and negativesin a concise, clear,
and objective manner.
● Utilize feedforward, offering constructive suggestionsforimproving those pointsin the future.
● Develop communication skills, expressing ideas and suggestions clearly and concisely.
● Demonstrate reflective thinking by analyzing the feedback and feedforward.
● Participate in constructive discussions and exchange ideas with peers.
Task Key Objective: Understand the difference and importance of both feedback (focusing on past
actions) and feedforward (focusing on future improvements) in software engineering practices.

Instructions:
● Find a colleague to work with. Both students will think about the feedback and feedforward to give
to the person who needs it (from the scenario) and represent a good attitude of the one who
receives the feedback and feedforward.
● Choose ONE scenario from the list below.
● Both studentsshould provide feedback and feedforward based on the scenario, applying the
techniques learned during the theoretical class.
● After discussing each scenario, write feedback and feedforward and make a role-play.
● Perform and present THAT scenario to the class (1-2 min), briefly showing how to give and receive
feedback and feedforward.

FAZ O SCRIPT para 2 minutos mais ou menos e aplica as praticas que foram faladas na aula pfv
Em portugues os script

Cenario
Problem Situation: In the bustling startup 'TechDream,' Pedro was known to produce
results swiftly. However, Maria, his team lead, found it challenging to decipher his code.
While it was functional, the lack of comments and unconventional methods made it a
puzzle for everyone else.

Pensamento

Creating feedback script in Portuguese

The user has asked for a script in Portuguese, roughly two minutes showing effective feedback and feedforward in a situation where Maria gives feedback to Pedro. I'll include clear lines for both, stage directions, and structures like opening, context setting, and techniques like SBI. I’ll also keep it concise with cues for a positive, productive interaction.

Creating feedback script in Portuguese

The user wants a 2-minute script in Portuguese for a feedback and feedforward scenario. I'll include both feedback and feedforward sections, stage directions, and time stamps. The tone should be casual yet appropriate for the topic. I'll write in neutral Portuguese to accommodate both Brazilian and European flavors. This script will cover Maria giving feedback to Pedro, and I’ll keep it concise. I'll label techniques like SBI and provide option for a written version with bullet points.

Finalizing script content

I'll stick to the 2-minute script, keeping the feedback and feedforward content. The tone will be concise but complete, with just the script provided, including relevant lines. I'll keep it clear, with everything well-structured, focusing on giving effective feedback and feedforward without overcomplicating things.

Finalizing feedback script

Maria opens by asking: "Pedro, do you have 5 minutes to discuss the last merge?" She acknowledges Pedro's strength: speed and delivering results. Then, using the SBI method, she gives feedback on a specific situation and its impact. Pedro responds positively, and Maria offers feedforward with clear steps, including setting SMART goals, establishing practices, and

Thought for 18s

Resposta

Aqui vai um roteiro de ~2 minutos (com falas e marcações) para o cenário da TechDream. Ele aplica técnicas de feedback (SBI: Situação–Comportamento–Impacto) e feedforward (sugestões práticas e acordos SMART), além de escuta ativa e atitude respeitosa.

Roteiro (Maria = líder, Pedro = dev)

[0:00 – 0:10 | Abertura & Permissão]
Maria: Pedro, tens 5 minutos para alinharmos sobre o último PR? Quero partilhar feedback e também combinar melhorias para os próximos.
Pedro: Claro! Quero muito ouvir e melhorar.

[0:10 – 0:40 | Feedback com SBI + reconhecimento]
Maria (reconhecimento): Primeiro, parabéns pela rapidez. O módulo de faturamento ficou pronto antes do prazo e passou nos testes de integração. Isso ajudou o time a desbloquear o deploy.
Maria (SBI):

  • Situação: No PR #128 do módulo de faturamento, ontem à tarde;
  • Comportamento: o código veio sem comentários, com nomes de variáveis abreviados e algumas abordagens fora do nosso padrão (ex.: funções aninhadas sem docstring);
  • Impacto: a equipa levou cerca de 2 horas a decifrar a lógica durante o code review, e ficou um risco de “bus factor” se só tu entendes o trecho.
    Pedro (escuta ativa): Entendi. Faz sentido. Podes dar um exemplo específico do que ficou mais difícil?

[0:40 – 1:05 | Exemplos específicos]
Maria: Por exemplo, a função calcNF() faz três coisas: valida, calcula impostos e formata a resposta. Sem comentários, foi difícil seguir o fluxo. E vx/dt como nomes não mostram intenção.
Pedro: Verdade. Optei pela velocidade e sacrifiquei clareza. Obrigado por apontar.

[1:05 – 1:40 | Feedforward (sugestões + acordo SMART)]
Maria: Para os próximos PRs, o que achas de combinarmos:

  1. Nomes explícitos (ex.: calcularImpostos() / validarEntrada());
  2. Docstrings curtas por função (1–2 linhas sobre “o quê/por quê”);
  3. Comentários só onde há decisão não óbvia;
  4. Seguir o nosso guia de estilo (linters + convenções);
  5. Checklist no PR template: “nomes claros”, “docstrings”, “separa responsabilidades”.

Acordo SMART:

  • S: No próximo PR, separar funções por responsabilidade e incluir docstrings básicas.
  • M: Mediremos pelo tempo de review ≤ 30 min e 0 pedidos de clarificação de nomes.
  • A: Posso partilhar um snippet de docstring e um exemplo de nomes claros.
  • R: Alinha com nosso padrão e reduz manutenção.
  • T: Já no PR de hoje; e manter nos próximos 2 sprints.

Pedro (compromisso): Fechado. Hoje mesmo refatoro calcNF() em funções menores, renomeio variáveis, adiciono docstrings e marco-te no PR. Posso também criar um snippet de docstring para o time.
Maria: Ótimo! E amanhã fazemos um pair de 20–30 min para revisar juntos. Pode ser às 10h?
Pedro: Perfeito.

[1:40 – 2:00 | Fechamento & reforço positivo]
Maria: Obrigada pela abertura, Pedro. A tua rapidez é uma força — com estas melhorias de legibilidade, o impacto vai ser ainda maior.
Pedro: Valeu pelo feedback direto e respeitoso. Obrigado pelas sugestões práticas — vou aplicar já.

(Opcional para entregar por escrito)

Feedback (passado):

  • Força: entrega rápida e testes passando; desbloqueou deploy.
  • Ponto a melhorar: falta de comentários/docstrings, nomes abreviados e métodos fora do padrão no PR #128 aumentaram tempo de review e risco de manutenção.

Feedforward (futuro):

  • Adotar nomes explícitos, docstrings curtas, comentários apenas onde há decisão não trivial, seguir guia de estilo e usar checklist no PR template.
  • Meta: no próximo PR, tempo de review ≤ 30 min e 0 pedidos de clarificação de nomes; manter prática nos próximos 2 sprints.
  • Apoios: snippet de docstring, pair de 20–30 min amanhã às 10h.

Pronto! É só ensaiar com tom calmo, contacto visual e pausas curtas. Boa apresentação! 🎭

Compartilhar esta Q&A