The Colorful and Gray World of Engineering Management

Embark with me on my journey through the colorful situations & challenges and the (gray) ambiguity of management in the software industry.

Browse by Tags

Tagged Content List
  • Blog Post: Fixing What's Not Broken

    Many engineering teams look at change as a bad thing, something that will disrupt their work. And granted, changing for the wrong reasons, or making changes for the right reasons but too many of them too quickly, can be disruptive and affect productivity. But you should also be careful about being too...
  • Blog Post: I Scream, You Scream, We're All Testing!

    Scream testing is an interesting concept, not so much applied to finding defects, but instead to clean up your processes. In the engineering world, we have a habit of creating a lot of things, yet have a very difficult time retiring things, whether those things are projects, hardware, automated test...
  • Blog Post: What are Testers Thankful For?

    When I think about all the issues my QA team has to deal with to ship projects, I wonder as we get closer to Thanksgiving what they are thankful for. What makes their jobs easier or fun? Two things come to mind. Testers are thankful when their developers produce quality builds. Getting a build that...
  • Blog Post: QA or Test - does the name really matter?

    I've been the manager for many different teams. Some call themselves Test and some call themselves QA. Personally, I've found it easier to just use those terms interchangeably. But for many, there are two very distinct schools of thought about what a Test team is and what a QA team is. Maybe at some...
  • Blog Post: Everyone Wants To Test

    You are new to testing. You are sitting in front of your computer staring at the software you need to test. What do you do? Let's look at testing from a very basic level and maybe this will help you make progress. If you don't "get it" at this level, you should consider if being a tester is the right...
  • Blog Post: Play with fire, but don't get burned

    Instrumenting your product's source code to get an indication of how much of the code was covered during testing is a really, really smart measurement to get. If you aren't at least measuring this number, you should be. Visual Studio provides features that continue to make this easier. What does this...
Page 1 of 1 (6 items)