Day 325 - Sponsor Team Reshape

The team is constantly changing from the beginning of the project and that is not helping the project at all.
This time, the sponsor team has suffered another reshape and one key person will move away from the data migration project.
The person how's being transferred has been reassigned to another task, but this person is one of the few key team members because he knows all the the areas like no one else. The person that is replacing him only knows a small subset of what he knows.
I believe the sponsor team has made a bad move regarding the data migration project.

Day 317 - Team Reshape

Since the project has been rescheduled, it was necessary to reshape our team.
This is necessary because our work load has not changed, it was just the project dead line that has been postponed.
The result of such reshape is still not clear, but the team will be downsized from 4 to 3 people. This does not exclude a temporary downsize to 2 people for up to one month within a couple of months or so. Only time will tell.

Day 314 - Waiting for Resolutions

We have solved most of the issues reported, mostly were wrong mapping specifications, but some implementations bugs were also found.
Almost all issues are set for the functional team to solve and relate with rule specification.
Things are at a stable speed, but a bit slow from my point of view.

Day 307 - Good Migration Results

The prioritization had some real effects.
Some things that were stalled for weeks were finally resolved and this weekend migration was the best we ever had. Nevertheless, there's still some very old issues, 3 months old, that need to be fixed.

GIS has also been cleaned up, which means the loading was performed without any trash on the system, and the test team can now perform the tests without calling us to check if there's a real problem or is it just some dirty data false problem.

Things look promising from now on. Let's see if it keeps this way.