I can't believe I didn't write about this already. I was sure I had, but as I look back, I didn't. I know I put it on my LinkedIn status. Back in April I was excited to try something unique and innovative for a development project. I wanted to develop the backup capabilities that would allow me to backup to the cloud. In this case, I had performed research to backup to the Amazon cloud, EC2. I had priced it out and was eager to try to get started. The contractors supporting me were eager to try this as well because this has to be the direction of the government.
Unfortunately, I was a little ahead of my time. I was told that I would be required to backup to a different office and use other internal resources. Not exicted about this news, but I rolled with it. Getting services from internal resources is not always a good situation, and this case bears that out. We met and ran through the schedule and agreed that it would be set and ready before August 1. At the time, I asked, "Is there any risk that could get us that would prevent us from meeting the August 1 date?" The response was "No." Here we are on September 16 and it still isn't ready. This is a six week schedule variance.
Then today, what do I read? Apps.gov is now available for use. This is GSA's cloud, competing with Amazon and Google but geard for the federal sector. It is about 4 months too late for my project, but for backup of data and contingency operations, I will try to use it for my next project. I bet that I can get a Service Level Agreement that will help me to avoid six week schedule variances.
No comments:
Post a Comment