Consultant, Business Analyst, Sr Systems Engineer (QA, Jira, Requirements, Documentation)

10/2024 – 12/2024

Position: Quality Consultant, Requirements Analyst
Quality related consulting and supporting: Process improvement
• Comprehensive evaluation of process documents
• Reporting of all findings along with a final report, conclusions, options
• Proposing a mitigation workflow
• Reviews of the Design Development Plan

Kundenberater

2/2023 – 5/2024

Position: Requirements Engineer, Automotive Quality Consultant (Radar)
[ASPICE
SUP.7 Documentation Management
PIM.3 Process Improvement
RMRE Requirements Management/Engineering]
JIRA Workflow Consulting
• SUP.7
• Quality related analysis and correction of the documentation of the first large component of the RADAR system, initially Word based.
• Creation of an internal documentation rule set along with instructions.
• Investigating into and supporting the process of evaluating and selecting a CCMS system, the final solution then was based on Confluence plus plug-ins. For that purpose, I created a large, comprehensive table in Confluence during a timeframe of three months while adding information like results of investigations, specs of Confluence plug-ins and diverse related tools on the market, along with specs of CCMS systems off the shelf, plus proposals of adapting existing internal mix of scripting solutions managed by DevOps.
• Development of a pilot plan (Excel) to identify the performance of the CCMS system based on Confluence plus plug-ins.
• JIRA
• Creation of Jira tickets and workflows to cover the creation and review processes of documentation modules, and paragraphs, in different stages, and for the different levels of the documentation, e.g. document level, chapter level, creation, review, re-review, instant fix, etc.
• Due to the project organization, the Jira workflows to control the development of the documentation modules needed to get adapted, here the demands turned out to be different from the usual Software related workflows.
• PIM.3 + JIRA
• Jira process analysis and improvement, proposing specific workflow redesigns (Findings: The existing Jira workflows of specific sections were incomplete).
• RMRE + JAMA
• As general support for the REQ team, I analyzed existing requirements specifications in Jama after quality criteria; these requirements were under constant development and expansion by the REQ team, already more than one year at the time when I joined the project. I evaluated the requirements along with hierarchies for gaps and inconsistencies.
• All quality related findings of requirements I reported to the REQ team.
• Occasionally, I carried out a Gap analysis (via tree mapping) of common attributes of requirements specifications of the RADAR system in Jama for one or more of the different RADAR main components (main deliverables).
• Analyzing and testing Jama behavior of e.g. text paragraphs when used for storing documentation and compiled a list of issues along with mitigation proposals.
• For the US design team, I created two stakeholder requirements specifications in Jama from scratch after finalizing first with the flexible method of tree mapping. These specs were intended for the power supply component of the RADAR system.
• I created these two new Jama requirements specifications after two specification documents provided by a) the US design team (Word file), and b) by the customer (PDF file).
• To stick to a standard, I organized these requirements as usually done in the Automotive supply business. Then I documented the content, the structures and the specifics in use in a comprehensive way since the US design team did not have any knowledge about Jama in specific, or RM systems and requirements organization in general.
• Note: The REQ team took a completely different, non-Automotive approach when organizing all the requirements specifications in Jama for the whole RADAR system, in Fall 2023 the internal demand came up to change this organization of the requirements in a way to reflect a) the design of the RADAR system, b) the functionality, or functional structures.
• Additionally, I prepared these new requirements specifications in Jama according to the internal (non-Automotive) way done by the REQ team, so that these two specifications could easily be adapted at any time later on, a matter of choice.
• GENERIC
• Planning and coordinating hands-on activities for the DevOps team due to the demand to store and process specific data at cloud-based locations.
• Preparing workflows for the DevOps of required pre-processing on local systems before uploading, among other tasks, e.g. planning for automating processes.
• Communicating, coordinating numerous topics to align team leads and teams better, to outbalance the lack of communication and synchronization, while supporting diverse objectives, roles, with numerous activities.
Tools: JIRA, Confluence, ASPICE, JAMA, MS Office, MindManager, Xmind

Jira, Requirements Management

3/2022 – 12/2022

Position: PRM Problem Resolution Manager (HUD)
Cyber Security - Lead of the CS Task force
[ASPICE
PIM.3 Process Improvement
SUP.9 Defect Management]
JIRA Workflow Consulting
• PRM
• My main role was Defect Manager at this project, constantly tracking, and reporting defect, non-defect, and quality tickets, internal and customer tickets.
• To track ALL progress, and tickets of all the areas and branches of the project, the Jira tool Big Picture was in use.
• I constantly created and rewrote the required PRM process documentation according to ASPICE level 2 until the final version before SOP.
• Also, I created trend reports of all ticket types, however, on a regular basis.
• I also created the CM (Change Manager) and the PRM role descriptions, to pass the relevant APICE level 2 approvals alongside my TPM. In this context, we collaborated very closely for fulfilling the ASPICE level 2 demands, while solving and managing process, development, and quality tickets.
• Besides these daily duties, I investigated, tracked, and communicated numerous topics among team leads, teams, departments, and the relevant team in Japan.
• Further, I supported diverse objectives and activities of the TPM, also performed as a substitute of the TPM role, for conducting team meetings, serving requests of the customer, among other tasks.
• I worked on work packages of ASPICE level 2 related demands of the SQA department. In this regard, I created, and extended QA related content according to ASPICE level 2.
• JIRA
• Since I recognized some specific effects in the Jira dashboard meetings with the SQM team and the development, testing departments, I evaluated the existing Jira structures, workflows, and processes, thus, analyzed them.
• Since it turned out, that the most essential Jira workflows were incomplete, the effect on the tracking process was obvious and the reason for the loss of resources, resulting in higher costs, effort, and delays.
• As a result of my pointing out report, the Line Manager initiated a complete redesign of all the essential Jira workflows of the development and testing processes. As a member of the Project Management board, and due to my Jira PRM knowledge from the former Bosch project, I participated in this activity.
• Requirements documentation
• During the evaluation of specific, internal documents, I commented and annotated my findings in the relevant documents of requirements management.
• CS Cybersecurity
• In collaboration with the Cybersecurity Engineering team, I carried out several evaluations of the provided Cybersecurity requirements as part of the stakeholder requirements set, and subsequently the interpretation and classification regarding intelligibility and effort estimation. The Cybersecurity Manager then performed the final check along with some additional verdicts and conclusions.
• I was leading the Cybersecurity Task Force serving this project, while coordinating CS topics among team leads, departments and the customer, all in alignment with the planning of the Cyber Security Manager who had to serve several projects simultaneously.
Tools: JIRA, Jira Big Picture, Confluence, ASPICE, MS Office, MindManager, Xmind

Informationssicherheit