Skip to main content

Iteration 0

This week is my iteration 0 for the project I’m on. It’s the first project that I’m going to be the lead architect on. This is something that I’ve always wanted to do, so it’s very exciting for me to get my first taste. I have some great people around me and some mentors that I know I can go to for some help when (not if) I need it.

The project is a redesign of a client’s public website. The current website is written in Cold fusion and has a shopping cart functionality that is achieved using Comergent. We’ll be redesigning the site using ASP.NET. We’ll be leveraging the functionality of Commerce server 2009 for the shopping cart functionally as well as interfacing with SAP for billing/shipping/product information. On top of that the client is using Interwoven as a Content Management system. We’ll have to build a custom DB that Interwoven can write to and that our Website will query to get non product related information.

My biggest problem so far is trying to fit the Agile/SCRUM methodology into a consulting project. Normally in an Agile/Scrum methodology you’d get some high level requirements, sit down and figure out the most important ones, do the estimates and start the work. Not too many clients will allow a consulting firm to come in and build something on Time & Materials basis so we’ve already taken the time to sit down with the clients and get a feel for the development and given an estimate. This is a common Iterative/waterfall methodology. Finding a balance between the two is tricky and I’m bound to learn lots of lessons. Anyone got any words of advice for me?

Anyway, I’m like a kid on the first day of school. I’m excited for the opportunity, but worried about how things are going to go.

Wish me luck!


Popular posts from this blog

Build/Deploy Windows service with TFS

Building and deploying a web service or website via TFS is pretty straight forward, but automatically deploying a windows service or console application takes a b it of setup. I’ve outlined the steps below to get your service deployed. Step 1: Set up Automated Build and MSDeploy on the Target server. If you are doing any sort of automated build/deploy I recommend using MSDeploy. You can follow steps 1-3 from a previous post here.Step 2: Edit the .csproj fileThe project file for the app you are trying to deploy needs to be edited so that TFS will create a directory for the output of the project. Otherwise the project will be built, but the assemblies will be placed in the code drop location with no organization to it.To edit the file, go to the open file dialog and locate the csproj file. Select it but don’t click “Open. Instead click on the dropdown arrow next to the Open button, select “Open with”, and choose the XML (Text) editor as shown:Once the file is open, add the following “Pr…

Quickly and Easily Deploy Websites/Web Services with TFS Build via Web Deploy (MSDeploy)

When I first started deploying code from TFS I took the simple approach and created a batch file and deployed the websites via RoboCopy. I’m a very “Keep it simple” kind of guy, so this worked for us for a long time and so nothing was changed. With my most recent project however, we were deploying code over a slow VPN tunnel from our servers in Chicago to servers located in Europe. Due to this, the RoboCopy was taking over 4.5 hours to complete. I needed a better/faster way so I started looking into Web Deploy (MSDeploy). I was able to get it working fairly easily and I was pleasantly surprised how easy it was to get it working, and how much time its saved me! I can now deploy the code in less than 20 minutes!I’ve outlined the process in detail below, but in general you only need to do this:Add MSBuild parameters to your automated buildCustomize the deployment parameters for the websiteCreate a batch file to an auto-generated MSDeploy scriptExecute the batch file from the automated bu…

MSDEPLOYAGENTSERVICE 401 unauthorized–Resolution

We recently migrated a production environment for a client to new Servers. I had previously been using MSDeploy to deploy the websites/services to the servers so I figured all I had to do was install MSDeploy, point Update my deploy scripts to point to the new servers, and deploy! I was using MSDeploy 2 on the previous servers so I figured it would work on the new ones. Unfortunately it didn’t turn out to be that easy.
When I ran the updated scripts I got the following error:
Fatal: Request to remote agent URL 'http://myserver/MSDEPLOYAGENTSERVICE' failed.
Fatal: The remote server returned an error: (401) Unauthorized. Fatal count: 1
I was using an admin account and I could hit that URL above in a browser so I knew it wasn’t an authorization issue.
Here are the things I tried that DIDN’T work:
Uninstall/Reinstall MSDeploy 2Install MSDeploy 3Create the fake user group on the server per these instructions:…