Curently I am working as a Systems Architect for the Dept of Communities on the ICMS project.  This is one of the most interesting and enjoyable jobs that I have had so far in my career.  The environment is friendly and full of great people, the project has well defined goals and a supported vision and the solution is being designed using agile processes using common supportable toolsets that can with a minimum of effort communicate with each other.

 

Originaly when I came onboard I belivied my role to be that of a SharePoint Architect, however since I have started I have expanded more into becoming the Systems Architect for the project looking at all aspects of the solution including the full application set (including SharePoint) the hardware implimentation and the logical design model being used.  We're producing content in 2 week iterations (which is quite fast for software development) and with the government process the MSF Agile process that we are using is presenting quite a few interesting challanges around the design of the system.

 

What I am finding is that as we push to get environments ready for deployment of the iterations is that the requriements for the environemtns themselves are in a constant state of change.  Interaction with other people, external project requirments and even interactions and dependacies on other projects themselves is causing a constant change in the implimentation style of the project it self.

Recently I had an issue on a customers web site where I had to fix an issue with Microsoft Commerce Server.  ummmmmm i've heard of it but never used it!  After a few minutes of looking I came accross this quick Technical Overview.  Also the Only4Guru's site is pretty cool as well with lots of documentation on various topics