We had a rush to finish our first delivery for testing. Some guys on the team were staying late until midnight to finish tasks. I was gunning hard to be productive so I did not need to work so late. It was hard. But we finally got our first release ready.
Then the configuration management guy calls a meeting. He said things are confusing. We tried to clear the matters up. Then he uncovered that he does not know where he is going to deploy our changes for testing. There are many other streams of work going on. There is currently no place to deploy our changes. Oops.
The lead on my team pushed this issue up to the project managers. He asked them to sort it out and let us know the outcome. Good job. I imagine there was a task on the project plan to take care of these infrastructure issues. Guess nobody paid attention them until the last minute. Now it is too late. Testing will just have to be delayed.
Luckily this is a huge effort. We only just finished drop 1. There are many more drops to go, and many more months of work left (maybe 6 to 9 months) before we deploy to production. Hopefully we have some lessons learned with this first failure. I am not losing any sleep over it.
Newbie Gets Confused
-
A relatively younger developer got tasked with doing some performance tests
on a lot of new code. First task was to get a lot of data ready for the new
c...