Organisations that have technical founders have a very different character to their work internally, need to make knowledge of the quality of software more pervasive – the business need to understand more about the technical side, and the developers need to understand more about the business
Code that has excessive error handling typically has other design problems – benefit in thinking about whether…
This is a special mashup episode recorded in Auckland, New Zealand. Craig catches up with Mark Derricut from the Illegal Argument podcast and Craig Aspinall from the Coding By Numbers podcast. Not your usual Agile podcast, the discussion starts around the definition of Agile (“crash often, crash regulary”) and trying to define quality and ends up in a chat about wicked problems, devops and software development skillsets.
This episode has been released on the other channels as well (take a listen if you haven’t already)
The second keynote was supposed to be Mark “Bomber” Thompson from the Essendon Football Club but he was an unexplained no show. After an impromptu thankyou speech from me and breaking the conference for an early break, James Hird arrived to substitute and did an impromptu talk. As a result of the scheduling changes, I unfortunately did not get to see much of either session.
time machine pattern – work an iteration or more ahead of the development team
UX is primarily about design, we are in two different worlds
embed the time machine pattern within Scrum
personas – focus on the pragmatic face of our users (David Hussman) – synthesise what we understand at the moment
added to GWT… Given I am a role AND I VALUE, When… Then…
grooming is the forgotten ceremony
involved the users in planning poker – got clear perspective in the context of their environment]
demo became a cognitive walk through
Emerging Paradigms in Software Testing
I was MC for this session for Kristan Vingrys from ThoughtWorks. I have known Kristan for a number of years, and I resonate very closely with his views on testing and testers. His slides are available here.
ATDD is a good way to break down the barriers between developers and testers
need to change focus to preventing defects rather than finding defects – measure yourself that more defects is bad
fast feedback – embrace continuous integration, automation and the test pyramid
involve everyone – crowd source your problems, tests are an asset, version control your test cases
change focus from how I prevent this going into production onto how I get this into production
build pipeline- stage build to run different tests in different stages in the pipeline
tester needs to inform the team of quality, not be responsible for quality
target testing to things that are changing, not just scatter gun
it’s about the principles, not the practices
test code is code – treat it like any other code
it’s important to know what you are not covering, more than what we are covering (Model Based Testing)
Design Eye For A Dev Guy
I was MC for this session delivered by Julian Boot from Majitek. This was one of the highlight sessions that I attended at the conference and as I remarked when thanking Julian, it reaffirmed how much I don’t know about good design. His slides are available here.
focus on data over labels – make the data bigger, keep your headings close to your data so you don’t get lost
hierarchy of actions, but use them properly
colour – use a designer, but if not use 3 colours in one shade and two others (using three grey is the best pro tip and two others)
let design be your brand, don’t overuse the brand
Agile Executive: The Naked Truth!
I was MC for this session led by Kelly Waters from ThoughtWorks and author of the All About Agile blog. I unfortunately did not get to see much of this presentation, the slides for which are available here.
I was MC for this session delivered by Tony Young from Integrated Research. This session was designated as “Expert” but there is nothing in this that I could see that made it that level. His slides are available here.
My presentation from Agile 2011 that I delivered with Adrian Smith called “The Speed To Cool: Agile Testing and Building Quality In” is available on Slideshare.
Ensuring that the approach to testing and quality is understood and appropriately valued in an agile world can be a struggle for many organisations, especially when resources are limited and our customers are expecting business value in a timely manner. In this session we will define what quality means and share a number of tools for measuring it, discuss approaches to improving the skills, empowerment and role of testing in the organisation and share why testing is the coolest role on the team and why it is everyones responsibility.
Some of the comments on Twitter included:
@BrianGress: We tend to test only what we can see. #agile2011 @adrianlsmith
@tonyrockyhorror: @smithcdau Speed to Cool was best talk I’ve seen all week. It will take a mighty effort to top it. #agile2011