Key Trends Shaping the Future of Infrastructure.pdf
The Gathering February 2017
1. “Our vision is for a Scotland where people who
are disabled or living with long term conditions
and unpaid carers have a strong voice and
enjoy their right to live well.”
3. Our agile principles
We value teamwork and individual skills and
experience over processes and tools.
We value working software over writing about working
software.
We work with people and not for people.
We respond to change over following a plan.
Source: http://agilemanifesto.org/
Editor's Notes
Thanks Sally for the opportunity
Hi my name is Douglas
I work for H and S C A S and we exist to help disabled people, people living with long term conditions and unpaid carers have a strong voice and live well.
I’m here today to showcase our agile development approach in designing and delivering a new and greatly improved ALISS service.
ALISS is A Local Information System for Scotland and it helps people find and share resources that support health and wellbeing.
We’ve took years of feedback, learning and analytics and started to re-design a new web service. So on the 6th January we launched a new beta or testing website.
So I’m going to give you a quick understanding of our agile development approach, the principles we are using and an example of how agile rocks!
So what problem does ALISS solve? – how do you link communities to local information and the local activities on their doorstep ?
10,000’s of great activities happen every day, and for a lot of these, you either don’t know about or miss out. ALISS is the place to put the really local type information that can help people live well.
We then share that with people through a range of routes. But we also strongly believe that the people best placed to know what's in their community is the people from that community. That’s why we want to make it easy for people to add and share the activities that mean something to them.
1 – we don’t have PIDs, requirements, learning logs, etc. (or most of the other PRINCE 2 stuff that’s costly and a bit scary) – we have a skilled team who have the autonomy and ability to think about our work.
2. We don’t write about building great software – we just build great software. That is the goal, that is the result, the outcome, the output
3. We don’t use Service Levels Agreements, contracts, technical specification documents – we work with people at all stages to deliver a great product.
4. We don’t have a monster Gantt chart that we follow religiously (well until the first minor delay , then it goes out of the window) – we have a high level roadmap that sets our direction and then our team, our users, our analytics and sometimes our gut feelings help us respond to change.
The beauty of working in an agile environment is our ability to respond to change.
During our 1st sprint we started to realise that our system for converting a location in text format to a place of interest on a map wasn’t as accurate as we needed. This meant when people were adding resources some addresses were not being found; e.g. we were trying to add Johnstone Swimming Pool, Ludovic Square, Johnstone PA5 8EE as a location but our geolocation software couldn’t find it. This meant the resource couldn’t be added.
Is this had happened in a Gantt waterfall type planning, it would have never been picked up at the planning stage so to deal with this we would have had to add pressure to our team, add additional costs to sort it or just pushed the end day further away.
But it didn’t, we quickly found the issue, we tested another mapping software and changed the back end service and shipped (made live) it in 3 days.
We’ve now moved to ArcGIS software and we’re monitoring the results, but it looks much more accurate already.
Now I’m going to leave you with in my mind the main benefit of agile…Shipping small changes regularly is the point of agile and everything we do at ALISS, to develop a great service that helps people to live well.
Thanks for your time