Agile Digital Services (AgileDS™) - APMG International

The Best Guide To An agile life in GDS projects - Scott Logic Blog

We use some important cookies to make this site work. We 'd like to set additional cookies to understand how you use GOV.UK, remember your settings and improve government services. We likewise utilize cookies set by other sites to assist us provide content from their services.

GOV.UK is counted on by countless individuals every day to access essential services and details. Product published on GOV.UK can move financial markets. GOV.UK is an important part of our national infrastructure. But GOV.UK differs from many other pieces of nationwide infrastructure in one respect: we built it and we run it utilizing agile.

GOV.UK has actually always been and will continue to be agile at scale. But being agile doesn't suggest merely setting up a methodology and then religiously sticking to that methodology. It implies adapting what we do based on what we have actually discovered. And this consists of adapting our methods of working. A bit ago we learned that we had a few obstacles with GOV.UK delivery.

How do you divert a waterfall..? - ESFA Digital

Getting The Three lessons on how Singapore built an agile government To Work

Here's what we did and what we discovered. We built GOV.UK really quickly. It launched in 2012 and simply over a year later it was hosting all the content for 24 ministerial departments and 330 organisations. By 2015, it had actually changed the sites of 1,882 federal government organisations. But doing all this had actually come at an expense.

And the variety of people working on the program had changed, suggesting that there wasn't much stability. As the program developed, it was time to go back and review our methods of working. By the start of last year, we observed 4 issues that were affecting shipment: as due dates might be flexible, in some cases work wasn't stopping higher clarity was needed on the most essential issues research study effort wasn't always reflected in shipment we had a lot of possible single points of failure So we put in place a brand-new way of working to deal with these.

That was due to the fact that every 3 months we wanted a real re-evaluation point where we could state: "Do we definitely want or need this work to continue? What is the engaging proposal for another 3 months on it?".  Another Point of View  kept the time period short due to the fact that we desired to develop in the flexibility so that we might change instructions, if we required to.