Random Post: get_results("SELECT ID,post_title,guid FROM $wpdb->posts WHERE post_status= \"publish\" ORDER BY RAND() LIMIT 1"); $p=$post[0]; echo ('' . $p->post_title . ''); ?>
RSS .92| RSS 2.0| ATOM 0.3
  • Home
  • About
  • Team
  •  

    CHALICE: The Plan of Work

    DRAFT

    GANTT-like chart showing the interconnection between different work packages and participants in CHALICE – not a very high-quality scan, sorry. When there are shifts and revisions in the workplan, Jo will rub out the pencil markings and scan the chart in again, but clearer this time.

    As far as software development goes we aspire to do a Scrum though given the resources available it will be more of a Scrum-but. Depending how many people we can get to Scrum, we may have to compress the development schedule in the centre – spike one week, deliver the next pretty much – then have an extended maintenance and integration period with just one engineer involved.

    The preparation of structured versions of digitised text with markup of extracted entities will be more of a long slog, but perhaps I can ask CDDA and LTG to write something about their methodologies.

    The use case gathering and user engagement parts of the project will develop on the form already used in the TextVRE project.


    2 responses to “CHALICE: The Plan of Work”

    1. […] Historical Authorities with Links, Contexts and Entities « CHALICE: Open Licensing CHALICE: The Plan of Work […]

    2. Have you considered using a burndown chart for scrum WPs? The #cloudbank project used this to some affect and seeing the line fall down the graph helped drive them on in the end?