Segue abaixo feedback do workshop:
Felipe Furtado
You can find more feedback here:
http://sites.google.com/site/kanbanandbeyond/recent-feedback
I did collect feedback at the session itself. I followed the same style used on QCon Sao Paulo last year. At the end of the session I had a bow, a few pen and cards (blue, yellow and pink; respectively great, medium, bad). The workshop attendees could write a few lines of feedback on the chosen card and drop it at the bow.
Here is the feedback written on these cards (in no particular order):
1. Make reusable cards. It was too much work to prepare, and I will not be able to reuse these cards.
2. Add a mark for amount of work completed in each card (50% done and 100% done)
3. Add a timer for each half day (for example: 1 minute for each half-day)
4. Keep the same numbers of people involved (1 BA, 5 Devs, 2 testers), but reduce the number of people making decisions on who should work in which card and stage (at most 3 people for each team).
5. Time box the activity
6. Have enough time for discussing the results (10 minutes at the end)
7. Have the card wall for each team already prepared on each team table. This should include the cards already on play on day 1 (now renamed to day 3). The theory on limits and targets is already covered during the presentation.
8. Have avatar for each team member ready (BAs, Devs and testers)
9. Simplify the rules (consolidate it), and have it visible at the wall
10. Have a calendar to show the days passing by (again, visible on the wall)
11. Have one person for each two teams to answer questions (co-presenter)
Please let me know if oyu have any more feedback. And once again, thanks for the feedback!
The Retrospective of Retrospectives (RoR for short) meeting is held after each individual team retrospective. The participants (representatives of all team and the program) meet to discuss what went well and what to improve in the program level. The RoR focus is on improving the overall program output, and not on individual team performance.