Link Details

Link 997167 thumbnail
User 355617 avatar

By piccoloprincipe
Submitted: Jul 13 2013 / 04:46

Retrospectives are often considered to be a valuable agile technique, as they support teams to reflect and adapt their way of working and help them to improve and deliver more value to their customers. But sometimes teams find it difficult to do retrospectives. Team members can feel that they don’t control things that need to be changed, think that they can’t improve any further, have difficulties defining good actions, or start complaining in stead of defining actions. They may find that retrospectives are boring, and feel that they are a waste of time. How can you deal with these difficulties, and help teams to discover better ways to do retrospectives?
  • 2
  • 0
  • 59
  • 7

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (2)

Voters Against This Link (0)

    Apache Hadoop
    Written by: Piotr Krewski
    Featured Refcardz: Top Refcardz:
    1. Play
    2. Akka
    3. Design Patterns
    4. OO JS
    5. Cont. Delivery
    1. Play
    2. Java Performance
    3. Akka
    4. REST
    5. Java