Report/List Requests

Hi Louisa,

This thread might be of use.

A Form does not really work for us.

As part of our Scrum Tessitura Release Process which we call BAMtemp. We use a quick user story as the request and followup with conversations at Release planning and beyond.

To get started a requester (we call business owner) needs a user story is in the form

As a __________________________________________

                                     Type of Person or Roll

By ____________________________________________

                                       Optional Date

Can _________________________________________________________

                 Some thing the person above can do

So That _________________________________________________________

                  The reason that you want to do that

Because ________________________________________________________

                     The business rational (Save time, cut cost, numbers are good here.)

And any known conditions of satisfaction.  Things that we can know so we know when we are done.

This often, for a report, takes on the form of a dummied up spreadsheet showing what the report might look like.  OR a PDF on an existing report showing the desired changes. Sometimes we go to the point of actually sourcing data directly from Tessitua and put it in a spreadsheet and build a dummy report that way.

This is then presented at the Release planning meeting (which occurs once every 6 weeks) by the Business Owner and the story is evaluated based on Size of the story (Cost to build the change) and Business Value.  (This gets a crude ROI analysis done.)  We as a group then build a prioritized backlog of changes.  At that point the programmer and Business owner will have frequent interactive sessions until a report or process is completed.

Hope this helps.

Here's ours, as developed by our DBA, Katie Lachance-Duffy.

Thanks everyone for the suggestions! It is very helpful.

Thanks everyone for the suggestions! It is very helpful.