Isrshortcomings
  1. When will we have the development resources to lift the current "freeze" on IS report development?
    • test
  2. What needs to happen for the current team to embrace this part of the product and start making some visible improvements to it.
  3. What work can be salvaged from the 4-5 months spent on the previous project for reporting overhaul? Is there a report or a project plan/milestones associated with that work?

1) When will we have the development resources to lift the current "freeze" on IS report development?
2) Do we need to start over or can we upgrade the current system incrementally? I'd like to get real on the current distancing of the development group from the IS product as an "ugly step-child" for lack of a better term. What needs to happen for the current team to embrace this part of the product and start making some visible improvements to it.
3) Prioritization of current IS reporting wishlist items. Of particular interest is restriction of the pool of developed reports to specific users.
4) I'm personally confused by our "Save" methodology.
5) Potential for using the framework as a generalized reporter for non IS tables.
6) What work can be salvaged from the 4-5 months spent on the previous project for reporting overhaul? Is there a report or a project plan/milestones associated with that work?
7) Education of the un-enlightened (well, me, at least) of advances, options, for building customized web reports in general (IS?, non-IS?)
8) Who is thinking about IS 5.0? Is this on the drawing board? Will it include any changes to IS Reporting? Can we talk about it at EXPO?