5 ms·

Gantt charts also represent dependencies among tasks. They add more information as well: time estimation, milestones, asignees, etc. Gantt charts receive some

Gantt charts also represent dependencies among tasks. They add more information as well: time estimation, milestones, asignees, etc. Gantt charts receive some criticism since estimations are approximations and any precision issue starts compounding very quickly. Issue trackers may also support dependencies between tasks. The problem is that issue trackers usually come with scrum/kanban boards that do not have a represention dependencies among tasks. There are many applications to put together a gantt chart.

zwischenzug 9y ago
Can I export it to code?
- partycoder 9y ago
  I am not sure a GraphViz digraph is the way to go. If you want to keep track of what is done and what is remaining eventually you will need to update that file. This will quickly lead to version control conflicts. Issue trackers I think are the way to go. You can integrate with one using their API.
  - zwischenzug 9y ago
    I think version control conflicts are good in this case - they indicate the level to which there is conflict within the team around what the project consists of.
    - partycoder 9y ago
      Version control conflicts in this case don't necessarily map to disagreement. Imagine 2 team members that are in agreement add leaf 2 nodes. That would trigger a version control conflict. Now imagine that situation in a team of 5, or 10. It becomes hard to maintain.
- codingdave 9y ago
  That is an odd question. There is data underlying any type of chart. You would work that data from your data layer, not your UI, and then code something new with it, or re-render a new visualization as you see fit.
  - zwischenzug 9y ago
    Some data is easier to collaborate with as code than others. This is one reason why XML was superceded by JSON, and YAML exists as a rival. GUI apps are great but less good for sharing. The conflicts are part of the point.
- DEADB17 9y ago
  plantuml is also text based and supports many types of diagrams: http://plantuml.com/gantt-diagram http://plantuml.com/gantt-diagram

zwischenzug 9y ago

Can I export it to code?

partycoder 9y ago
I am not sure a GraphViz digraph is the way to go. If you want to keep track of what is done and what is remaining eventually you will need to update that file. This will quickly lead to version control conflicts. Issue trackers I think are the way to go. You can integrate with one using their API.
- zwischenzug 9y ago
  I think version control conflicts are good in this case - they indicate the level to which there is conflict within the team around what the project consists of.
  - partycoder 9y ago
    Version control conflicts in this case don't necessarily map to disagreement. Imagine 2 team members that are in agreement add leaf 2 nodes. That would trigger a version control conflict. Now imagine that situation in a team of 5, or 10. It becomes hard to maintain.
codingdave 9y ago
That is an odd question. There is data underlying any type of chart. You would work that data from your data layer, not your UI, and then code something new with it, or re-render a new visualization as you see fit.
- zwischenzug 9y ago
  Some data is easier to collaborate with as code than others. This is one reason why XML was superceded by JSON, and YAML exists as a rival. GUI apps are great but less good for sharing. The conflicts are part of the point.
DEADB17 9y ago
plantuml is also text based and supports many types of diagrams: http://plantuml.com/gantt-diagram http://plantuml.com/gantt-diagram