Some of the things that I've written about publicly in May 2023:
Some teams think that they have matured beyond the need for coaching, but the organization should think about the long-term and addressing turnover, growth, and other changes when deciding how to staff coaches.
The knowledge and background needed by a coach depends on what type of coaching they are expected to provide.
There is middle ground between "build, release, and fail fast" and "go live with a complete solution". This middle ground is highly applicable to regulated industries and more critical systems.
Even if you are practicing Continuous Delivery, having a synchronization point between the team(s) and key stakeholders is valuable to review schedules, budgets, and plan next steps.
To make the most use of time in a timeboxed iteration, prioritize automation and have well-defined boundaries for the team's work.
Having a cross-functional team is important to success, but having cross-functional individuals reduces risk.
It is rarely, if ever, possible to effectively estimate the time to build a software-intensive system, even if you have a set of requirements and a design.
Root cause analysis works best when analyzing a system. Having a clear and shared understanding of the system - people, processes, and tools and technology - is essential.
On generated code: there's no need to commit generated code to your source code repository and you shouldn't be enforcing style rules on generated code.
