How can you establish a good requirements overview for an IT or Web application project? Good question isn’t it?
Over my more than 10 years experience in IT world I have seen plenty of good and bad project specifications, KPIs and requirements. Similarly I have been honoured to participate in quite a large number of initial project meetings, where you actually obtain that information.
How can you avoid confusion, how can you make both meetings and paperwork effective and comprehensive for all parties involved?