Similar to the key facts document when you buy insurance, I’ve put one together for Frank Ray and Associates so you know what to expect when hiring us. This can be found here: http://www.frankray.net/key-facts.pdf
One of the key issues I’ve found when working as a Business Analyst is the potentially huge breadth of role combined with (often) a lack of clarity as to what kind of Business Analyst is expected / required by the client.
My personal strength in the Business Analyst role is providing the following kinds of services – assessment of existing architectures, future state development, market analysis, new product proposition, audits and problem diagnosis, refactoring of code bases, unit test coverage. Even requirements gathering and project planning.
However, some clients also require the Business Analyst to act like a Product Owner / Scrum Master, writing and maintaining Jira tickets for a downstream development team. Nothing wrong with that, except it’s just not what I do.
I plan to provide the key facts document to every client / hiring manager / agency before we commence working together.
My approach will be to make it non-legally binding but ensure whatever contract is signed has enough wiggle room to withhold services and/or cancel it if the spirit of the key facts aren’t being met. That means it should remain usable irrespective of the hiring arrangement.
Thank you to Adam Nathaniel Davis for inspiring me to initially draft the key facts document based on your own, ‘remote first stall’
Frank Ray & Associates is a software engineering consultancy that builds high quality software for businesses.