Hailing from the cold, frozen tundra of Minneapolis, MN, I rely on the combined heat of my two cats and several computers to stay warm through the long dark winters. I am the Project Center Manager at Magenic Technologies, responsible for project management, project methodologies, and delivery quality across our client engagements.  I see successful project management, especially for software projects, as a large Rube Goldberg machine with many different parts all affecting each other, but coming together for a positive result.  I have a passion for figuring out those linkages and trying to improve them through measurement and innovation.

You might notice that just as many of my blog entries are focused on Team Foundation Server as on project management in general.  I see TFS as one of the best innovations for the management and metric-izing software projects.  This means we have the ability to control and apply standard DMAIC methods to agile processes.

I am a frequent contributor to the Microsoft Forums and was a contributing author to the Syngress Windows Server Enterprise Administrator Certification book (Chapters 2, 7, & 10)


4 thoughts on “About”

  1. I’m wondering why you choose fixed work when setting Project 2010 for agile. I thought that fixed duration would be more appropriate. With the duration of the task to be the same as an iteration and the variable being the percentage of a resources time spent on the task.

    EG Iteration duration 15 days
    Task 1 Duration 15 days Resource1 15%
    Task 2 Duration 15 days Resource1 7%
    Task 3 Duration 15 days Resource1 30%

    Overallocation occurs when a resource allocation is over 100%

    1. Most projects will have two different kinds of tasks: some that are truly duration-based (server builds, procurement process, legal review, time-boxed acceptance testing) and items that are work-based (building SPROCs, coding objects, writing reports). The real litmus test is whether the task could get done faster with more people on it. This is where the 9 women can’t have a baby in one month argument comes in, but this works well for macro-level planning and by the time you have the task decomposition done to a point where that really would be painful, you should have things broken into items that a single person is doing anyway.

      In my experience, development projects tend to rely on work-based tasks, using either hours or story points as their units of work. Setting the project plan up this way allows you to see that effect if you do have multiple people on tasks, i.e. the duration will shrink to get the task done faster. If you leave the project in the duration mode, it’ll just use the resources for the full time without adjustment.

      In leveling the plan, you will still see accurate resource allocation but now you have the option to let the plan drive partial allocations against the task completion dates and even start and end dates. This lets you decouple those and use project rather than having to plan out the percentages yourself, though this might be uncommon as many work-based tasks are usually done serially rather than in parallel.

      I hope that makes sense.

  2. Hi Sir,

    I need your favor,
    I installed TFS2010 on Win2008 R2 successfully, But my IT Infra team changed the Machine name. Due to which when i logged on The TFS Admin console says sql server databases are not available. some how i resolved the issue. but now i m unable to update the tfs2010 sharepoint products.

    Kindly guide me

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s