4 ms·
The "Delivery/Deployment" distinction is baseless and used as a justification for not shipping by people who are attached to old and burdensome change managemen
by slumdev 6y ago
The "Delivery/Deployment" distinction is baseless and used as a justification for not shipping by people who are attached to old and burdensome change management processes.
Software not in the customer's hands hasn't been deployed OR delivered.
Alternatively: Software undeployed is software undelivered.
- signal11 6y agoNote for people attached to old and cumbersome change management processes, eg ITIL: ITIL’s latest iteration, ITIL v4, has a track for “high velocity IT” which incorporates rapid release cadence, CD, etc and is described by them as suitable for “digital” organisations or organisations going through digital transformation. I laughed a bit at this because this is just ITIL playing catch-up, but still, it’s a useful data point to get some ‘stuck in the past’ people to see that the “old Enterprise IT ways” are no longer un-challengable.
- changemgmtproc 6y agoI've always found the change management tooling backwards. Force the developer to aggregate the data so that auditors have an easier life when they check a single change once a year. Why doesn't the tooling just hook into the existing data sources that already provide the data for auditors. like PRs, testing data, JIRA tickets, etc...