Advisory Council on IT assessment (AcICT) Unique mandate to advise Dutch Government and Parliament Independent body Published advice (open access) on: – feasibility of IT-projects – maintenance and management of information systems – improving uniformity, quality and efficiency of information systems Tasked to provide knowledge transfer and knowledge promotion 5 members with background in private & public sector and academia Staff organisation of 20+ FTE Mandatory request for advice on IT- projects over 5 million euro by: – ministries – independent administrative bodies – police & council for the judiciary Per year 15-20 reports on high-risk projects with a total value of over 1 billion euro
Audit Elias Parliamentary Committee 2012 – 2014 2015 – 2020 Bureau IT-assessment (BIT) Extension BIT mandate with police and council for the judiciary 2018 2019 Decision minister IKR (BZK) about future of BIT Institutional decision Advisory Council IT-assessment 2021 – 2024 2024 Law Advisory Council IT-assessment in place Brief history The importance of metrics in the success of IT-projects 4
cannot compare it to anything? Size of new software is not always known Experience from the own organisation is not taken into account Experience from similar organisations is not taken into account Bottom-up plans can give the impression of a solid estimate How good is your estimate? The importance of metrics in the success of IT-projects 7 Use a reference Use multiple approaches Learn from the differences
linked to the way the estimate has been created What’s your status? The importance of metrics in the success of IT-projects 8 Use a repeatable metric Report where you are Report where you want to be
ever discussed in retrospectives or PI-events And also hardly ever questioned by management How predictable are you? The importance of metrics in the success of IT-projects 9 Make predictability a key metric Use numbers in retrospectives Limit Work in Progress Blue line is the number planned story points Orange line is the number of realized story points
(not) to do Prioritization done at a low level can frustrate high-level goals Where is the focus? The importance of metrics in the success of IT-projects 10 Set and communicate priorities Limit Work in Progress Mgmt presence at PI-planning
is a good practice to have requirements ready 2-3 sprints ahead Reprioritization done at a high level can frustrate work-level productivity Where is the priority? The importance of metrics in the success of IT-projects 11 Never reprioritize during a sprint Preferrably not during a PI or a release
Have you ever seen size in a risk log? Evolution is better than revolution Size is a risk in itself The importance of metrics in the success of IT-projects 12 Keep it simple Define small steps Control scope growth