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

Comments

Popular posts from this blog

Attending Southwest Fox 2019 could change your life - Find out how

Southwest Fox is coming up in October and as I do every year, I spoke with the organizers Rick , Doug and Tamar on the FoxShow. Deadlines for Southwest Fox: Super-saver price (before July 1): $695 Early-bird price (before August 1): $770 Regular price (August 1 and later): $820 This year, I took a different approach with separate shows for each organizer but the main message is still the same : July 1st is their Go/No-Go date. Conferences don't talk about this very often. I don't think developers really question if Apple will hold their WWDC in June or Microsoft will hold their Build conference - but that's because those conferences are vendor-led. Southwest Fox is a community-driven conference - it's not driven by a company with an agenda. Listen to the interviews and you can hear how important each of the organizers feel the live connection between speakers and among attendees.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub . A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article  : "...   people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack? Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP