Skip to main content

Software Project Management with Visual Studio: Sharing Information Is Key

MSDN recently pointed to an article on the approach being taken in the Team system to software project management. What I found to be the best "take away" from this was "Getting crucial metrics about the project is important to track status, and to make decisions."

Status is important but so is severity and lifespan. The warning posted in the article is that "Often, the project lead becomes lost in the details of tracking and is not analyzing project risk or making course corrections on the project."

Well another big problem is making sure the leads stay AWARE of the issues going out. Whenever you distribute metrics, be aware that too many numbers simply make people ignore them. Of course, if you've already flipped the bozo bit on the person who gathers them, you're only setting yourself up for failure.

But seriously, just because a project may have 1500 open "bugs" doesn't mean it's impossible to figure out what to look at. Break them into quantifiable categories: reproducible, enhancements (like it or not, customers will likely see many ERs as "bugs"), critical, by design and others.

Our development team at one client has a rule: no critical bugs over 24 hours, no serious bugs over a week. Well, the problem with those rules is that how do you get rid of critical bugs? No - You don't re-categorize them to a lower level with a work-around.

Regardless of the tools people use to track bugs, the only way not to get lost in the metrics is to have some discipline about going through them. Maybe Visual Studio's Team System will help this (I'm still in the process of installing it as it requires a separate DB server).

I don't find the discipline that hard to work with: Critical within 24 hours, Serious within a week. After that, duplicated non-fatal bugs are looked at. Even if you only look at 5 a day, you're still chipping away at something and getting out of the death march.

But sharing the metrics are critical. We send out a daily status report on support calls and issues, followed by a weekly one with a larger breakdown and then a monthly summary. All of these are done through email. Sure, we could ask people to look at them on a web site but guess what? That makes it "someone else's responsibility". Put it in their face (although not as a pop-up ad) and then be brutal. There's no reason for people to say "I didn't know" if you have at least given them every opportunity to see what's going on.

And if your project lead becomes lost in the details, then someone needs to be trained better and soon.

Visual Studio 2005 Team System: Software Project Management


Popular posts from this blog

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator)

So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinctions I…

Security in Windows 10

 discusses some Windows 10 privacy settings and their implications.

"Finally, we will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary." "In other words, Microsoft won't treat your local data with any more privacy than it treats your data on its servers and may upload your local data to its servers arbitrarily"
I did a quick install on a VM choosing the Express settings. When I fully deploy this on a real workstation, I will likely choose to wade through all of the individual pages, as David recommends.

Of course, losing one's privacy is nothing new - it's happening all over the place (despite Santa Ana's police force's lawsu…


I'm not TRYING to be "fanboy-flame bait" but what I saw yesterday was a typical "Do it this way, now do it this way and then we'll go back to this way" all over again.... a move similar to what Microsoft does to developers on an ongoing basis.

Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.

Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"

Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.

Guess that means the iPhone 8 will be back to boxy.

And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming.  The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" wor…