Jump to content
Toggle sidebar
UNITApedia
Search
English
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Talk
Contributions
Navigation
Main Page
User Guide
Viewpoints
Structural
Strategic
Beneficiary
Semantic
Infrastructure
Data
Beneficiaries
UNITA Participants
GEMINAE
Collectives
Agile Management Guide
Quality Management Process
Tools
What links here
Related changes
Special pages
Page information
Page values
In other languages
Editing
UNITA Agile Management Guide
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
More
Read
Edit
Edit source
View history
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== Ideas for team-based feedback ==== Agile approaches to feedback encourage collaborative methods. Retrospectives are used by the team as a way to pause, consider their performance and discuss ways to continually improve. This technique is based on American writer and therapist Virginia Satir and colleagues’ work which explores the past in order to improve the future (Satir, Banmen, Gerber and Gomori, 1991). In a retrospective, four questions can be used to surface and communicate issues: * What went well? * What didn’t go so well? * What have I learned? * What still puzzles me? (Source: Lyons and Waite, 2013) Here are some further factors to remember when planning feedback: * '''Make room in the plan''': How often is it appropriate for your team to carry out this type of reflection? * '''Action the learning''': How will the learning from the feedback be fed into the next work phase? What needs to change? * '''Deal with the issues''': How can you solve the things that still cause puzzlement? * '''Celebrate the successes''': How do you recognise and reward team success? It is important to remember that feedback is not about attributing blame. Both teams and individuals will be seeking feedback in order to gain awareness of themselves and how they are performing, and to use this for learning. Individual and team feedback should also be clear and ideally everyone should contribute.
Summary:
Please note that all contributions to UNITApedia are considered to be released under the Creative Commons Zero (public domain) (see
UNITApedia:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Debug data: