Joe and Parker's capstone journal's Journal|
[Most Recent Entries]
Below are the 15 most recent journal entries recorded in
Joe and Parker's capstone journal's LiveJournal:
|Friday, March 22nd, 2002|
Sorry this hasn't been updated for ever and a day.
Our project is officially finished. We will still be putting some finishing touches on Livezilla and helping Brad launch it. Our paper will soon be available online, but for now...( read below for our project abstractCollapse )
|Monday, January 28th, 2002|
Two polls (mostly written by Parker, thanks man!) went up today into the lj_dev
community: one for members who have actively participated in lj development, and another for those who simply read lj_dev.
The reason for this is because we have different things to ask each of those two groups. For active devs, we want to know how they currently manage projects, what works, and what doesn't. For "lurkers" we want to know why they don't develop.
That came out wrong. We'd like to know why lurkers don't take an active roll in volunteering for LJ.
Read the polls for more information. The response has already been phenomenal (n=40, n=15 for active devs and n=25 for lurkers, both in the span of one afternoon).
Check out the polls:DevsLurkers
|Thursday, January 24th, 2002|
Stupid lost journal entries. I'll keep this one short:
Interviews with Brad/Evan/Dormando/Mark went well. Still need to do some more interviews. Perhaps with Sherm/Avva/Opi/[misc small-time dev]/[misc lj support volunteer] ?
Turned in first draft of lj_dev poll to David. We're going to split up the poll into two: one for people who have "developed something" and "lurkers" on lj_dev.
We're also researching existing PM applications. bugzilla looks pretty good so far, but we'd need to pair it down, because it's a little too much as is.
|Wednesday, January 2nd, 2002|
|Adding Parker to the project
Parker Thompson will also be working with me on the capstone project. Since we are now a team of two, we are brainstorming ways to increase the scope of the project that will be both beneficial to our client, and to the capstone project goals. Ideas so far include:
- More detailed evaluation (incl. detailed ethnographic study, pre/post implementation evaluation)
- More robust software
|Friday, December 14th, 2001|
|More pearls of wisdom from Prof McDonald
'satisfaction' is one potential metric. Do you know of any existing measures of 'satisfaction' (say, with a given technology) that you can reuse? You might look into that if you don't already know of one.
Uptime might be an interesting metric. But I think I'd want to know a little about how uptime is related to effective project managment and a project management tool.
Remember, you're trying to show that the technology made a change, so there needs to be some relationship between the thing that you measure (e.g. 'satisfaction' or uptime) and the effectiveness of the technology. I think establishing that link is sometimes the most tricky thing.
Boldalics are mine.
|Research in a design process
Brought up at yesterday's capstone meeting:
VSD uses a three-level evaluation during the design phase:
1. Theoretical (non empirical)
These take place during
Part of an iterative processArtifact as inquiry
serves parts 2 and 3.
|Wednesday, December 12th, 2001|
Prof McDonald writes: I think we'll need to think creatively about how to evaluate the impact of a changed project managment tool/system on livejournal. I think looking at project timelines is interesting and you should probably collect that data when you make the changes.
My concern is that even if you have access to the project timelines it's hard to compare projects (unless they are doing the same project over and over again). As well, it often takes some period of time (maybe months?) before you might have enought 'projects' to actually evaluate the impact based on project timelines. SO, I think there are other ways of evaluating the impact and we should work at brainstorming some of those.
What other, maybe indirect, effects could you examine?
One way I can judge the impact is with the satisfaction of
A. Mr. Fitzpatrick
B. Development volunteers
C. Site users at large.
Also (and this is closely related to C., above), another measurement could be site uptime. Currently the site has what I believe to be a scalability problem, and sometimes goes down (especially for users of the free "light" service). Perhaps some company projects have to do with better uptime.
Those are just initial thoughts. I can also ask Mr. Fitzpatrick his views on the subject.
|Saturday, December 8th, 2001|
|Letter of Intent
Capstone Statement of Intent
Title: Project management in an open source developing community
Project Head: Joe Goldberg
Email Address: email@example.com
Type of Capstone (research or design/implementation): design
Credits Requested: 5
LiveJournal (www.livejournal.com) is an open-source online journaling service, developed by Brad Fitzpatrick and a handful of volunteers around the country (and some abroad). There is an information problem between the various volunteers working on LiveJournal, both between each other ("has x already been taken care of?") and between them and Mr. Fitzpatrick, LiveJournal's creator, ("what should I work on?", "do you have the skills necessary to develop x?").
My project would involve assessing the information needs of the two main stakeholders-volunteers and Mr. Fitzpatrick-and developing an automated system that would enable them to communicate, and for Mr. Fitzpatrick to assign projects to various volunteers with no overlapping and no projects being unassigned. If development work gets beyond the range of my expertise, LiveJournal volunteers have offered to assist me. Furthermore, if my research shows that an existing over-the-counter application suits the needs of the company best, then I will recommend that.
Needs assessment: a combination of email surveys and interviews (with local volunteers), and an in-depth interview with Mr. Fitzpatrick.
Impact assessment: after implementing the project management system, I will have access to all project timelines, so I will be able to see if projects that were stalled are now being worked on. Furthermore, I will conduct follow-up interviews and surveys to assess the impact on individual volunteers, and Mr. Fitzpatrick.
I think this is a fitting project, because it draws from material I've learned in 310 (how people go about finding information), 320 (a method of presenting both the "volunteer list" and the "to-do list" in a rich, easily searchable manner), 380/381 (analyzing LiveJournal's business/organization and information flow systems), and hopefully 340 (making a database with volunteers and projects for them to do).
Client Information: LiveJournal (www.livejournal.com)
Brad Fitzpatrick (firstname.lastname@example.org), President
Letter of Support from Client: I have a hardcopy of it.
Equipment or software you needed: none.
|Saturday, December 1st, 2001|
|From Dave McDonald, design capstone leader
Some of the things you may want to consider as you continue to develop this project idea:
- What are the current technologies that support this volunteer organization and their communication? Is it necessary to build something new to support the project management aspects of the organization?
- If a new project management tool is necessary - what would the new tool provide that is not being provided by the current (in-use) technologies (or is not available in a commercial project management tool)?
You also probably want to think about what phase of the project interests you most; is it something about the needs assessment, is it something in the development of a new tool, or perhaps something about evaluating the impact of introducing a new technology?
|Monday, November 12th, 2001|
|Working Mission Statement
There is an information problem between the various volunteers working on LiveJournal, both between each other ("has x already been taken care of?") and between them and Mr. Fitzpatrick, LiveJournal's creator, ("what should i work on?", "do you have the skills necessary to develop x?").
My project would involve assessing the information needs of the two main stakeholders--volunteers and Mr. Fitzpatrick--and developing an automated system that would enable them to communicate, and for Mr. Fitzpatrick to assign projects to various volunteers with no overlapping and no projects being unassigned.
I think this is a much more fitting project, because it draws from material I've learned in 310 (how people go about finding information), 320 (a method of presenting both the "volunteer list" and the "to-do list" in a rich, easily searchable manner), 380/381 (analyzing livejournal's business/organization and information flow systems), and hopefully 340 (making a database with volunteers and projects for them to do).
|Monday, November 5th, 2001|
It's been a while, and there's a lot to update. Jenny and I decided not to pursue Passdoodle as our capstone. There are a few options right now for me:
1. Labscape. A continuation of the project I am currently working on with Annie Foreman and Travis Beck. We are now working on the educational uses of Labscape, a ubiquitous computing system for a Biology lab. I'm worried a
2. (New!) Brad Fitzpatrick offered me a position with livejournal, as some sort of info/org manager. I talked with Batya about this, and as I expected, she voiced a few concerns. She wanted to make sure that the project is:
1. Dealing with an "information problem"
2. Making use of material learned in Informatics courses
3. Large enough in scope
I'm going to have to talk to Brad about how well the position will fulfill these criteria.
|Friday, September 28th, 2001|
Uh. Big changes to the future of my capstone may be in order. More on this after a meeting with Jenny and Vibha on monday.
|Tuesday, August 14th, 2001|
I thought it would be a good time to do a quick capstone update, since I'm going out of town tomorrow though early September. We finished up the user study, with n=13, and have done some preliminary analysis of the data. The main problem appears to be the small sample size, for making any statistically significant conclusions. However, if we wish to speak qualitatively or anecdotally (which we may spend most of our paper doing), we have many interesting findings. I won't go into them now, but the better ones will definitely be in the paper.
Additional hours: 48.
Total hours: 128.
|Friday, July 27th, 2001|
Today I'm pretty sure I know what I'll be doing for capstone. I had a meeting with Jenny and Vibha about the future of the passdoodle project, and here's what we came up with:
This summer: complete the paper-prototype user study, and full analysis on the data. The goal is to write a 2 page paper for CHI 2002 now.
Winter Quarter: For the "meat" of the capstone project we will run another user study, with the working prototype and prepare a full length paper for CHI 2003
Batya says that I'm supposed to be keeping track of my hours. That's going to be kind of hard, but I've probably put in about 80 hours so far.
|Friday, September 7th, 2001|
I met with Jenny and Vibha today, after a few week hiatus. Turns out that not much work was done on the project since I left as Jenny was focusing on her AIBO project. We mapped out our work for the duration of Fall quarter. The Student Poster deadline for CHI 2002 is December 7. If our paper gets accepted, Jenny and I will both get to attend the conference! We will spend the rest of this month analyzing data from the user study. Then October we will write the two page "extended abstract" and put the poster together. November will be a buffer month for further iterations of the paper and poster. Vibha stressed that she wanted to see high quality work, and that she will help us in any way to get it done. We plan to meet once a week once class starts.
I have a meeting with Batya the last week of September to get her up to speed on my work over the summer.