Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace: • how_do_we_use_story_point_estimates_to_forecast • how_should_we_initially_track_release_progress • why_do_we_assign_business_values_to_pi_objectives • how_do_i_help_raise_awareness_of_transformation_problems • what_are_the_potential_problems_implementing_okrs_in_an_organization • safe_values_and_principles • why_don_t_we_use_gantt_charts_in_agile • what_is_session_based_testing • what_are_the_problems_with_estimation • what_is_wrong_with_100_utilization_thinking
why_don_t_we_use_gantt_charts_in_agile

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
why_don_t_we_use_gantt_charts_in_agile [2017/05/29 15:12] – [Why Don't We Use Gantt Charts in Agile?] hpsamioswhy_don_t_we_use_gantt_charts_in_agile [2023/08/14 11:45] (current) – ↷ Links adapted because of a move operation hans
Line 1: Line 1:
 ====== Why Don't We Use Gantt Charts in Agile? ====== ====== Why Don't We Use Gantt Charts in Agile? ======
- 
-====== Premise ====== 
  
 Most of the time when we go down the path of an agile implementation Gantt charts do not help much. I've seen them used to describe high level plan, almost like a roadmap more as a result of a need to meet a governance standard but not really useful as a tool for managing a project (or dependencies). Most of the time when we go down the path of an agile implementation Gantt charts do not help much. I've seen them used to describe high level plan, almost like a roadmap more as a result of a need to meet a governance standard but not really useful as a tool for managing a project (or dependencies).
Line 9: Line 7:
 ====== 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.
Line 16: Line 14:
 For additional discussion on Gantt charts at [[http://www.techdarkside.com/the-demise-of-the-gantt-chart-in-agile-software-projects|The Demise of the Gantt Chart in Agile Software Projects]] For additional discussion on Gantt charts at [[http://www.techdarkside.com/the-demise-of-the-gantt-chart-in-agile-software-projects|The Demise of the Gantt Chart in Agile Software Projects]]
  
-Also see [[blog:why_doesn_t_traditional_project_management_work_for_software_projects|Why Doesn't Traditional Project Management Work For Software Projects?]]+Also see [[what_is_the_best_approach_to_making_decisions_in_our_context|Why Doesn't Traditional Project Management Work For Software Projects?]]
  
  
 {{tag>FAQ ProjectManager Project PM Gantt}} {{tag>FAQ ProjectManager Project PM Gantt}}
  
-~~LINKBACK~~ 
-~~DISCUSSION~~ 
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/why_don_t_we_use_gantt_charts_in_agile.1496095974.txt.gz · Last modified: 2020/06/02 14:21 (external edit)