Project Management
Chris Sells, mensa member, Windows coding hero and all around guru has posted some great tips for project managers (program managers for those in Microsoft). I wish all project managers would follow his advice.
PM Skill #0: Know Your JobPM Skill #1: Communicate, Communicate, CommunicatePM Skill #2: Building ConsensusPM Skill #3: Getting Things DonePM Skill #4: Exhibiting the Behavior You WantPM Skill #5: Unblock Others FirstPM Skill #6: Be The Team MomPM Skill #7: Use That Meeting Time!PM Skill #8: Give Credit FreelyPM Skill #9: Learn From The MastersPM Skill #9B: Team Offsite
Now Playing: MercyMe - Here Am I
Scoble reports that there are a whole bunch of videos on Visual Studio Team System at TeamStystemRocks.com. See everyone, Scoble can be right about some things. Keep doing what you do Rob.Now Playing: Simple Minds - Don't You (Forget About Me)
I’ve got to check the Channel 9 Video feed more often. Channel 9 posted a ten minute chat with MS head honcho Steve Ballmer. It’s an interesting video. The one thing that I found surprising was Ballmer’s energy. I always thought that his energy level was more of a sales pitch thing than anything else. Kinda like the way radio DJ’s are always over exaggerating things. But it seems like he’s really like that. Now it could be that he’s just hamming it up for Channel 9 but I don’t think so. Note to self: a good leader should...
This talk focused all on demos.
Team System will incorporate a code coverage tool.
In the code coverage tool you can drill down to the module level.
It also shows which lines of code in the application have or have not been tested. It shows this information by highlighting the lines of code in different colors.
Testing code will still have to be written by hand. The real question now is how to get my team to write the code??
Writing a rule for the static code analysis tool (FXCop) is hard. They say that it's a couple of days type...
I didn't have any notes on this one…so shoot me. Essentially, three members of the Visual Studio Team System team talked about Team System and its features. One feature of note was shelving. Shelving occurs when a developer wants to place an unfinished piece(s) of code into source control. Since the code is unfinished it is undesirable to place the code in the main source code control system since it will probably break the build. The developer can "shelve" the code outside of the main source code control so the code is safe and the build remains unaffected. Nice.
I saw this and I did a double take. It looks like that there is a team of developers that will be unifying the N-tools (NUnit, NAnt, etc) under one project called NTeam. It sounds like a good idea after the blogsphere blew up (see Rick LaPlante, Eric Sink, and Eric Bowen) one the Visual Studio Team System (VSTS) pricing announcement. I just can’t see NTeam 1) replacing Visual Studio 2) replicating the VSTS feature set. The major problem that I’ve had with the N-Tools is the documentation. When MS releases VSTS it will have numerous knowledge base articles, magazine articles, a...