Project Evaluation: Validation phase 2

During the development phase of the ‘Validation’ project (see my earlier evaluation). We got approached by another project group (well the project manager) and they wanted us to adopt some changes related to their project. We were in the midst of our testing phase, so our project manager turned them down.

So it was decided they should issue a change request so we could follow-up, when we were done.

In order to help them out delivering the requirements for us to complete the task, I wrote a mail with our team project manager, apparently our technical lead had done the same (without Cc’ing us however). Anyway – none of the requirements where met.

So when I had my window of opportunity I started hunting down the requirements and started looking into what changes to make to the existing application.

  • Lacking communication of key parameters (test environment names etc)
  • Lacking test data
  • Loss of momentum
  • Bad specification (even for a simple CR)

The most important requirements where names and parameters on test environments and of course test data. This took some time to get. I was able to implement the changes quite fast based on information from the change request, even though is was immensely sparse.

And all this hunting after key parameters cost a lot of time and momentum.

Now I am just awaiting the result of the final test before I can close the project, I have waited two weeks…

Leave a comment

0 Comments.

Leave a Reply


[ Ctrl + Enter ]