Update :
All of the comments are in from the F-Spec
Unsurprisingly, the majority of them are "change requests" as they did not attend the workshops and hence have no clue what is written in the F-Spec
The PM engaged this morning, with very supportive comments - if it's not been defined before and is in their comments then it's a change request
So this afternoon we went through all the comments; they're mostly change requests
The PM says "We can't be banging these all back as change requests"
Suity : "Why not?"
PM : "Cos it won't look good"
Suity "What do you suggest?"
PM "We need to find a way to manage these changes?"
Suity "Well seeing as there is a requirements freeze in force, the only way I see to manage these is via change requests"
<queue long hours discussing the same old tulip
I feel sorry for the PM as he was seriously undermined today - This is a 20 week project, 4 weeks allocated to design and 16 weeks to build and test, and yet when we arrived there were no requirements to work with
So mucked in and did the requirements gathering
And no one had time to attend the workshops
So now the requirements are incomplete and they are bleating about it during the review stage
Our ONE saving grace was that the dev environment, due to be delivered by ClientCo is now a month late so the off shore team cannot start developing
That was until today when we learned the PM from ClientCo had called the consultancy and agreed that even though the dev environment was a month late there would be no slippage
All of the comments are in from the F-Spec
Unsurprisingly, the majority of them are "change requests" as they did not attend the workshops and hence have no clue what is written in the F-Spec
The PM engaged this morning, with very supportive comments - if it's not been defined before and is in their comments then it's a change request

So this afternoon we went through all the comments; they're mostly change requests
The PM says "We can't be banging these all back as change requests"
Suity : "Why not?"
PM : "Cos it won't look good"
Suity "What do you suggest?"
PM "We need to find a way to manage these changes?"
Suity "Well seeing as there is a requirements freeze in force, the only way I see to manage these is via change requests"
<queue long hours discussing the same old tulip
I feel sorry for the PM as he was seriously undermined today - This is a 20 week project, 4 weeks allocated to design and 16 weeks to build and test, and yet when we arrived there were no requirements to work with
So mucked in and did the requirements gathering
And no one had time to attend the workshops
So now the requirements are incomplete and they are bleating about it during the review stage
Our ONE saving grace was that the dev environment, due to be delivered by ClientCo is now a month late so the off shore team cannot start developing
That was until today when we learned the PM from ClientCo had called the consultancy and agreed that even though the dev environment was a month late there would be no slippage

Comment