The top 10 things you'd change about your SIS
Summary: I went to a meeting yesterday of the X2 Advisory Council. This is a group of users/tech director types that our student information system developer (X2 Development Corporation) set up to to help drive product development cycles for the Aspen SIS.
I went to a meeting yesterday of the X2 Advisory Council. This is a group of users/tech director types that our student information system developer (X2 Development Corporation) set up to to help drive product development cycles for the Aspen SIS. We meet roughly once a quarter to review their product roadmap and help set priorities.
This time, however, they took a different approach that I thought was incredibly effective and was clear evidence that with their product now quite mature and stable, the company is keenly focused on delivering the most useful and usable product it can to its customers. Before the meeting, one of the project managers asked all of the members of the Advisory Council to identify the top 10 things we'd like to see changed in the system. Aside from a review of new features in their upcoming release, we didn't talk much about the roadmap.
As it turns out, many of the problems we identified were either fixed in the coming release or scheduled to be addressed this summer. Better integration with Excel, scheduling improvements, updates to their special education module, you name it. They're even eliminating the pop-ups that invariable give our users fits (try telling a parent accessing their student's grades for the first time how to disable the pop-up blockers in three toolbars and their browser over the phone).
X2 Aspen just keeps getting better. Although I can't discuss the details or exact outcomes of our discussion, suffice to say that we certainly pushed for some pretty cool new features that will take a rock solid product and make it even more useful. If X2 can pull it off (and I think they can), new and current customers have a lot to look forward to.
This is where you come in, though. What would you change about your SIS? Include the name/vendor and the top features you'd like to see added, the top "features" you hate, and even, the features you really like. Talk back below.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
RenWeb
The number one thing I would change is that they do not provide a way to do customizations using serious programming. So custom modules, SQL update queries, etc are out of the question.
But RenWeb's advantages far outweigh this minor inconvenience.
Avoiding pushing specific SIS systems
Writing about only one system becomes somewhat of an ethical question.
Avoid Vendor Lock-In
Esp given the budget situation, costs a lot for districts to purchase licenses for these products compared to say apache/mysql/postgresql or some of the other OSS options.
"code to published, open standards, not to platforms".
Make sure there are hooks to allow your IT dept to extend the system without having to wait for the vendor to decide if the needed feature is worth doing from a business standpoint.
Being able to automate data extracts and pipe them where they need to go is great, though in my case I had to build this out myself outside the system (perl + freetds).
With increasingly demanding data interchange requirements, esp those that are requested by local entities (frequently custom, one-off stuff), having to manually dork with spreadsheets and text files is just plain lame.
RE: The top 10 things you