Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
why_don_t_we_use_gantt_charts_in_agile [2017/05/29 15:12]
Hans Samios [Why Don't We Use Gantt Charts in Agile?]
why_don_t_we_use_gantt_charts_in_agile [2018/01/17 14:12] (current)
Hans Samios [Discussion]
Line 9: Line 9:
 ====== Discussion ====== ====== Discussion ======
  
-The reason ​gaunt charts (or other project management artifacts) are not need is that with agile we set things up so we are producing iterative and incremental "​complete"​ solutions (MVP), building on what we have as we go. Our plan is based on producing value. ​+The reason ​gantt charts (or other project management artifacts) are not need is that with agile we set things up so we are producing iterative and incremental "​complete"​ solutions (MVP), building on what we have as we go. Our plan is based on producing value. ​
  
 In particular, tasks are managed by the team. Dependencies therefore become a lot more localized and dealt with through discussion with the team - we get the next piece of value as a result of having teams task the work required that deliver that value. If they need some task completed first that becomes part of the discussion. Sometimes that discussion will bleed into a prioritization discussion (eg team says "if you want this higher priority value item first, we might be better off doing this lower value item first" or one team talks to another about the relative prioritization'​s of two team's work) but those conversations should be relatively straight forward and the result is that an item moves up or down in the prioritized backlog. In particular, tasks are managed by the team. Dependencies therefore become a lot more localized and dealt with through discussion with the team - we get the next piece of value as a result of having teams task the work required that deliver that value. If they need some task completed first that becomes part of the discussion. Sometimes that discussion will bleed into a prioritization discussion (eg team says "if you want this higher priority value item first, we might be better off doing this lower value item first" or one team talks to another about the relative prioritization'​s of two team's work) but those conversations should be relatively straight forward and the result is that an item moves up or down in the prioritized backlog.
  • /home/hpsamios/hanssamios.com/dokuwiki/data/pages/why_don_t_we_use_gantt_charts_in_agile.txt
  • Last modified: 2018/01/17 14:12
  • by Hans Samios