So what an exciting first few weeks back we’ve had!
We started off nice and easy, picking up all the support requests that had been filed over the Christmas break and, after a suggestion from Kelvin last year, put together a demo of an augmented reality map of the University campus using Layar (which I will post more about later).
We also started preparing for our next set of work, delivering the most-requested features and fixes to our news publishing service, which is based on WordPress.
The shortlist of work we’d do was created in December during face-to-face meetings with members of the Press Office after which it was published on our wiki using the survey macro to give everyone a chance to vote and comment on which items were most important. At the same time, we got on with estimating all of the listed items so that once voting was complete we’d be able to balance the importance with how long they were going to take!
And then the snow came.
Fortunately the University had prepared for this already and an emergency telephone number had been set up with the current status of the campus and there were prepared news articles ready to be published. Of course, yet again the use of Twitter was instrumental in delivering the message that campus was closed as quickly as possible (and at least one person enjoyed their 7.30am tweet delivery!)
Sadly for us in Web Services, there are excellent remote working facilities provided by Computing Services, with a good VPN and remote desktop connection to work PCs and a wake-on-lan facility if your PC is off. There is also an instant messenger server which enables both one-to-one chats and chatrooms for groups of people which enables us to co-ordinate effectively even when we’re at home in our PJs.
The combination of remote desktop provision and web-based tools for documentation and issue-tracking meant we were able to complete the work for the news system on time. Now that the snow's melted we're just waiting for a moment to deploy our changes and show the Press Office what we've done!
After months of developing, beta testing, feedback and more developing we have launched our research website!
Research is the first of the core sites to be launched as part of the external website project and will be closely followed by study (due for launch in December).
Despite having a research presence before, the site did little to promote the world class research undertaken here at Bath. Unless you drilled down to departments and individual centres and groups our research was difficult to find from our central website. We've also invested a huge amount in a publications repository in recent years but this was invisible to our users.
The new site focusses on exposing this information and promoting it. Led by Web Services we have worked with a number of key stakeholders across the University including our Pro-Vice-Chancellor Research, Jane Millar.
It is the first in a long line of developments and it will evolve over the coming months (and years!) but I am incredibly proud of the team here and what we've achieved.
One down... many, many more to go!
Update: Due to a number of complexities the wiki upgrade has been postponed to Tuesday 29 September between 8am and 9am. Web Services apologise for any convenience this may cause.
Original message below:
The University wiki is due to be upgraded on Friday 25 September 2009. The upgrade will take us to Confluence 3.0 the latest version of the software which has substantially improved performance and a range of new features.
For more information watch the Confluence 3.0 overview video or read the release notes.
Please note the wiki will be unavailable between 8am and 9am on Friday to allow for this upgrade.
As of this time last year, the University Academic Year Charts have been generated in HTML, PDF and iCalendar formats from Excel spreadsheets. Previously there were only PDFs for download but we thought that providing versions to view live on the web and a version people could add to their own calendar software would be useful.
To take the burden out of maintaining all these different formats by hand we used some short Ruby scripts to do this (using libraries such as roo, pdf-writer, and icalendar).
Within Web Services we use the calendar plugin of our wiki to schedule who handles our frontline support on a daily basis (and then get it deliverd to us over instant messenger, as we've blogged about before) but it didn't show the University holidays, meaning that the support was somtimes unfairly balanced.
A screenshot of our support schedule plus University holidays
Yesterday we remembered that one of the year charts we generate just contains dates relevant to staff, without all the teaching days and student holidays marked in, and like all the others, we generate an iCalendar file for it, which the calendar plugin can read. So, a few clicks later and now our support schedule contains the University holiday dates as well as our custom-added events.
This means our calendar has an iCalendar input (the holidays) for human usage when we're updating the schedule as well as an iCalendar output (our support schedule) for robot usage when delivering our schedule directly to us! We've had to do comparatively little to enable this, neither of them have to be maintained by hand, and this is only a tiny fraction of the things that are possible, and all enabled because we use software which generates and consumes standard, open formats (and thanks to Tom Natt for making sure we did it!).
See how the news system was developed courtesy of a Tom Natt walkthrough.
(and if you know how to convert this SWF into an FLV file please let us know! The usual ffmpeg magic has failed us!)
Yesterday was a good day for Web Services as we not only launched the first of our 'new external website' projects but we've released the first application built using Scrum.
The publishing system for our news articles/press releases has been replaced with a new application built with WordPress. The decision as to why we chose WordPress has been well documented on our blog and wiki as has our adoption of Scrum but yesterday our users got to see what we've been working on and our colleagues in Corporate Communications got a new system to manage news articles.
We've had an internal article published (on the new system) which explains some of the background to the project and we plan to launch a video (showing the inside of the app within the next few days).
* Thanks to @lovelychaos for the title!
With apologies to Bassment Jaxx... Anyway. So we've been doing lots of WordPress development in preparation for the relaunch of our news system. One of the big reasons we picked WordPress was the plugin API and it's turned out to be a really good decision on that front.
Once I understood the basics of a plugin (thanks to Savin's 10 minute tutorial) - the architecture, how hooks work, how to render widgets - and accepting that it'd be easier to write code in plain old functions to get going initially instead of writing classes (gasp!) it took me a couple of days to write my first plugin.
After my first plugin, it took me a day to write my next plugin's first iteration. Working code in a day. All I had to do the next day was add one more feature. Then it took me another day to make it all jQuery-tastic.
Roll on writing more plugins in our next sprint!
In SCRUM there's an essential role that has to be fulfilled by someone who can't partake in the work tasks from a project. They are called the SCRUM Master.
That isn't to say that the SCRUM Master doesn't have tons of work to do. In fact, if they don't do their job properly, the "sprint" of tasks the team are to undertake isn't properly organised and hence affects their productivity.
So if you're not the SCRUM Master, surely you'd think that it's unfair as you're doing "actual" work rather than "mere" project management? Well no, in fact. The SCRUM Members (it's not an official term I don't think - I made it up. I'm imaginative like that) actually have it easier. Your entire focus is on your task at hand, nothing else, and that task should have been broken down into a working day-sized chunk but no more. You have nothing else to worry about, even when you get to a point that you can't do your work - that's for your SCRUM Master to do! They deal with impediments on your behalf you see
A recent example was when Phil had a pile of support queries to deal with which were stopping him from getting on with his project work. His SCRUM Master Andy Male took those tickets away from Phil and dealt with them, allowing Phil to get on with his tasks.
Essentially, it's the SCRUM Master's role to make it as easy as possible for you to get on with your work and from my observation that takes a lot of effort. With all that hassle taken out, working becomes much easier for the members.
A truly fair management style! The rest of Web Services seem to agree.
In the last couple of months we have started to use Scrum to manage our development projects. If you are within earshot of our office you will hear people using words like 'Sprint', 'Backlog', 'Velocity' and 'Impediment'. People have new titles, our clients are 'Product Owners', Phil and I have been 'Scrum Masters'. It's all quite exciting.
I've always felt uncomfortable with traditional project management but using an Agile project management methodology like Scrum eases all my concerns. It's fair to say that even if the waterfall method ever worked it's unlikely to be seen on the other side of this economic crisis, everyone needs to be more agile.
It's very easy to talk about our experience of Scrum as the process includes the 'sprint retrospective'. This has allowed us to look at how the last iteration of the project went and how effectively we are using Scrum to manage it. The Scrum Master takes responsibility for making improvements so that the next iteration is more productive.
The benefits we are seeing already are:
- The progress of the sprint is clearly shown through the use of a burndown chart
- The Product Owner has to tell us the priority of all the required features
- The team are committed to the sprint goal because they plan the work that is included in the sprint
- Any impediments to tasks are identified quickly at the Daily Meeting
- We are starting to understand how quickly we work (our velocity) and can therefore commit to realistic deadlines
We have started Scrum with relatively little pain, this is largely because of the enthusiasm everyone has shown. That being said it's interesting to see that often the reason cited for the failure of Scrum is that the team weren't rigorously following the process. We realise we haven't got this nailed yet so our expectations have been modified accordingly.
We need to learn more about things like estimation and how to start Scrum with clients who have never been closely involved with a development project. I'm looking forward to this as I think we are already more focused, productive and working more closely as a team.
I would be interested to know how other people are project managing or their experience of Scrum.
Hello and Happy New Year to you all!
As a followup to Kelvin's post on the topic, I thought I'd expand on some of the trials and tribulations we had adopting a new Java framework.
We've been developing all our most recent Java applications in Struts2. This has brought both tears and laughter but among the biggest problems we faced was that once we'd deployed a few of our apps to our live Tomcat server we realised that we couldn't deploy new a version without shutting down the entire instance, and therefore making all our other apps unavailable at the same time. Yikes!
It turned out that Spring, which we use for dependency injection, was holding onto a couple of our jar files even when we were undeploying the application. We'd seen this on some Windows development machines before but not on Linux or our Solaris deployment machines. This time however, the problem didn't occur at all under Windows, about half the time on Linux and 100% of the time on Solaris.
The way we'd dealt with this previously was to get the Windows-based developers to add
antiJARLocking="true" to a hard-coded Context in their server.xml which keeps the problem nice and localised.
That wouldn't work for our live servers since, as the documentation says, "applications that are outside the appBase for the Host will cause the application to be deleted on Tomcat shutdown." which means that for our configuration each time we stopped Tomcat would result in a number of applications being completely deleted!
We eventually solved the problem by writing application-specific META-INF/context.xml files that specified "
antiResourceLocking=true". This means that we can now deploy new versions of our applications and shut down our server without it deleting everything.
This was a reasonably pesky bug to track down since of course I couldn't use my local machine (where the bug didn't appear) or any of our standard development Tomcat instances since I could very easily be deleting people's applications every time I restarted the server. Lesson learnt though and we'll be paying more attention to the deployment configurations we use in future!