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: Imperfection is the Way to Agility!

    The term "perfectionist" is one that most people are familiar with. Either because we are one or we know someone who is one. Many times, being a perfectionist adds a ton of value to your work, your team, etc. As one, you are driven to do the right things to a level of detail most won't go to. You may...
  • 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: The toughest question you can ask, isn't tough enough

    One skill all engineers need to have in order to ship high quality software is the ability to ask hard questions. No matter if you are a developer, a tester, or a project manager, you need to look at each situation, line of code, architecture/design, or user scenario and determine if you and your project...
  • Blog Post: Tribal Knowledge and Engineering Don't Mix

    In many engineering teams, having tribal knowledge is normal and accepted. This is when information about a product, process, or technology owned by the team is described verbally from person to person, release after release, without writing it down. Or if it is written down, only a select group of people...
  • Blog Post: No Crystal Ball Required

    One of the most challenge skills to master is long-term planning. This skill is needed for many different tasks at work, especially around project planning, budget planning, and (at a personal level) your career planning. Long-term planning is needed in order to get the most out of these exercises. In...
  • 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...
  • Blog Post: Do Whatever It Takes!

    I had a test lead years ago that did a great job at setting expectations for his people. But for himself, his main goal was always stated as "do whatever it takes to ship the product". This was really difficult to measure him against. But the concept is an interesting one. Many teams fall somewhere in...
  • Blog Post: Action-oriented vs. Results-driven

    In many project teams, I see people mistaking actions for results. One of the best inputs a manager can give to a team is to evaluate when the team is too action-oriented and guide them to be more results-focused. If a project team is always really busy and working long hours but then they keep missing...
Page 1 of 1 (8 items)