Defining good ACs can be difficult, especially if you are undergoing a 'transformation' and are moving from traditional 'requirements' Lets talk about what makes a good AC.
All management is hard, and whilst you get told a lot of things as a new manager, these are things (on top of everything else!) I wish I'd been told. I probably wouldn't have listened.
In my experience, a decent walking skeleton is the most underused technique when teams are trying to de-risk software delivery. In this article I attempt to articulate its value so you want to use it more :)
On 'Why software development is like running a restaurant' and 'What analogy do you use to usefully describe the act of software development?'
How the future of software development is becoming more QA
Moving to #noestimates and relying on forecasting can be difficult for any person, team or organisation. Here I describe one way I go about it
"The uncomfortable world of constant discovery" or "The difference between Delivery and Product teams"June 12, 2019
A look at the differences between 'Product' teams and 'Delivery' teams
Understanding the best way to deploy serverless architectures and solutions
Some thoughts based on my recent exeperience in the healthcare domain
A summary of my thoughts on TDD (Test Driven Development), MDD (Monitering Driven Development), ODD (Observability Driven Development) & HDD (Hypothesis Driven Development). Phew.
An overview of different approaches to breaking down problems into slices
Even more examples of how to use CRC (Class Responsibility Collaboration) cards in your day to day work
Some examples of how to use CRC (Class Responsibility Collaboration) cards in your day to day work
A description of my 'go to' meeting for understanding the differing values across a team in a low trust situation
A short article on why I like Test Driven Development (TDD)