Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Roles and responsibilities on the project

(info) Note: QA Analyst responsibilities can vary on different projects as sometimes we have lower allocation we would need to do everything we would like to. Therefore responsibilities for QA Analyst are divided into 2 sections - mandatory and optional.

Project role

Description

Responsibilities

Project Manager

The project manager is responsible for leading the team, defining and maintaining the project plan and timeline, managing project communications and status reporting, overseeing sprint execution and delivery, ensuring up-to-date project documentation, and selecting individuals to support pre-sales activities and SoW creation.

  • Lead the project team

  • Define and maintain project plan and timeline

  • Manage project communications, status reporting, and escalations

  • Responsible for sprint execution and delivery (kick-off, stand-ups, etc.)

  • Accountable for up-to-date project documentation

  • elected individuals to support pre-sales activities & SoW creation

Solution Architect

Solution Architect oversees defining solution architecture, user story development, guiding solution development, ensuring solution quality, mentoring technical team members, and supporting scope estimations.

  • Define solution architecture

  • Responsible for user story development and management (w/ Customer)

  • Advise and guide solution development

  • Accountable for solution quality

  • Mentor technical team members

  • Support scope estimations

Configuration Engineer

Configuration Engineer is responsible for configuring the solution based on design from the SA.

  • Configure solution according to Solution Architecture and user stories

  • Collaborate with the project team to resolve issues

  • Performs unit testing of the delivered solution

QA

Quality assurance (role is QA Analyst) is responsible for testing, bug reporting, retesting, and preparing testing strategy, with proper communication and documentation in X-Ray.

Mandatory:

  • Reporting and retesting bugs

  • Functional testing based on user stories

  • Regression testing after bug fixes

  • Smoke tests after deployments to a new partition

  • Checking risks connected with testing of the solution (like not enough time for testing, repeating bugs in the same functionality, too complex user stories, …)

  • Prepares testing strategy for the solution

  • Documenting testing in X-Ray (test plan, test execution, test cases, bug reporting)

  • Proper communication on the project

Optional:

  • Helping the customer with UAT testing - tips, guidelines, X-Ray demo, other support

  • Prepare and present functional demo for the customer during Feature Sprints

  • Help with integration testing at early stages of the project in case needed access and resources are available

  • Create test automation scripts in Cypress for later regression testing

Business Analyst

Business Analyst

/wiki/spaces/CUST/pages/2456158437

BA is responsible for analyzing, structuring, designing, and documenting pricing processes and practices, proposing viable pricing solutions, advising on business practices, documenting pricing requirements, and serving as an intermediary between key users, product owners, and the application implementation team

  • Analyze as-is pricing processes and business practices​

  • Analyze and structure to-be pricing strategy and objectives​

  • Design and document to-be pricing processes and practices ​

  • Understand and advise on business practices of similar companies from earlier (Pricefx) pricing implementations​

  • Propose viable pricing application solution options & approaches

  • Document pricing requirements into Epics and user stories​

  • Be the intermediary between business key users, product owners and the application implementation team​

Project phases and QA involvement

...