Author Archives: Mik Quinlan

About Mik Quinlan

Java Technical Architect and Agile Mentor with more than 18 years experience. I specialise in helping organisations adopt Agile methods effectively, developing strategies for effective cultural change and implementing hands on with the team, and turning cultural change into returns with visible ROIs. You may contact me via LinkedIn at https://www.linkedin.com/in/mikquinlan/ or on Twitter @MikQuinlan.

No more burndown, no more definition of done

Posted on July 28, 2013 by Mik Quinlan

Over the last year and a half of effectively working with 1 week iterations, two aspects of the traditional method of running an Agile project have not been required for us.  The first is the burndown chart, and the second … Continue reading →

Posted in Agile, Software Execution | Tagged | 4 Comments

Presentation on Behaviour Driven Development available

Posted on May 13, 2013 by Mik Quinlan

Here is the presentation I gave to the Los Angeles Java User Group about BDD and its application using Cucumber in the following contexts: testing REST APIs, testing web sites (integration with Selenium) and testing Hadoop / Hive. The slides … Continue reading →

Posted in Agile, Software Execution | Tagged , , , , , | Leave a comment

Blackbox testing, Whitebox testing and Behaviour Driven Development

Posted on March 7, 2013 by Mik Quinlan

As I have mentioned before, I have been involved in the re-platform of the Inventory system here at Shopzilla for the last 14 months.  During this time we got to experiment with a couple of approaches with great success.  One … Continue reading →

Posted in Architecture, Software Execution, Technology | 1 Comment

Re-platforming a system and the value of 1 week iterations

Posted on March 7, 2013 by Mik Quinlan

For the last 14 months I have been working at Shopzilla to re-platform the Inventory system.  I haven’t had the time to blog about what we experimented with, what worked, what didn’t.  This is the first of a number of … Continue reading →

Posted in Agile | 3 Comments