Dedicated BA's for documentation
We will shortly be developing a piece of middleware. I estimate I will need three developers for this, which will encompass the front end and backend as well.
Generally, do people recommend hiring a dedicated Business Analyst to write up requirements/ logic/ documentation on this or is this something they leave to their developers, given that one of the core principles of Agile is 'just enough documentation'.
Some may disagree with this but I think it depends on the level of complexity of the software. The beauty of Scrum is that the developers decide HOW to create the software so you have to be careful that is not taken away from the dev team. However, if the software is incredibly complex, it may be worth having a BA document that information. Think about building a bicycle versus building a car. A bike is basic enough that you don't need super specific requirements and logic to build a working bike. A car, however, is much more complex and has hundreds of systems working together. I would want a BA to give me the details and requirements for the car, I wouldn't waste the resources on that for a bike.
Is there a clear product owner for this middleware, and a wish to bring complexity under control by means of incremental delivery?