a new model for tech developments

We’ll it’s time to revist the issue that many of our tech developments have delivered late, been overtaken by other work requirements, and we are not generating enough creative ideas as a broad team. So, what shall we do about it? We’ll nothing serious, we just need to tweak the way we work. So, instead of the 3 month plans, weekly moodle tech meetings / targets, I’m proposing the following;

The three month plan – identifies projects (based on operational and development plans)

  • A key change is Moodle trac / RT tickets will be worked on as a week sprint – i.e., once a month, as opposed to the ongoing weekly set of targets.
  • Community merge is explicitly factored in as a 3 day work package (includes, merge, testing and tag update for Dave)
  • Unless bugs are mission critical then leave until the next month Moodle Maintenance Monthly Package.
  • SAMIS tickets become a separate monthly work package – all tickets bundled
  • between “intense” periods – usually the Moodle work slots the developer will be given some down time for innovative / creative development, i.e., do something blue skies …

If tickets are dealt with inside the week, then more can be prioritised.

The way it needs to work is, a week before the Moodle weekly work, there will be a number of meetings between the Moodle Team to decide on the targets / priorities. This planning meeting can be used to scope what people will need to ensure the jobs are done, i.e., if they need access to other systems (remember TurnItIn blog !!!)

At the end of each blog, there is a very quick “wash up” meeting, where we document what was achieved, and what wasn’t. This will be documented for the next block.

So how will this translate to James’s current three month plan?

April

  • Week 1 (2 days work) Moodle bugs and fixes, (3 days work) Housekeeping on Log Tables
  • Week 2 (2 days) SAMIS Work
  • Week 3 (3 days) TurnItIn Mop Up, (1 day) podcast
  • Week 4 (3 days) Community Merge

May

  • Week 1 (5 days work) Moodle bugs and fixes
  • Week 2 (2 days) SAMIS Work, (1 day) podcast
  • Week 3 (5 days) QR Code Development
  • Week 4 (3 days) Community Merge

June

  • Week 1 (5 days work) Moodle bugs and fixes
  • Week 2 (2 days) SAMIS Work
  • Week 3 (3 days) Single Sign On, (1 day) podcast
  • Week 4 (3 days) Community Merge
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s