| Team environment, or individual project? The first rule of project management is to keep it as simple as you can get away with. Don't overcomplicate anything until absolutely necessary. > I don’t know how to manage issues dependencies (for instance, there are three issues A,B,C and they must be done in the order B->C->A) In the ticket for C, note that it depends on B. Link to B at the top of the description. Anyone reading the ticket should immediately see that B must be done first, and will click through to it. Repeat for A's dependency on C. Keep it simple. > detailed schedules like Gantt Chart. Unless you have perfect estimation skills and you can 100% scope your project from the start, you it's not realistic to put all of your tickets on to a Gantt chart. You'll find that the Gantt chart goes out of date within weeks or even days. Gantt charts are best reserved for high-level goals and milestones. For example, you could plan to work on B on week 41, work on C on week 42, and then work on A on weeks 43-44 with a milestone for completion of this group at the end of week 44. However, the Gantt chart isn't all that useful for dependencies within a single, contained project. It becomes more useful to view dependencies across teams and projects when you can allocate more people to tasks as necessary to unblock the critical path. If you're just working on a single project, the Gantt chart often simplifies to a basic estimation calendar, so use a base calendar instead. |
It is for team environment.
Yeah, I agree with you.
I have experienced mid~long period project and struggled with them so I asked this topic.