Monday, August 20, 2007

State of Assistment: August 2007

Summary:
  • The first "State of Assistment"! - Monthly letter to keep a clear Assistment's vision clear.
  • The "good/bad" old days - Thank you to the people who realized we needed a change and a quick history of how we got here.
  • What to expect from v3 - Quick releases - monthly feature updates / Changes from the user point-of-view.
  • How Close Are We? - Pending issues: A couple small issues (more IE6 fixes, tutor extensions rendering fixes for effort bar and feedback, and general interface cleaning),
    and a new feature (resuming assistments ... abe and I are working on it).
  • Where do we go from here? - Versioning, Tutor Calculator, cleaner content, and more interface updates / Infrastructure updates.

The first "State of Assistment"!

Woohoo! This is "State of Assistment ", the first of many letters/rants/musings I will write to the team. How often? Not sure, but once per release (roughly once a month) is what I'm thinking now. The purpose of this is to keep the vision of Assistment fresh in every one's mind, introduce new ideas, and ultimately guide Assistment along it's newfangled "Productization" path. (Remember when I thought I made up the word "productization"? They use it all the time here ... go figure).

These might get obscenely long as a lot of content may pile up over the month ... so I will rely on you all to tell me what's interesting to you, what you want to hear me rant about, or how you think this is "completely worthless and just my vain efforts to stick around and not let my baby go" ... umm, yes, that's a quote from myself. Hopefully it will be more valuable than that ... but again, help me make this useful to you.

The "good/bad" old days

I'm happy I never had to touch the old system. I'm also sadistically happy some folks were around that had touched the old system too much ... or possibly had the old system inappropriately touch them. Not only did they help preserve the original vision, but more importantly they were the loudest voice for why the system needed to change.

All the code you use and the UI you see today was created during that time, and the v2 system tucked away for nostalgia. I started off as a UI designer, but also started prototyping a new Assistment Builder in Rails. After convincing the leadership that Rails could save Assistment, Darren Torpey and I wrote the Assistment v3 0.1, a early prototype to show that this conversion was possible. After monthly releases, school testings, and a bunch of new developers, we are on the verge of releasing v3.

What to expect from v3

With the Java system [almost] behind us, what should we expect from this new version? What should our users expect?

First off, feature-release should be a much quicker process. The Assistment system should get new features/updates every month. Of course, this statement makes assumptions about the size of the feature, and that we have enough students working, but that's fine ... your released features shouldn't be that huge. However, this amount of time allows for features to be released in a stable, tested fashion; no more should we accept Assistment crashing for a class or students seeing error messages.

Version 3 is not just a technical rebirth, but a rethinking of everything that Assistment was. A completely new User Interface and new ways thinking about content and tutoring are really what make this version what it is. Our current users will find the new system much more intuitive, requiring little training on how to accomplish their tasks. Content creators will find that creating an assistment/problem set is MUCH quicker and logical than the previous system. Teachers can manage their classes much easier, see how their students are doing (not much change there), and use the system to maintain all their student's grades, even the non-assistment grades. Students will also see a huge difference, with bigger fonts and more logical navigation through their tutoring, hopefully this system will be more effective at tutoring the students.

How Close Are We?

Holy! It's August 20th? How close are we to moving all the classes to version 3??? Other than small bug fixes with visuals (more ie6 fixes, tutor extensions rendering fixes for effort bar and feedback, and general interface cleaning), and a new feature (resuming assistments ... abe and I are working on it), I'm comfortable to say we're almost done. For the rest of this week (8/20-24), most of our work should be focusing identifying any other "show-stopper" issues; it doesn't need to be perfect ... but we need to know what we're slacking on and make the appropriate decisions/trade offs.

Where do we go from here?

Getting to this point has been a great experience, seeing this system grow from "./script/generate model Assistment" to what we've got today. Darren, Abe, and I we're able to get it off the ground, but lots of thanks to Cody, Shane, Elijah, and Ryan for all the cool stuff you're doing and adding more depth to Assistment; I can't wait to see what else you guys will do. Thanks also to the newer developers; you're code will see the light of day very soon. =)

After this release (end of August), what will be deliver in another month? I see this next release as including things such as Versioning, Tutor Calculator, cleaner content, and more interface updates. Also, we should also look at our infrastructure, finding ways to make our setup be as effective as possible (dedicated web-server for static content, database replication, rails page/action caching).

In Conclusion ...

This is a great time to be working on Assistment; we really have a chance to be the best tutoring software out there. I wish I could be in schools seeing students learning from our work, but you'll just have to let me know how it goes. =)

Any Questions? Comments? Suggestions? I hope this was useful/informative to some of you ... at least to convey some sort of consistent direction/vision. Again, if there's anything you'd like me to cover in this, let me know.

No comments: