in Agile, QA Agile test curve
This post is an update to my original post Testing Curve. I’ve had a few emails asking for a more detailed graphic and some advise on avoiding the unhealthy test curve. Don’t allow test debt to build up in your Sprints. Start testing as early as possible. Tips on how to avoid the unhealthy test tidal...
Though many have drawn up double funnel models, a few days back whilst talking with Dan Brown (aka Kanban Dan) about constraints and Kanban, we modified his double funnel diagram by adding in a vice with the initial applying forces of Command & Control and as these forces are applied the blame force grows exponentially. So what does this...
Kaizen (改善), Japanese for “improvement”, or “change for the better” refers to philosophy or practices that focus upon continuous improvement Strangely I’ve never blogged about something I’ve implemented in virtually every Agile environment I’ve worked in recently, something I call Team Kaizen’s. Kaizen’s are often associated to Kanban, but there’s no reason why you cannot use...
Agile cheat sheet – The manifesto – http://agilemanifesto.org/ Scrum – All bold / italic test in Description area has a corresponding section Term Description Comparable too Done / Definition of Done One of the most over used and debated words in Agile is the word ‘Done’. Done in some organisations means ‘Dev Complete’ or ‘Testing completed;...
I wrote this in 2012, originally published on my old site before GoDaddy killed it by mistake, and reviewing my drafts I thought I’d add a small update about the debacle that is SaFE and then publish it again. I’ve even left in parts that have now evolved, but it is a good reference point...
in Agile, Delivery, DevOps, Engineering / Development What is a (genuine) high performing software engineering team
Recently I had an amusing conversation about everything Scrum transformation (early hours of the morning due to timezone differences). The person driving the conversation was keen to understand how to create a high performing software engineering team without leveraging on TDD, BDD, Pair programming or using any XP practices. To be clear, so that there can...
How often have you worked in an organisation that uses either 3rd parties or in-house development exclusively or a company that has tried (and often failed) to embrace the best of both worlds only to become unstuck as an us vs them mentality sets in? How often have you heard; Out sourcing this piece of...