4 ms·
> Requirements will always change, full stop But that doesn't mean you have to stop what you're doing and go chase those requirements. Why did the requirement
by nerdponx 3y ago
> Requirements will always change, full stop
But that doesn't mean you have to stop what you're doing and go chase those requirements.
Why did the requirements change? Is it mandatory that the change happen right now? What research was done to support the requirements change? Was the original requirement bad in the first place? Was insufficient alignment and understanding achieved at the start of the project? Do you actually talk to the stakeholders at all, or does your PM just forward you their emails and expect you to do whatever is in there?
There's a lot of room between "design everything up-front and never change anything" and "allow requirements to change arbitrarily".
- mrkeen 3y ago> There's a lot of room between "design everything up-front and never change anything" and "allow requirements to change arbitrarily". The arbiter of the changing requirements is the one paying for the work.
- nerdponx 3y agoSort of. I've only done a small amount of consulting, but when I did, change requests from the business side of things were the start of a conversation, not direct unchangeable instructions. I would never knowingly choose work in an environment where the latter was the norm.