Business Analyst or Business Systems Analyst or Systems AnalystBookmark This
Westwind Solutions LLC
Description4 Business Analysts/Systems Analysts for Platform Services. 2 for each.
General description for both is below.
1)The client is seeking two individuals with the following skill sets.
Overview of need:We need four Business Analysts/Systems Analysts or contractors, both Right to Hire, to work for Global Research. Having at least 1 individual on board within 2/3 weeks would be great. 2 would be fantastic.
- Will work on Platform Services. Platform Services provide the interface between multiple end user applications/websites an online Library, their most profitable product, a platform in which researchers access our renowned scientific, technical, medical and scholarly research journal content) and back end systems.
2)The client is also seeking two individuals with these following skill sets:
They are largely identical MINUS the Systems Analysis/RiSK stuff that is specific to Platform Services. So, you could say the other two positions are more generalists. In all four cases, They really want strong requirements leaders. They need to be able to be seasoned practitioners of the methodologies (OOAD, RUP, etc.) but also have to be good critical thinkers and leaders with ver strong verbal and written communication skills, etc. Influence without authority, emotional intelligence, all of that stuff.
Note from client:Individuals need to substantiate what is on their resume. If they say they know the Rational toolset, they need to be able to describe how they used it and why? If they say they have experience with OOAD they need to be able to explain what it is and why/how it is used.
Creating a set of reusable services means that application development teams do not need to keep building bespoke solutions for similar project requirements.
Foundational/technology principles driving Platform Services:
- Representational State Transfer (Very helpful is candidates have defined "ReST Services in prior work experience).
- All objects will have a Unique ID
- Use standard HTTP Method.
- Objects can be viewed in multiple ways
- Communication performed without Sessions
PRINCIPAL ESSENTIAL ACCOUNTABILITIES:
Major Activities Expected End Results
(what the position is responsible for) (why it is done).
Define enterprise-wide, standard ways of identifying and elaborating upon and managing software requirements. Consistent, correct, concise, testable, unambiguous and re-useable requirements across software delivery projects.
Work with project managers and other SQA colleagues to estimate the effort associated with the Requirements Management component of software delivery projects. Consistently reliable estimates for the Requirements Management component of software delivery projects.
Work with PMs, Client, and other project stakeholders (Users, Architect, Dev Lead, etc.) to prioritize and sequence requirements in order to ensure appropriate risk management for individual projects Appropriately prioritized/sequenced requirements such that risk is effectively managed and minimized.
Review requirements artifacts produced by individual business analysts for correctness, completeness, conciseness and ambiguity. Consistent, correct, concise, testable, unambiguous and re-useable requirements across software delivery projects.
Ensure adherence to process and tools usage models for Requirements Management on individual projects as defined by SQA Process and Tools team. Consistent, correct and practical application of Requirements Management process and tools usage models on individual projects.
Work with PMs and SQA Process and Tools team to ensure appropriate usage model are selected for specific software delivery projects. Project-appropriate usage model (ceremony/formality) selected for all projects.
Ensure traceability is established and consistently managed amongst different requirements/requirements types on individual software delivery projects. Common and clear understanding of origin of all requirements and their individual relationships to other project artifacts, e.g., test cases such that project stakeholders can a) easily assess impact of any change in requirements b) ensure adequate test coverage c) ensure completeness of resulting solution d) avoid "gold-plating .
Participate in life-cycle "toll gates to ensure quality and completeness of project requirements artifacts. Consistently successful execution of the Requirements Management discipline across software delivery projects.
Other critical qualifications:
--Excellent client-facing and tech lead facing written and verbal communication skills.
--Able to exhibit influence without authority diplomatically in a high pressure software delivery environment.
--Work closely with remote UK based teams and often engage in off-hours meeting to account for time zone differences.
--Development experience a major plus.
--BA or SA ReST services experience a MAJOR, MAJOR plus.
**NO Third Parties.