You might have noticed it has been a while since I should have updated our blog to incorporate Part 2 of our Managing Multiple Projects series. Since those carefree, innocent times, we have all learned a lot about what are possibly the worst conditions to work under during a pandemic.
There is an apocryphal story about a management committee meeting with three items on the agenda: design a power plant, build a bike shed for employee use, supply refreshments for the Welfare Committee. The story goes that the first item was approved in a few minutes. The second item turned into a forty-minute discussion about what color the shed should be and who should get to use it. The third item it was decided, after deliberation, did not have enough information to make a decision, so it was added to the next planned meeting’s agenda. The vast majority of the time in the meeting was spent on the least consequential of the agenda items. This is bike-shedding.
Here we have yet another blog article espousing all the ways to break through roadblocks to getting your project over the line and into your customer’s hands. I don’t know how much of this will be new. Probably less than 1%. That doesn’t mean it is irrelevant. Time and time again, I run across teams who have trouble covering the last 10% of the ground necessary to release their project.
Read the rest of this entry »
One of my favorite things about working at CodeNoise is the ability to work on multiple projects. Variety in the types of products we work on gives me a lot of fresh new challenges that are interesting to solve. Sometimes, the process of working through problems with one product can provide helpful insight into totally unrelated products.
As with everything, variety also has its challenges. One of the operational hurdles people ask us about is how we manage to keep multiple projects on track at the same time. Read the rest of this entry »
