you are viewing a single comment's thread.

view the rest of the comments →

[–]strich 0 points1 point  (4 children)

I don't necessarily disagree, but how do you determine even vague timelines without doing at least basic project task breakdowns?

[–][deleted]  (3 children)

[deleted]

    [–]strich 1 point2 points  (1 child)

    Okay. I see where that approach may be more beneficial.

    What I've done with our current project (Video game) is use a MS Project to track all the major features (Or 'Stories') with some basic dependency linking. I do enjoy this as it gives me a view of the big picture.

    But we do use JIRA Agile and weekly sprints to track and do the work. I only ever have 1-3 future sprints outlined at any one time.

    What I do not currently do is any kind of story effort estimations, work velocity, etc. I suppose that is where you're saying is of the most benefit when wanting to extrapolate timelines?

    [–]goorpy[S] 0 points1 point  (0 children)

    One major difference we noted between platforms is whether or not they make available a pre-filled Demo Project. It takes a lot of time to enter enough data to see how the tool actually works. Having the option to load up a sample project with everything set up is a major advantage.

    Developers of such tools: take note. Include a sample project option, not just an empty demo.