MSTechEd Day 4: Thursday – Final day –
In the morning there were not many session that interested me. I did find a session on by Ben Day @PluralSight instructor covering SCRUM, QA, UAT & Test/Dev Release practices as they relate to development tools. Remember now, I am not a developer, but I do sit next to one. Working at a startup, individual roles or titles are less relevant that is the actual fundamental key to shipping a product, Do The Work. For myself this means that in addition to customer and partner engagement, a large component of my energy goes into taking the feedback I capture and doing Product (Solution) Design. Our developers already practice test-based coding in which as a feature is designed, prototyped and integrated into the product, iterative testing is performed in parallel at each stage to ensure that there are no unintended interactions as various moving pieces are stitched together. Significant components of traditional QA might be ‘boring’ to some people but it is nonetheless critically important to delivering a reliable product that hits the mark on DWYSYWD. This is why as much as possible, the ‘boring’ stuff should be automated to focus on the ‘fun’ stuff. Functional and Exploratory testing can be more fun at least for me, I enjoy putting on my chaos monkey hat and swinging through the buttons and screens, clicking and poking my cursor where it should be and feeding bad parameters to commanlines who didn’t want to see me doing that. Overall I strive to make my contributions to the product release cycle align with the principles of Jez Humble’s book Continuous Delivery.
Back to the conference though…. The remainder of Thursday I decided to invest more time in the Hands On Labs.
Fail. – Step 1. NTP sync problem between the VMs & hosts involved in this lab environment. Essentially there are a minimum of two VMs and two or more physical hosts involved in the lab setup. These are broken down as follows: a Domain Controller VM and a SystemCenter Virtual Machine Manager VM, the physical servers running Hyper-V hosts (2 in the lab I did) and then a File Server which could be a single server or multiple in a cluster.