“In almost every case there are stakeholders who are moved by quantitative data (say the percentage of phone calls that could be avoided.) There are also other stakeholders who connect with qualitative human stories. The magic really happens when you offer both types of evidence. Telling the stories, and backing them up with data points for the cost or the impact of what is happening to people, this is evidence with impact.
Link: Without a formal mandate
“In almost every case there are stakeholders who are moved by quantitative data (say the percentage of phone calls that could be avoided.) There are also other stakeholders who connect with qualitative human stories. The magic really happens when you offer both types of evidence. Telling the stories, and backing them up with data points for the cost or the impact of what is happening to people, this is evidence with impact.
Link: Do you need a corporate vision in government IT?
“In an organisation like a local authority this is especially tough as they are such disparate entities. Think about it, in what strange universe does it make sense for a single organisation to collect taxes, deliver social care, pick up bins and operate transport? None of these and many of the other services councils deliver have much to do with each other, apart from the coincidence of local delivery… Coming up with a single vision or operating model for such an organisation is pretty tricky therefore, which makes it less likely that transformation teams are going to get one.
Link: Do you need a corporate vision in government IT?
“In an organisation like a local authority this is especially tough as they are such disparate entities. Think about it, in what strange universe does it make sense for a single organisation to collect taxes, deliver social care, pick up bins and operate transport? None of these and many of the other services councils deliver have much to do with each other, apart from the coincidence of local delivery… Coming up with a single vision or operating model for such an organisation is pretty tricky therefore, which makes it less likely that transformation teams are going to get one.
Link: “Let’s think about control. I’d struggle to find any engineers operating within a DevOps mindset eschew control of their production systems. I encourage the use of a CMDB, but again, it’s live, automatically updated, and software-based. It’s ca
“Let’s think about control. I’d struggle to find any engineers operating within a DevOps mindset eschew control of their production systems. I encourage the use of a CMDB, but again, it’s live, automatically updated, and software-based. It’s called a Chef server. Similarly, ITIL places a strong emphasis on configuration. Teams I have built do the same. All changes to the system are made in code, go through a peer review process, are automatically tested, and rolled out in a recordable, repeatable, and auditable manner.
Link: “Let’s think about control. I’d struggle to find any engineers operating within a DevOps mindset eschew control of their production systems. I encourage the use of a CMDB, but again, it’s live, automatically updated, and software-based. It’s ca
“Let’s think about control. I’d struggle to find any engineers operating within a DevOps mindset eschew control of their production systems. I encourage the use of a CMDB, but again, it’s live, automatically updated, and software-based. It’s called a Chef server. Similarly, ITIL places a strong emphasis on configuration. Teams I have built do the same. All changes to the system are made in code, go through a peer review process, are automatically tested, and rolled out in a recordable, repeatable, and auditable manner.
Link: Why You Need To Know About Low-Code, Even If You're Not Responsible For Software Delivery
“Low-code [uses] declarative techniques instead of traditional lines of programming… Common features include reusable components, drag-and-drop tools, & process modeling. Individuals or small teams can experiment, prototype, & deliver apps in days or weeks.” Plus, marketsizing: something like $4bn. Original source: Why You Need To Know About Low-Code, Even If You’re Not Responsible For Software Delivery
Link: Why You Need To Know About Low-Code, Even If You're Not Responsible For Software Delivery
“Low-code [uses] declarative techniques instead of traditional lines of programming… Common features include reusable components, drag-and-drop tools, & process modeling. Individuals or small teams can experiment, prototype, & deliver apps in days or weeks.” Plus, marketsizing: something like $4bn. Original source: Why You Need To Know About Low-Code, Even If You’re Not Responsible For Software Delivery
Link: Progressive Delivery, a History…. Condensed
“On the business side, Progressive Delivery involves two core changes in the delivery model:
Release progression – progressively increasing the number of users that are able to see (and are impacted by) new features (e.g. Stage 1: visible to developers only; Stage 2: visible to developers and beta users; Stage 3: visible to more users; Stage n: visible to everyone)
Delegation – progressively delegating the control of the feature to the owner that is most closely responsible for the outcome.
Link: Progressive Delivery, a History…. Condensed
“On the business side, Progressive Delivery involves two core changes in the delivery model:
Release progression – progressively increasing the number of users that are able to see (and are impacted by) new features (e.g. Stage 1: visible to developers only; Stage 2: visible to developers and beta users; Stage 3: visible to more users; Stage n: visible to everyone)
Delegation – progressively delegating the control of the feature to the owner that is most closely responsible for the outcome.