requirements – D’Arcy Norman dot net https://darcynorman.net no more band-aids Wed, 24 Aug 2016 23:21:25 +0000 en-US hourly 1 https://darcynorman.net/wp-content/uploads/2015/04/crankforpeace3-552f33a1v1_site_icon-32x32.png requirements – D’Arcy Norman dot net https://darcynorman.net 32 32 1067019 sharing LMS requirements https://darcynorman.net/2013/06/06/sharing-lms-requirements/ Thu, 06 Jun 2013 02:07:15 +0000 http://darcynorman.net/?p=17099 Continue reading "sharing LMS requirements"]]> Jen suggested many (many) months ago that I post the requirements we used in the LMS RFP on github so people could use them, fork them, etc…. A starting point, so every institution doesn’t have to reinvent the wheel each time. Considering the amount of time and effort she put into helping craft them, how can I possibly refuse? I can’t, that’s how.

So.

Generic-ish LMS RFP requirements, ala github.

Things I learned about using this set of requirements:

  1. WAY too many line items. When ranking responses, we got serious regression toward the mean – the numbers balanced out and the differences were de-emphasized. Pick the ones that mean the most to you. Ignore (or demote) the rest.
  2. Some of the items were way too specific, others, not specific enough. Yeah. Balance.
  3. The vendors provided great responses to all of the items. I know they must have been frustrated by the sheer number of line items, but they pushed through and provided what we needed. And now, they have responses to copy and paste as needed, so it should get easier for everyone…

I haven’t received explicit approval from The Management to share these, but they were included in a public document, so it shouldn’t be a problem… Openness and sharing and unicorns and butterflies etc…

Update: I chatted with our CIO about this, and he thought it was a great idea. Cool. Done.

]]> 17099