Hi All,
I am currently working on my first none-software related project where we are looking to move one of our offices to another location. I have picked up the project mid way through after a contractor had collected some "high level" requirements from business areas. It is now down to me to categorise and filter the requirements prior to sign off. The problem I have is that I feel that these high level requirements don't seems as though they should fit in to the usual general/functional/non-functional buckets due to not actually delivering anything software related.
I have a number of requirements related to communication to employees and vendors about the changes and update of documentation with addresses etc. I also have requirements related to legal matters, moving hardware, removing access for certain staff from old software, migration of paperwork and moving of physical furniture. Should I be going down the typical route of general/functional/non-functional and their related sub categories? It is hard to picture how these should be set out, its almost as if I want to jump straight in to sub categorisation such as security & access, legal, constraints, security and create some further categories for communication etc.
Any advice on how I should tackle this and any experiences of working on non-IT delivery projects?
I think you answered your own question. Why would you force requirements into categories that don't make sense?
What categorize at all? What's the purpose? To organize a large number of items for easier consumption, correct? So use the categories you mentioned such as Security, Legal, Communication, etc.
You might also think of other ways of categorization rather than just type of requirement. Maybe separate them by responsibility (i.e. things to be done in-house, things to be done by 3rd parties)? Or by timeframe of delivery (i.e. things to do week 1, week 2, week 3, etc.)?
brought to you by enabling practitioners & organizations to achieve their goals using: