What I said/did:
- Assess and start training the new guy
<snip>
- Meet w/ ASUH representative to get student-oriented feedback.
Had the meeting and wrote it up on the blog: http://uhmis-ecafe.blogspot.com/2008/03/asuh.html.
The short version is that they pretty much approved the system, liked what they saw, and are very happy we talked to them. They also said that it appeared that privacy concerns were addressed and they had no issues there. We spent the majority of the meeting talking about possible methods of increasing response rates.
- Implementing staff features.
Writing code? What's that?
- Reading: MySQL and ?
The ? turned out to be Ruby. My eyes are tired. Florescent lights suck. Let's declare the Manoa Starbucks a "Remote Office," they have windows.
In other news:
- I mentioned how there needs to be a small barrier for requesting features. I'm trying out this. We'll see how it goes.
- The BSAR specs were posted to the blog and I sent an email to D on Wednesday.
- Some advisory board members were saying that they like the blog, but want notification of when posts are made. So, I started a Google Group which users can join and opt for email notification. When a post is made, the blog automatically sends notice to the group, the notice is then disseminated by email to all members of the group.
Next week:
- Reading (will it EVER end?)
- Working on eCAFE Staff features
- Going to that "User Centered Design Tests" lecture
- Looking into how we can "hide" grades when students don't do their surveys.
Showing posts with label status report. Show all posts
Showing posts with label status report. Show all posts
Thursday, March 20, 2008
Friday, March 14, 2008
Status Report: 3/10-3/14
What I said/did:
- Factor D's most recent comments into the BSAR specs.
Done. I'll be posting it to the site and asking for his review on Monday.
- Implementing staff features.
Didn't really do much here. Ended up doing some edits to the database layout and looking into how/if I can accommodate a feature request. In contemplating how the feature would work, I generated a number of questions I needed them to answer. When I forwarded the questions, the request got dropped.
At one of the sessions I went to at the conference, there was a discussion on users asking for features and how it quickly bloats software. The determination was that users should have to go over some sort of hurdle when making a feature request. If it's too easy, then they'll toss up any old idea, even if hardly anyone would use it. This was proven true in the above example, and now I'm debating how to incorporate a small "barrier" for future feature requests to make sure it's something that people have really thought about and need, rather than just a whim.
- Reading up on MySQL and maybe some other technologies for BSAR.
I'm working my way through some of the MySQL books. Will be ongoing for a while.
Next week:
- Assess and start training the new guy
- Meet w/ ASUH representative to get student-oriented feedback.
- Implementing staff features.
- Reading: MySQL and ?
While I wrote the above as a guide, it's going to be pretty fluid depending on what happens with new guy. I'll be playing things by ear next week.
- Factor D's most recent comments into the BSAR specs.
Done. I'll be posting it to the site and asking for his review on Monday.
- Implementing staff features.
Didn't really do much here. Ended up doing some edits to the database layout and looking into how/if I can accommodate a feature request. In contemplating how the feature would work, I generated a number of questions I needed them to answer. When I forwarded the questions, the request got dropped.
At one of the sessions I went to at the conference, there was a discussion on users asking for features and how it quickly bloats software. The determination was that users should have to go over some sort of hurdle when making a feature request. If it's too easy, then they'll toss up any old idea, even if hardly anyone would use it. This was proven true in the above example, and now I'm debating how to incorporate a small "barrier" for future feature requests to make sure it's something that people have really thought about and need, rather than just a whim.
- Reading up on MySQL and maybe some other technologies for BSAR.
I'm working my way through some of the MySQL books. Will be ongoing for a while.
Next week:
- Assess and start training the new guy
- Meet w/ ASUH representative to get student-oriented feedback.
- Implementing staff features.
- Reading: MySQL and ?
While I wrote the above as a guide, it's going to be pretty fluid depending on what happens with new guy. I'll be playing things by ear next week.
Friday, March 7, 2008
Status Report: 3/3-3/7
What I said/did:
- Open the original eCAFE up to instructors.
Done. Been answering the inevitable questions that result from it. On a side note, S and I agreed on an arrangement for answering emails. We'll alternate weeks for now, adjusting/pitching-in as needed. We had a few missteps where we both answered the same email, hence the need for the arrangement. I just wanted to let you know this since you are on the mailing list now and might think that she was shirking the job. This was my week, next week it's all her.
- Factor D's most recent comments into the BSAR specs.
Didn't happen. Pushing this to next week.
- Rework the specs to account for the Women's Studies changes (once approved).
Done and posted to the blog.
- Work on implementing the staff features (this will be a repeating item on my list for the next month or so).
Ongoing.
In other news: I did the summary of other schools' experiences with going to an online evaluation system, and posted it to the blog. I haven't yet heard back any feedback on it, or on any of the ideas that came out of it.
I've also been trying to re-work part of the database that just seems... well, messy. It works, but I'm sure there's a better way to arrange things so it's more intuitive, yet I've been unable to see another way to do it. These few tables are a hold out from the last version and I think I'm so used to seeing them, that my brain won't drop them for another way.
Next week:
- Factor D's most recent comments into the BSAR specs.
- Implementing staff features.
- Reading up on MySQL and maybe some other technologies for BSAR.
- Open the original eCAFE up to instructors.
Done. Been answering the inevitable questions that result from it. On a side note, S and I agreed on an arrangement for answering emails. We'll alternate weeks for now, adjusting/pitching-in as needed. We had a few missteps where we both answered the same email, hence the need for the arrangement. I just wanted to let you know this since you are on the mailing list now and might think that she was shirking the job. This was my week, next week it's all her.
- Factor D's most recent comments into the BSAR specs.
Didn't happen. Pushing this to next week.
- Rework the specs to account for the Women's Studies changes (once approved).
Done and posted to the blog.
- Work on implementing the staff features (this will be a repeating item on my list for the next month or so).
Ongoing.
In other news: I did the summary of other schools' experiences with going to an online evaluation system, and posted it to the blog. I haven't yet heard back any feedback on it, or on any of the ideas that came out of it.
I've also been trying to re-work part of the database that just seems... well, messy. It works, but I'm sure there's a better way to arrange things so it's more intuitive, yet I've been unable to see another way to do it. These few tables are a hold out from the last version and I think I'm so used to seeing them, that my brain won't drop them for another way.
Next week:
- Factor D's most recent comments into the BSAR specs.
- Implementing staff features.
- Reading up on MySQL and maybe some other technologies for BSAR.
Status Report: 2/25-2/29
What I said/did:
> - Hook up the new eCAFE to MySQL and start adding parts back in (copy
> code from the old eCAFE and edit it for the new schema).
Done. I have the stripped-down eCAFE working off my local MySQL server, and I've started adding basic functionality back in and editing it all for the new schema.
> - Once I have the changes to the schema finished, I'll add more tables in
> the MySQL database as necessary.
Made many changes, posted the new schema to the blog along with a listing of what changed between each revision and why. I'm creating tables in the db as they become necessary for implementing code/functionality.
> - Try to get some meetings with users.
I had a meeting with the chair of the Women's Studies department today (finally), and it was a very productive conversation. We came around to a different way of handling some things. I'm working on a post and an email to send to all interested parties to put the changes out there and get feedback. Assuming the changes are ok with everyone, then I'll do the necessary revisions to the schema.
Next week:
- Open the original eCAFE up to instructors.
- Factor Darrell's most recent comments into the BSAR specs.
- Rework the specs to account for the Women's Studies changes (once approved).
- Work on implementing the staff features (this will be a repeating item on my list for the next month or so).
> - Hook up the new eCAFE to MySQL and start adding parts back in (copy
> code from the old eCAFE and edit it for the new schema).
Done. I have the stripped-down eCAFE working off my local MySQL server, and I've started adding basic functionality back in and editing it all for the new schema.
> - Once I have the changes to the schema finished, I'll add more tables in
> the MySQL database as necessary.
Made many changes, posted the new schema to the blog along with a listing of what changed between each revision and why. I'm creating tables in the db as they become necessary for implementing code/functionality.
> - Try to get some meetings with users.
I had a meeting with the chair of the Women's Studies department today (finally), and it was a very productive conversation. We came around to a different way of handling some things. I'm working on a post and an email to send to all interested parties to put the changes out there and get feedback. Assuming the changes are ok with everyone, then I'll do the necessary revisions to the schema.
Next week:
- Open the original eCAFE up to instructors.
- Factor Darrell's most recent comments into the BSAR specs.
- Rework the specs to account for the Women's Studies changes (once approved).
- Work on implementing the staff features (this will be a repeating item on my list for the next month or so).
Monday, February 25, 2008
Status report 2/4-2/22
The last few weeks were in upheaval from the mainland trip and getting
sick, so the last weekly status report I filed was on 2/1.
What I said/did:
> - Setting up a meeting w/ the official advisory board.
Had the meeting. Got approval on the specs so we can move forward with
development. There are a few issues still outstanding, but we have time
before those need to be resolved, and people are assigned to get them
resolved.
> - Setting up interviews w/ various people who do things "differently."
No one wants to talk. It seems that everyone wants to
complain, but when I try to set up meetings, they're busy. At
least some actually read the doc and provided feedback. I haven't
given up on meetings, or at least phone conversations, yet.
> - Working on db schema (where I plan to spend the majority of my time)
Some changes came out of the meeting which still need to be incorporated.
I plan on finishing this today.
> - HCC stuff.
Never touched it.
In other news:
I made a stripped down version of eCAFE which logs in all the different
user types and takes them to the appropriate page. It doesn't do anything
else. This is necessary due to the huge changes going on in the database
schema. We had to strip all but the most basic of code out so we can run
the system on the new schema. This new eCAFE is checked in as a
completely separate new project.
I spent some time looking into possible methods of transferring data from
ods to eCAFE, I know this is tasked to someone else, but since it's going
to affect S and I in a big way, I think I should at least have a
passing familiarity with the options.
Spending time working on my MySQL knowledge. Apparently, I've forgotten a
lot. No worries, it's coming back.
Next week:
- Hook up the new eCAFE to MySQL and start adding parts back in (copy
code from the old eCAFE and edit it for the new schema).
- Once I have the changes to the schema finished, I'll add more tables in
the MySQL database as necessary.
- Try to get some meetings with users.
sick, so the last weekly status report I filed was on 2/1.
What I said/did:
> - Setting up a meeting w/ the official advisory board.
Had the meeting. Got approval on the specs so we can move forward with
development. There are a few issues still outstanding, but we have time
before those need to be resolved, and people are assigned to get them
resolved.
> - Setting up interviews w/ various people who do things "differently."
complain, but when I try to set up meetings, they're busy. At
least some actually read the doc and provided feedback. I haven't
given up on meetings, or at least phone conversations, yet.
> - Working on db schema (where I plan to spend the majority of my time)
Some changes came out of the meeting which still need to be incorporated.
I plan on finishing this today.
> - HCC stuff.
Never touched it.
In other news:
I made a stripped down version of eCAFE which logs in all the different
user types and takes them to the appropriate page. It doesn't do anything
else. This is necessary due to the huge changes going on in the database
schema. We had to strip all but the most basic of code out so we can run
the system on the new schema. This new eCAFE is checked in as a
completely separate new project.
I spent some time looking into possible methods of transferring data from
ods to eCAFE, I know this is tasked to someone else, but since it's going
to affect S and I in a big way, I think I should at least have a
passing familiarity with the options.
Spending time working on my MySQL knowledge. Apparently, I've forgotten a
lot. No worries, it's coming back.
Next week:
- Hook up the new eCAFE to MySQL and start adding parts back in (copy
code from the old eCAFE and edit it for the new schema).
- Once I have the changes to the schema finished, I'll add more tables in
the MySQL database as necessary.
- Try to get some meetings with users.
Friday, January 25, 2008
Status Report 1/24-1/28
What I said/did:
- Release to staff users. Set up HCC campus-wide.
- Volunteering at TIP conference for most of the week, and there's a holiday on Monday, so I'll work in eCAFE/BSAR specs as I can, but I'm not expecting much.
I did send out the notice to the staff users. HCC needs a bit more work as I'm trying something new with setting them up which needs more testing but hopefully will save me effort later in the semester.
I'm still holding on the BSAR specs as I've only gotten three responses so far, and not all of my questions have been addressed. Darrel sent an email to all probable users yesterday, asking them to provide feedback. I'll give that a week and then put out a final plea if I don't get much back.
The eCAFE specs are coming along nicely.
Had a meeting with Hae regarding eCAFE. She's going to talk to some faculty organization about a plan we discussed regarding who gets to see results. She opines that any faculty who is mandatory likely has to share their results, so we could allow the dept to see those without having the instructor send it. She'll be looking into it, meanwhile, I'll write it into the specs and see if instructors flip about it or what.
We also discussed the advisory board. She told me about hers, and I told her about mine. We've agreed that I'll publish the new specs to the blog, gather feedback from both boards, and then we'll set up a meeting with her official board to discuss and make any needed decisions.
Next week:
- Finish eCAFE specs rewrite and post to blog
- Test new HCC setup
- Work on setting up the schema in eCAFE MySQL db.
- Release to staff users. Set up HCC campus-wide.
- Volunteering at TIP conference for most of the week, and there's a holiday on Monday, so I'll work in eCAFE/BSAR specs as I can, but I'm not expecting much.
I did send out the notice to the staff users. HCC needs a bit more work as I'm trying something new with setting them up which needs more testing but hopefully will save me effort later in the semester.
I'm still holding on the BSAR specs as I've only gotten three responses so far, and not all of my questions have been addressed. Darrel sent an email to all probable users yesterday, asking them to provide feedback. I'll give that a week and then put out a final plea if I don't get much back.
The eCAFE specs are coming along nicely.
Had a meeting with Hae regarding eCAFE. She's going to talk to some faculty organization about a plan we discussed regarding who gets to see results. She opines that any faculty who is mandatory likely has to share their results, so we could allow the dept to see those without having the instructor send it. She'll be looking into it, meanwhile, I'll write it into the specs and see if instructors flip about it or what.
We also discussed the advisory board. She told me about hers, and I told her about mine. We've agreed that I'll publish the new specs to the blog, gather feedback from both boards, and then we'll set up a meeting with her official board to discuss and make any needed decisions.
Next week:
- Finish eCAFE specs rewrite and post to blog
- Test new HCC setup
- Work on setting up the schema in eCAFE MySQL db.
Thursday, January 24, 2008
Status report 1/14-1/18
What I said/did:
>
> - Monday is likely going to be all BSAR stuff. Tweaking the presentation,
> cleaning up some recent changes I made to the specs, and incorporating
> feedback from the meeting.
The meeting went as expected, I learned that while I had a good starting
point, there are quite a few changes that need to made. I've re-written
the specs since then and posted a list of questions on the blog. I'll
give a few days for answers, incorporate those, and send out the new
version of the specs for more comments.
> - There's a meeting Swee set up with the ODS people to discuss a specific
> issue we've been having. It's on Tuesday at 2pm if you care to join us.
Went well. Hashed out issues regarding dirty data and functional/organizational concerns.
> - The rest of the week is going to be spent wrestling with Photoshop (a
> new toy for me) and redoing the eCAFE specs with the goal of getting the
> first version out to current board members at the end of the week.
When I wrote this, I had forgotten that the next usage period for staff
starts this coming week. My time has been spent making sure accounts are
ready to go and other last minute setup stuff. This would be easier if
people were better about returning their phone calls.
I did do some work on the eCAFE specs, but there's a ways to go.
> - The caveat to the previous item is that Swee leaves on Thursday, so
> Thursday/Friday may be taken up with unknowns depending on where she is
> with the database stuff.
She did a good job. BTW, in talking to the people that used eCAFE last
semester, everyone has good things to say about Swee. The general
consensus is that she was very prompt in answering emails, conscientious
about her work, and in general left a positive impression. Thought I
would pass that on.
Next week:
- Release to staff users. Set up HCC campus-wide.
- Volunteering at TIP conference for most of the week, and there's a holiday on Monday, so I'll work in eCAFE/BSAR specs as I can, but I'm not expecting much.
>
> - Monday is likely going to be all BSAR stuff. Tweaking the presentation,
> cleaning up some recent changes I made to the specs, and incorporating
> feedback from the meeting.
The meeting went as expected, I learned that while I had a good starting
point, there are quite a few changes that need to made. I've re-written
the specs since then and posted a list of questions on the blog. I'll
give a few days for answers, incorporate those, and send out the new
version of the specs for more comments.
> - There's a meeting Swee set up with the ODS people to discuss a specific
> issue we've been having. It's on Tuesday at 2pm if you care to join us.
Went well. Hashed out issues regarding dirty data and functional/organizational concerns.
> - The rest of the week is going to be spent wrestling with Photoshop (a
> new toy for me) and redoing the eCAFE specs with the goal of getting the
> first version out to current board members at the end of the week.
When I wrote this, I had forgotten that the next usage period for staff
starts this coming week. My time has been spent making sure accounts are
ready to go and other last minute setup stuff. This would be easier if
people were better about returning their phone calls.
I did do some work on the eCAFE specs, but there's a ways to go.
> - The caveat to the previous item is that Swee leaves on Thursday, so
> Thursday/Friday may be taken up with unknowns depending on where she is
> with the database stuff.
She did a good job. BTW, in talking to the people that used eCAFE last
semester, everyone has good things to say about Swee. The general
consensus is that she was very prompt in answering emails, conscientious
about her work, and in general left a positive impression. Thought I
would pass that on.
Next week:
- Release to staff users. Set up HCC campus-wide.
- Volunteering at TIP conference for most of the week, and there's a holiday on Monday, so I'll work in eCAFE/BSAR specs as I can, but I'm not expecting much.
Friday, January 11, 2008
This week/Next week Status report
This week:
What I said I'd do vs. what I did:
> - The BSAR project documentation and db outline seems to be done for now.
> Next up is another meeting with Darrel followed by doing a presentation
> for the other BSAR people. There's no meeting scheduled yet, but
> hopefully I can get one in next week.
The presentation is this Monday at 2. Slides are done, but I imagine I'll
spend some time tweaking them before the actual meeting.
> - Rewriting the eCAFE specs as a starting point for the advisory board.
This turned out to be bigger than I thought. All my old "screenshots"
need to be redone, along with the site flow diagrams. Between that and
re-thinking how all the pieces fit together, this will be my big job for
next week.
- More reading.
Slow progress. I feel a little scattered right now between the usability
stuff and the MySQL stuff. Guess I need to set a priority.
Next week:
- Polish up the BSAR presentation, and incorporate feedback from the meeting.
- Clean up some recent changes I made to the specs
- There's a meeting on Tuesday @ 2pm with the ODS people to discuss a specific
issue we've been having.
- Rewrite the eCAFE specs with the goal of getting the first version out to current board members at the end of the week.
- The caveat to the previous item is that co-worker leaves on Thursday, so Thursday/Friday may be taken up with unknowns depending on where she is with the database updates.
What I said I'd do vs. what I did:
> - The BSAR project documentation and db outline seems to be done for now.
> Next up is another meeting with Darrel followed by doing a presentation
> for the other BSAR people. There's no meeting scheduled yet, but
> hopefully I can get one in next week.
The presentation is this Monday at 2. Slides are done, but I imagine I'll
spend some time tweaking them before the actual meeting.
> - Rewriting the eCAFE specs as a starting point for the advisory board.
This turned out to be bigger than I thought. All my old "screenshots"
need to be redone, along with the site flow diagrams. Between that and
re-thinking how all the pieces fit together, this will be my big job for
next week.
- More reading.
Slow progress. I feel a little scattered right now between the usability
stuff and the MySQL stuff. Guess I need to set a priority.
Next week:
- Polish up the BSAR presentation, and incorporate feedback from the meeting.
- Clean up some recent changes I made to the specs
- There's a meeting on Tuesday @ 2pm with the ODS people to discuss a specific
issue we've been having.
- Rewrite the eCAFE specs with the goal of getting the first version out to current board members at the end of the week.
- The caveat to the previous item is that co-worker leaves on Thursday, so Thursday/Friday may be taken up with unknowns depending on where she is with the database updates.
Subscribe to:
Posts (Atom)