Business Analyst

40000.00 - 45000.00 GBP Annual + GBP40000 - GBP45000/annum
15 Sep 2017
19 Sep 2017
Contract Type
Full Time
Business Analyst/ Product Owner


The primary goal of a Product Owner is to represent the needs and desires of the stakeholder community to a delivery team, being the first source of information about the problem domain for the team. Each delivery team or product line has a single Product Owner to go to for information and prioritisation of their work. A secondary goal for a Product Owner is to represent the work of the team to the stakeholder community. In traditional terms, a Product Owner is in many ways an empowered business analyst.

In essence the Product Owner is the member of the team responsible for defining stories and prioritising the Team or Product Backlog so as to streamline the execution of program priorities, while maintaining the conceptual and technical integrity of the features or components the team is responsible for. As the liaison between the development team and stakeholders, the Product Owner must collaborate closely with both groups to ensure there is a clear understanding of what features are needed in the product or application. Because there may be a variety of types of customers and users, the Product Owner must have a firm understanding of the business domain and the varying needs of different types of users.

Also acting as a Business Analyst the Product Owner is the individual who has the primary responsibility to elicit, analyse, validate, specify, verify, and manage the real needs of the project stakeholders, including customers and end users. The individual serves as the conduit between the customer / stakeholder community and the software development team through which requirements flow and is involved throughout the entire system or software development life cycle. Upon establishment of the requirements baseline, the focus is shifted towards the management of the requirements specification and verifying the fulfilment of all requirements.

The Product Owner is responsible for ensuring that business tasks are performed properly, creating and managing a backlog of product / project activity, prioritising the backlog in line with Project Sponsor, communicating with the development team and reporting on development (sprint) activity and progress. This is achieved by contributing to writing useful product backlog items (e.g. user stories), applying techniques for prioritizing the product backlog, expressing acceptance criteria and working together as a team with testers and developers, predicting the delivery date of a project (or the features that will be complete by a given date) using velocity, managing the key variables influencing project success and managing and reporting to higher management (and what visibility to expect from the team).

Sklls needed:

- Interviewing skills, to talk with individuals and groups about their needs and ask the right questions to surface essential requirements information
- Listening skills, to understand what people say and to detect what they might be hesitant to say
- Analytical skills, to critically evaluate the information gathered from multiple sources, reconcile conflicts, decompose high-level information into details, abstract up from low-level information to a more general understanding, distinguish presented user requests from the underlying true needs, and distinguish solution ideas from requirements
- Facilitation skills, to lead requirements elicitation workshops
- Observational skills, to validate data obtained via other techniques and expose new areas for elicitation
- Writing skills, to communicate information effectively to customers, marketing, managers, and technical staff
- Organisational skills, to work with the vast array of information gathered during elicitation and analysis and to cope with rapidly changing information
- Interpersonal skills, to help negotiate priorities and to resolve conflicts among project stakeholders (such as customers, product management, and engineering)
- Modelling skills, to represent requirements information in graphical forms that augment textual representations in natural language, including using modelling languages already established in the development organisation
- Knowledge needed
- An understanding of requirements elicitation, analysis, specification, verification, and management practices and the ability to apply them in practice
- An understanding of how to practice requirements engineering according to software development life cycles in a team environment
- Knowledge of product management concepts and how enterprise software products are positioned and developed
- Knowledge of full software / product development lifecycles
- Knowledge of Waterfall and Agile development frameworks
- Application domain knowledge is a plus, to have credibility with user representatives and be able to work effectively with them


- Work with the project manager or project sponsor to document the product's vision and the project's scope
- Collaborate with internal stakeholders and teams to translate business requirements into user stories for the development teams to implement
- Establish and implement effective requirements practices and elicit requirements using interviews, document analysis, requirements workshops, storyboards, surveys, site visits, business process descriptions, use cases, scenarios, event lists, business analysis, competitive product analysis, task and workflow analysis, and/or viewpoints
- Define and prioritise the features of the application including enhancements, defects, and other work items for the team with a view to communicating a product road map and maintaining a manageable product backlog
- Write requirements specifications according to standard templates, using natural language simply, clearly, unambiguously, and concisely
- Decompose high-level business and user requirements into functional requirements and quality, specified in an appropriate level of detail suitable for use by those who must base their work on the requirements
- Define quality attributes, external interfaces, constraints, and other non-functional requirements
- Represent requirements using alternative views, such as analysis models (diagrams), prototypes, or scenarios, where appropriate
- Lead on requirements prioritisation; manipulate and report on requirements stored in a commercial requirements management tool. Define requirement attributes / acceptance criteria and facilitate their use throughout the project
- Develop and maintain an appropriately prioritized backlog of user stories for implementation
- Work with development teams to ensure that they understand the vision for the product and are designing great features for our partners
- Develop appropriately detailed specifications for product features so that they are clearly understood by the development teams
- Inspire and motivate the development teams to deliver innovative and exciting solutions with an appropriate sense of urgency
- Ensure adequate testing and due diligence analysis has taken place before signing off requirements as delivered or fulfilled
- Manage requirements traceability information and track requirements status throughout the project
- Participate in story point sizing and play a pivotal role in project planning and development activities
- Act as an ambassador for the product internally and externally, and as the primary technical contact for queries related to the product
- Work with key stakeholders across the company to ensure successful product releases


- Health cash plan, paid for by the company, to include the employee and their children.
- Salary Exchange benefits portal, access to a massive array of discounts, offers and shopping vouchers.
- Ride to work scheme, a salary exchange scheme with Halfords.
- Childcare vouchers
- Life insurance - x2 salary pay-out

More searches like this