As part of the external website project to create a new, centralised, section of the website for research information, the digital communications team has taken a slightly new approach to how we engage with stakeholders.
Friday 2 March 2018 | Agile
Let’s say you have a team of eleven knowledge workers, who have a wide portfolio of responsibilities, and you need to get a bunch of tasks done, across multiple projects, within a two-week window. How would you keep focus on …
Tuesday 30 January 2018 | Agile
Backlog refinement One agile practice that we’ve adopted from Scrum is that of product backlog refinement. In short, it involves representatives from both the project level team (project manager, business visionary, technical coordinator, etc.) and solution development team getting together periodically …
Monday 13 March 2017 | Agile
Back in August I wrote a post called “How do you know when you’re done?” in which I explored the agile concept of the “definition of done” or “done done”. However, in conversations with developers over the last few weeks …
Wednesday 14 December 2016 | Agile
Over the last couple of months we’ve had a number of requests from people and projects, somewhat out of the blue, asking for pieces of work to be completed with a deadline within only a couple of days of asking. …
Friday 9 December 2016 | Agile
I first encountered Agile at the Scotland on Rails conference in Edinburgh in early 2008. While much of the conference (about Ruby on Rails, a server-side web application framework written in Ruby) went sailing over my head, the keynote speaker …
Friday 25 November 2016 | Agile
I recently attended a time management training course put on by CAPOD. The session was very insightful, providing useful and practical techniques to become more efficient at work. However, during the session I realised that many of the time management …
Wednesday 12 October 2016 | Agile
How do you know when you've completed something? Agile invites you to define "done done" so everyone on the team knows.
Wednesday 31 August 2016 | Agile
This guide shows how the 60/20/20 proportion of must, should and could requirements in Agile MoSCoW prioritisation is against effort not number of requirements.
Friday 5 August 2016 | Agile
I've been thinking a lot about risk in Agile projects recently. It is something that I've known for a while we need to manage better. Here's some of what I've discovered so far.
Monday 27 June 2016 | Agile