Search code examples
scrumrtc

How long should I wait to see a Sprint Burndown chart in RTC?


We've just set up a Rational Team Concert v3 system. The data was loaded on Friday, but there was an issue connecting to the report data warehouses that was not fixed until today (Monday). We've fixed it, and the data load operations seem to be finishing correctly now.

I'm desperately eager to see a burndown chart - even though I know that in 24 hours we won't really have enough data to make it useful. I'm also eager to see just about any report from the RTC server, as we want to be able to share as much information as possible with the customer, and this is a trial for RTC as a large team tool.

How long should one expect it to take before RTC is able to show reports relating to work items? We've already cached several data updates - but only within the last few hours.

Should we wait 24 hours? 48? should it show up immediately? Haven't found any good heuristics for this on the Rational site.


Solution

  • You need a few things to happen to get a decent burn down chart in RTC

    1. Run the Data Warehouse job (this happens every 24 hours automatically, or you can trigger it manually from the Reports page in the Admin section.
    2. Get some work done - complete tasks, set Stories to Completed, etc. The burn down is a graph over time of work done.

    You should see progress on the chart after the two event above occur.

    Another thing to check - is that specific burn down chart set to point to the right project and team?

    If that does not work - you may want to raise the question with IBM support (sounds like something is wrong, or raise the question on the RTC forum on jazz.net