Tag: agile
-
How to tell if you’re doing agile wrong
I really liked my co-worker Paul Kelly’s post on this topic, plus some anti-patterns. So I made the video above! You may recall him from a discussion with Cora and me a few months back as well. Even if you don’t deign to watch my silly shit above, you should check out his post. Relative…
-
Everyone is Busy: Who Has Time to Transform? – Mark tries to crack the “how to engineer a corporate structure, plan, and incentive plan to actually change” problem of digital transformation. I think the answer is: make small goals that you do on a short (quarterly) basis instead giant, waterfall annual strategy plans. // “My…
-
why pair programming improves how large organization develop software, a case study
Pair programming has been around since the late nineties and boasts ample research and anecdotal evidence proving its effectiveness. It’s not limited to programming, either; it can also be valuable in roles such as product management. However, despite its benefits, it remains less commonly practiced than one might expect. Pair Programming in the Department of…
-
Pair Programming is a great fit for large organizations because of this one unexpected benefit. CLICK NOW.
I have another video today. You’ve heard of pair programming and you probably think it’s bonkers. Not many people benefit from this practice. Here, I go over how teams in the US military have been using pair programming to improve how they do software and spread that change to other teams. Some real DIGITAL TRANSFORMATION!…
-
The DoD: A Compelling Case for Extreme Programming – Good overview of why/how the practices in Extreme Programming (XP) help the needs of the military, and fit the constraints and challenges they have. For example, spreading knowledge with paired programming manages high turn over in staff.
-
202306 – apenwarr – ’If you take a single pull request (PR) that adds a new feature, and launch it without tests or documentation, you will definitely get the benefits of that PR sooner. Every PR you try to write after that, before adding the tests and docs (ie. repaying the debt) will be slower…
-
How’s DevOps been going?
Has DevOps reached its goals from way back in the late 2000’s: deploying multiple times a day and having developers work closely with operations people? Adam Jacob brought up this question in two interviews recently, on my podcast, interviewed on my podcast by Matt Ray this week (which I [cough] haven’t, well actually listened to…
-
Change Fatigue In Digital Transformation: Where Has All The Value Gone? – Ways to keep the digital transformation alive: Contextualize business outcomes; Share the effort; Share the value; Conduct holistic load management; Target smaller, more frequent wins; Have a playbook; If you can, adjust incentives.
-
How Agile Value Management Creates Value Faster – Some metrics for measuring progress.
-
It’s the agile mindset that matters for local government – getting local government to do agile is difficult – “Local government culture is heavily business case driven, where funding is unlocked by making promises around outcomes in one, two or more years’ time. There’s also decades of learned behaviour to overcome, where people are just…
-
CD Foundation Releases Fourth State of Continuous Delivery Report, 2023 – In these surveys (based on big SlashData surveys), Since 2020, the reporting on the deployment frequency breakout has held steady: ~35% more than a month, ~32% a week to a month, ~22% hourly to weekly, ~10% multiple times a day. These are a lot…
-
The Silo Unifier’s Paradox
If no one owns the problem, no one can fix it – The Silo Unifier’s Paradox Solving the IT silo problem is challenging as there’s no one person responsible for the entire process. Each solo is owned by different groups like software developers, operations, security, project managers, and more. These groups often have competing goals,…
-
They were just wearing Levi’s because of what it symbolizes
Not much time for original content today: a Link Gourmand, my own links, the wastebook, and quick chair. Garbage Chairs of Amsterdam Garbage Chairs of Amsterdam, March, 2023 For several years, I took a lot of pictures of thrown out chairs in Amsterdam. Here’s a small selection of early ones – I’ll have to upload…
-
🏨📺🥶 Pieter Bruegel’s Discount Motel, Color TV, Cold AC
Generic Plan for a Starting a Platform Team in a Large Enterprise On Friday, I had a discussion with someone just starting to think about how they’d put a platform in place at their very large organization. I have my ever evolving prattle about that, of course. But rather than talk about (only) that, I…
-
Publishing Versus Orchestrating
Publishing Versus Orchestrating You can focus on short term delivery, or long term delivery. Do you follow the Twitter drama day-to-day, or just wait every week or two to see what happened? Do you write an article in a day or two, or write a 40 page PDF in a month, 120+ page book in…
-
Be less reliable – Coté’s Commonplace Book – Issue #49
How I find time to make thumbnails for my enterprise videos. Sorry, I flaked The most operational self-help tactic I’ve learned in years is: get comfortably flaking out on things. Missing meetings, being late delivering things, being unreliable, skipping studying Dutch today (and tomorrow)…just failing at living up to your full potential. This thinking works…
-
🗂 Link: Deutsche Bank to set up innovation division to drive digital transformation
The bank will create agile teams where “product owners in business and infrastructure divisions will lead teams of technologists, using agile principles, to continuously work on products and ensure progress meets their expectations”. It will also increase the proportion of software engineers in the workforce and better support and motivate them, as well as “reduce…
-
🗂 Link: The Air Force Software Revolution
For example, at Kessel Run, they tried different-sized teams before deciding that about eight people make up the ideal product team. They also learned not every big idea worked as planned. Source: The Air Force Software Revolution
-
Notes on the 2019 DevOps Report
Some quick notes and callouts from this year’s 2019 DevOps Report: Four key metrics: lead time, deployment frequency, mean time to restore (MTTR) and change fail percentage. Med, High, and Elite all have a change fail rate of 0-15%. So, expect 15% change fail as benchmark worst case to shoot for…? Demographics: 30% are devs,…
You must be logged in to post a comment.