This post on learning lessons is a week late. Learning the lessons at the end of each milestone rather than at the end of the project is a key POC characteristic.
The effort put into the Show and Tell 1 paid off. Everyone was engaged with the topic and there were even a few laughs. They asked good questions, raising some issues we hadn’t considered before.
We reflected upon:
- what we did,
- how we did it,
- the issues people raised,
- what we did well and
- what could have done better.
The Show and Tell
- Availability of people on a Friday. Should we test on a different day? Look at Thursday. We are looking for opportunity for better feedback – giving people time to think about the presentation but not too long like the weekend.
- Use of major image to illustrate the most important concept worked
- The Show and Tell clearly demonstrated what the IOs really do.
Show and Tell Issues raised
Copyright
- what is specifically copyright: a bookmark? a tag? a collection of bookmarks?
- who owns the copyright? del.icio.us or the bookmarker or no one?
Communicating with the users of del.icio.us
- should we tell them even though the del.icio.us has an public bookmarks and open API system?
- would identifying key users open the system up for abuse and distort the results?
Does this threaten the work that the employed IOs do here?
- [Response:no - EDITH is designed to provide the IOs with better tools which better utilise their expertise and really add value to the discovered resources.]
- Invite IOs to attend POC2 meeting for their view of the EDITH project.
Vision
A point was raised whether ‘Users’ is right word in the vision. ‘Community’ was suggested as an alternative.
Are we really doing with ‘user engagement’. The approach is not engaging with users and the foreseeable
development path has a limited engagement (one way). Revisit next week.
Note to readers (you): we really would welcome your thoughts on this issue.
Process - worked well
Having POC1 being rolled into a real MyEdna project has given credibility to the POC process and some momentum. It is not as difficult to ’sell’ the idea that someone is doing work on the proof of concept.
- Using Yahoo! Pipes as a demonstrator to validate general principles was very very instructive for prototyping EDITH.
- Benefit of being flexible, providing the extra development week was very successful
- Collection Mgt is processing time intensive – this directly impacts on development time.
What we did
The real results impressed people. The raw list of users and links provided many interesting and useful results. Nick’s analysis of the results also revealed. which people at the presentation recognised some.
What we could do for next time
- Look at dedicated POC kit for processing - maybe an old computer.
Post a Comment