Archives
April 2011 (1)November 2010 (2)
October 2010 (1)
September 2010 (2)
July 2010 (1)
May 2010 (4)
February 2010 (1)
Sections
Announcements (4)Asking for help (1)
Presentations (2)
Progress posts (5)
Progress Post Type
EndUser (1)Methodology (1)
TechStandards (1)
FinalReport (1)
ValueAdd (1)
Jisc Tags
UserCase (1)RapidInnovation (4)
VRERI (4)
JISC (4)
BlogMyData (4)
Implementation (1)
Productivity (1)
TechnicalDevelopment (1)
ProgressPosts (1)
VRERI (1)
JISC (1)
BlogMyData (1)
DisruptiveInnovation (1)
ProgressPosts (1)
Tools
Show/Hide Keys
Progress Post Type: methodology
Jisc Tags: implementation;productivity;rapidInnovation;VRERI;JISC;BlogMyData
Just a few notes on how we are collaborating as a project team. In addition to this public blog (which contains announcements and progress posts; the latter are required by our funders to monitor progress), there are two private blogs, one containing our to-do list and another containing helpful hints we'd like to remember for the future. Although there may be better tools for issue tracking, by keeping all project information on one site we make it easier to collaborate and record information.
As the project manager, I find the to-do blog extremely useful for keeping track of what's going on. This blog engine contains some useful features such as key-value pair tags and Sections, which make it easier to categorize posts and get close to the functionality of dedicated issue-trackers. Unfortunately the unusual tagging system of this blog engine makes it hard to follow JISC's requirements of adding standard tags to progress posts. I hope that having a separate section for progress posts, and a dedicated tag for "Progress post type" will help our funders find the information they need to monitor us.
(The two private blogs may one day become public - but at the moment there is little of interest to outsiders and we don't want to increase the noise.)
Each post in this blog is automatically tweeted, for those of you who have joined the Twitterati and are interested in following our progress.
We use Skype to hold somewhat-irregular meetings of the project team, working off the outstanding entries in the to-do blog.
We are in the early stages of working with users to improve the system; these users are based at the University of Reading, and so I am visiting them personally as often as we can arrange to gradually iterate towards a useful solution.
Jisc Tags: implementation;productivity;rapidInnovation;VRERI;JISC;BlogMyData
Just a few notes on how we are collaborating as a project team. In addition to this public blog (which contains announcements and progress posts; the latter are required by our funders to monitor progress), there are two private blogs, one containing our to-do list and another containing helpful hints we'd like to remember for the future. Although there may be better tools for issue tracking, by keeping all project information on one site we make it easier to collaborate and record information.
As the project manager, I find the to-do blog extremely useful for keeping track of what's going on. This blog engine contains some useful features such as key-value pair tags and Sections, which make it easier to categorize posts and get close to the functionality of dedicated issue-trackers. Unfortunately the unusual tagging system of this blog engine makes it hard to follow JISC's requirements of adding standard tags to progress posts. I hope that having a separate section for progress posts, and a dedicated tag for "Progress post type" will help our funders find the information they need to monitor us.
(The two private blogs may one day become public - but at the moment there is little of interest to outsiders and we don't want to increase the noise.)
Each post in this blog is automatically tweeted, for those of you who have joined the Twitterati and are interested in following our progress.
We use Skype to hold somewhat-irregular meetings of the project team, working off the outstanding entries in the to-do blog.
We are in the early stages of working with users to improve the system; these users are based at the University of Reading, and so I am visiting them personally as often as we can arrange to gradually iterate towards a useful solution.