Home Help About Profile Search Home
Guest: login

H2O Meta > 0.5 Feature Priorities

Rotisserie Question

Now that we have a list of potential features, the next step is to prioritize
which features should be implemented in the 0.5 release and in what order.  Each feature has a guestimated number of days associated with it.  We have about 120 developer days before a release in mid-February.  Your job is to pick out which features should be included in the next release (all of your features should only take 120 days to complete) and then, *very importantly*, to prioritize when those features should be implemented.  Once we set a concrete release date in February, the release date will be firm, while the number of features we complete will not, so the priority of the features will determine which features will definitely get into the release and which may not.

As our esteemed leader, Jonathan Zittrain will be ultimately responsible for putting together the final list of priorities for the release, but the feedback we get from this discussion will play a very important role in his decision.

For the list of features, see:

http://h2odev.law.harvard.edu/viewcvs/*checkout*/h2o/docs/plan/feature-priorities.csv?rev=1.6

Status ?

Done. Started on
12/2/02 5:00 PM
Schedule
Start: 12/2/02 5:00 PM
Round 1 Due: 12/3/02 4:00 PM
Round 2 Due: 12/4/02 4:00 PM
Round 3 Due: 12/5/02 4:00 PM
Final Due: 12/6/02 5:00 PM
Projects
Statistics
Active Users6
Posts13
Scheduled Rounds3
Search ?
Rotisserie Posts  (Refresh) ?
Sort By: Thread / Author View: Rotisserie Posts and Comments / Rotisserie Posts Only
Expand Rounds: All / 1 / 2 / 3 / None

In terms of a functional tool that will be used by professors, teachers, and other distance and face-to-face educators, it seems that there are a few major priorities. A reliable More...

The reasoning behind this prioritization scheme is clear and very helpful.  

A comment on the user visible round crank which is listed as priority 1:   this feature is problematic in More...

I hadn't thought through both the engineering and usability issues associated with a premature crank. Your comments on possible ramifications are important to consider. Perhaps the system itself would not More...

View Thread Comments

2 Include user id in urls in assignment emails
10 Predefined attributes
15 Custom Attribute functionality
5 optional automatic expulsion on round skip
5 Invite unregistered user to join a More...

My priorities were based on classroom use, and the features that I had programmed (or failed to program) into past versions of the rotisserie.  So to me, more flexibility in More...

View Thread Comments

I've included a lot of the big ticket functionality items (custom attributes, routing, polling, invitations) b/c that's where I think we need to concentrate our efforts if the system is More...

I agree for the most part except for some of the routing.  The help was lower on my list, but I'm sure it will make it in there since not More...

View Thread Comments

I think the following (somewhat ranked by priority) are the most important/coolest features:

o Bulk user load (5)
o Bulk project acceptance page (5)
o Help system infrastructure - support More...

These look a good set of tasks/priorities for me. The only ones that I'm not sure about is how important extra custom attributes or specialized types of polling are. I More...

The polling and custom attributes are important b/c they allow more interesting kinds of routing.  For example, including the option to select a poll answer in addition to the standard More...

The poll is a simple way to add graphical feedback and fodder for in-class discussion.  It's quick for the instructor to set up, quick for the students to answer, and More...

View Thread Comments

Here's what I think.  Ordered by priority, 1 is the best.  Features I didn't think we should support in this rev have been removed.  Notably absent are the other types More...

View Thread Comments

,Rotisserie,5,"Add absolute date picker to date fields and to round start/end (so that the user can choose either round durations or specific end dates)"
,UI,1,"Include 'Current H2O Time' somewhere in More...

View Thread Comments