I've gone a little to far maybe, and I put an essential part of requirements, what we call "Needs", in the database.
So, I have all needs mapped with status, customer, contract and user. There I record:
1) What they want
2) Why they want it
3) How am I going to deliver it
I don't regret this, since it is giving me a lot of benefits in a dayly basis. So, my advice is, as much structure you can get, get it
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi!
I've gone a little to far maybe, and I put an essential part of requirements, what we call "Needs", in the database.
So, I have all needs mapped with status, customer, contract and user. There I record:
1) What they want
2) Why they want it
3) How am I going to deliver it
I don't regret this, since it is giving me a lot of benefits in a dayly basis. So, my advice is, as much structure you can get, get it