Hi, Hope you are doing great!
Please go through the below requirement & if you feel comfortable forward your updated resume so that I can get back to you. ===================================================================== Please send me your resumes at *[email protected]*<[email protected]>or call me at *610-621-1705*for further details. *Location* : Green Bay, WI *Duration : *6 month + duration ** ** These Business Analyst positions have 4 distinct objectives: - To be a liaison among stakeholders in order to elicit, analyze, communicate and validate requirements for changes to business processes, policies and information systems. - To understand and analyze business problems and opportunities in the context of the requirements and recommend solutions that enables the organization to achieve its goals. - To ensure documented business, functional and nonfunctional requirements are in line with project goals, objectives and scope. - To be a resource throughout the life of a project clarifying requirements and managing any requirements changes resulting from development, QA or business issues. *Scope* - Capable of gathering requirements for a single large project, 2 medium projects or 2-3 small projects concurrently*.* Sizes are based on BPQ definitions. - Capable of working with up to 7 stakeholders on a given project. May be partnered with another Business Analyst for a single, large initiative. - Capable of defining requirements for any business need regardless of technology and platform. - Able to work on project assignments that are not necessarily well-defined. *Responsibilities * The Business Analyst demonstrates proficiency in the following responsibilities. *Requirements Planning Competency* 1. Documents and obtains consensus of requirements scope, constraints, dependencies, risks and assumptions before gathering requirements. *Requirements Execution * 2. Works independently and takes ownership of all assigned tasks and its completion dates. 3. Takes responsibility for ensuring decisions impacting requirements completeness or quality are made and documented. 4. Engages Systems Analyst or Lead Developer to obtain technical feasibility and possible implementation approaches that impact requirements. 5. Ensures that requirements have appropriate attributes that manages them, such as priority, release, deferred status, etc. These are attributes that assist with the planning of features in a release or amongst multiple releases. 6. Obtains appropriate, documented sign-off from required business and technical stakeholders for all requirements artifacts according to the BPQ process. 7. Traces requirements from business/stakeholder needs to features, its use cases and other requirement types to allow development and QA teams to also trace their artifacts to requirements. 8. Manages incoming client requests after sign-off and ensures that changes to requirements are escalated as change requests to be assessed by the Project Manager and required project reviewers/approvers. 9. Provides impact assessment and estimates for change requests that require requirements changes. 10. Provides timely and appropriate updates to requirements ensuring that staff can identify changes. *Business Process Analysis * 11. Seeks to understand and document the current and future state of business processes explaining the interactions and activities amongst people, data, applications and systems. 12. Interviews SMEs, Stakeholders and users to understand gaps or opportunities in current state in order to prioritize them against other business needs for future state requirements. 13. Captures the business rules that govern constraints on the people, data, applications and systems in these business processes. 14. As needed by the project, captures non-functional requirements of the current state and future state and clearly articulate areas that remain the same or change due to project scope. *Functional and Nonfunctional Business Requirements * 15. Seeks to understand and document within the scope of the project: · Business requirements or needs (stakeholder needs) if they have not been documented in BPQ Phase 3 1 Features of the product or system that meet the stakeholder needs 2 Functional use cases that explain the basic and alternate flows of these features 3 Functional and system errors or exceptions experienced within these use cases 4 Nonfunctional requirements such as (not exhaustive) performance, availability, usability, and governance that support the features or steps in the business process 2. As needed by the project, may collaborate with the development team to document Nonfunctional Requirements at a use case or transaction level to ensure appropriate development and quality post requirements hand-off. *Data Analysis and Specifications * 17. Seeks to understand and document specifications for each data point in input and output files within the processes in scope for a given project. 18. Seeks to understand and document specifications for how data is transformed when processing files within the processes in scope for a given project. 19. Incorporates requirements feedback from data analysis by the Systems Analyst or Lead Developer of any sample input and/or output files. *User Interface Design * 20. For customer or user facing applications, create wireframes or mock-ups representing the documented features and interactions with the user. 21. Create UI specifications document supplementing the wireframes or mock-ups. *Development and QA Team Resource* 22. Provides a walkthrough of the requirements artifacts to the development and QA teams, stressing any complicated and/or risky areas of the requirements scope. 23. Facilitates transfer of knowledge by managing a query log, answering in a timely manner and updating documents as needed with clarifications. 24. Reviews the high level design and architecture solution to ensure that it meets the requirements documented by the BA and that requirements are translated appropriately in project and system deliverables. Provides sign-off to the high level design document attesting to their review. 25. Champions quality through reviews of QA artifacts such as the test strategy and test plans with the QA team. Approves and provides sign-off. 26. Reviews all test cases traced to requirements and provides sign-off. *Communication Skills* 27. Demonstrates flexibility in communicating to business and technical audiences, providing timeliness of information sharing with clear, concise use of language. 28. Develops clear, organized and thorough written documentation and follows department, company standards in communications. 29. Uses meeting and communication skills to keep management, leadership and team abreast of changes in requirements and risks impacting requirements. Uses a variety of communication vehicles while following department, company standards in communications. 30. Provides regular updates to sponsors, stakeholders, customers and project team as agreed upon in the project’s communication plan. * * * * * * * * * * * * * * * * * * * * * * * * * * *Regards, * *Raja* *GENERAL CONSULTING SERVICES,* Office: 610-621-1705 | Fax: 610-482-9315 [email protected] *I sent this email through Google/Yahoo Groups. If you do not want to receive emails in future then please remove your id from that specific group.* -- You received this message because you are subscribed to the Google Groups "SAP Workflow" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sap-workflow?hl=en.
