how_do_we_get_away_from_business_as_usual_thinking_on_teams
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| how_do_we_get_away_from_business_as_usual_thinking_on_teams [2019/01/22 18:51] – [Want To Know More?] Updated links hpsamios | how_do_we_get_away_from_business_as_usual_thinking_on_teams [2019/01/22 18:53] – [The Proactive Retrospective] hpsamios | ||
|---|---|---|---|
| Line 33: | Line 33: | ||
| * Impediment mining: Become more aware of recurring problems by looking through threads of messages in your email. Or perhaps look at the reasons you are having meetings. With “impediment mining” your email client can be a great source of potential problems with value delivery. Also look at your retrospectives over time. Do you see the same problems come up time and again. Perhaps you should do something about these? | * Impediment mining: Become more aware of recurring problems by looking through threads of messages in your email. Or perhaps look at the reasons you are having meetings. With “impediment mining” your email client can be a great source of potential problems with value delivery. Also look at your retrospectives over time. Do you see the same problems come up time and again. Perhaps you should do something about these? | ||
| - | (Note: I am indebted to Tom Perry' | + | (Note: I am indebted to [[https:// |
| In many ways, this thinking approach is really about increasingly seeing the whole system, seeing the Team’s part in that system, and seeing where the problems and impediments are. Once we have identified the problems, the usual Retrospective steps apply - root cause analysis, ideas to address, plan of action (including backlog items and experiment), | In many ways, this thinking approach is really about increasingly seeing the whole system, seeing the Team’s part in that system, and seeing where the problems and impediments are. Once we have identified the problems, the usual Retrospective steps apply - root cause analysis, ideas to address, plan of action (including backlog items and experiment), | ||
| - | |||
| ====== Supporting Significant Change ====== | ====== Supporting Significant Change ====== | ||
| Line 46: | Line 45: | ||
| * [[how_do_we_run_our_first_sprint_retrospective|How Do We Run Our First Sprint (or Iteration) Retrospective? | * [[how_do_we_run_our_first_sprint_retrospective|How Do We Run Our First Sprint (or Iteration) Retrospective? | ||
| - | * See [[https:%%//%%www.amazon.com/ | + | * See [[https:// |
| - | * See [[https:%%//%%www.amazon.com/ | + | * See [[https:// |
| {{tag> | {{tag> | ||
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/how_do_we_get_away_from_business_as_usual_thinking_on_teams.txt · Last modified: 2023/03/10 07:04 by hans