Business Analyst
So the ‘Product’ has been accepted and you wish to action the next great project with a high speed to market?
Woah there!…excellent news but there are a few things I would suggest or help complete for you here.
Stakeholder analysis
Establish ‘who’ the key business stakeholders are and ‘what perspectives’ you need to bring into the requirements.
Business Analysis Plan
The plan you have when you don’t have a plan – the ‘Clayton’s Plan’ perhaps? - someone will get this.
This should outline requirements, qualify the effort, the responsibility all within context of the Business Analysis effort.
For more shorter bursts or sprint based projects you can do without this but not recommended if you are to hand over the project to another party, vendor or team.
Scope Statement
Aah here we are – the meat of it. A clear definition of the scope or product.
AKA The Business Case or Vision Document.
We need to make sure we answer:
- Business need or problem to solve
- Is the investment worth it?
Business Requirements Document
One level down which may include Functional Requirements and should be included especially if using a vendor.
Wireframes and User Journeys to support the product and customer journeys. As a BA with strong production skills I am sure to understand and be able to make high fidelity prototypes.
Where I can be even more helpful is in my understanding of the technology to deliver on the product vision as I like to stay close to the technical solution itself not merely enforce a schedule.
Then it’s about planning a process of iteration. Deploy-learn-repeat.
A Digital Producer or Product Experience Manager can help takeover from here.