[New Job Vacancy] job in Mercedes-Benz Research and Development India Private Limited, (Bengaluru, Karnataka) – Jobs in Bengaluru, Karnataka

Are you searching for a Perfect job or looking for new opportunity then ebusinessarticle.com is best choice for you to search your dream Job.

Job Opening details:-
Company Name :-
Mercedes-Benz Research and Development India Private Limited
Position Name :-

Company Location :-
Bengaluru, Karnataka
Job Category :
 General jobs

Full Job Description :-
Aufgaben
Skills
Business analyst/ PO role requires problem solving skills i.e. to start with just a simple problem statement from users, and come out with a clear solution. This is especially true for non-IT users. At present, most of the POs are acting as communication bridge between the technical team and end users, to validate a solution from users, rather than coming up with the solution themselves. There are specific business analyst courses and certifications available in the market (not within MBRDI) that can help in bridging this gap.
PO community. We do not have this as of today. This will help in sharing demand management best practices in terms of process and tools. As an Eg: We learnt about the NPS concept from Elite team in the early days of Product orientation.
Estimation related trainings. POs need to have a good understanding of how estimation techniques work. Currently, this is purely based on technical team’s evaluation and sometimes guess work, with little or no inputs from the POs. There are various estimation techniques available like use case estimation, function point estimation etc. There may be even newer forms of estimation techniques in Agile methodology. We need to go through the techniques available and nominate our POs for these trainings.
Cross project contribution within PICAO on short term assignments to increase domain knowledge. For Eg: A PO from ISTDaWo can come and join requirement meetings for CIS 2 for a period of 3 months, but not necessary for them to actively contribute in CIS 2. Meaning they can just observe the requirements in CIS 2.
Resource pooling – In order to position ourselves as ready to taken on new PICAO topics, we can ask existing POs on a voluntary basis, to be available to take up PO roles for new topics as a stretch assignment. Meanwhile, we can look to hire additional POs from the market. Once we have a replacement (new hire) from the market and the handover is complete, the PO that came from another project can go back to the previous project (it can also be a joint decision between the employee and the manager/LS)
Travels – This is proving to be a challenge due to current Covid situation. PO roles requires strong collaboration with users. Therefore being collocated with the end users definitely has certain advantages.
Technology like data modelling, data analysis using AI and workflow design tools like PNM, Pipefy, Bizagi etc. This is increasingly becoming the market trend where POs/BAs are no longer expected to be playing pure functional roles. They need to have to skill in the area of Data analytics or Big Data and AI. At a minimum level, they need to be able to do data modeling using Database/SQL tools.
Tools – There are a number of BA tools like Balsamiq, Pencil, Mural etc. Our POs need to actively use these tools because PPTs are not effective.
Product management training. There are multiple aspects to product development, like branding, pricing, target focus group, source of revenue, market research, product roadmap etc. While all of these concepts may not be relevant for internal products, it is definitely useful to have the knowledge. The XLRI product trainings can be rolled out selectively to POs by nomination.
UX skills. While we do not expect POs to be experts in UX, they should at least have intermediary knowledge on UX, to come up with wireframes themselves and/or constructively review the wireframes given to them. We can leverage our UX CoE to impart this knowledge through workshops.
German language focus. Despite the support from senior leadership from our German stakeholders to communicate in English, the end users sometimes are not comfortable to communicate in English especially during brainstorming sessions. MBRDI POs need to have a clear plan/timeline to ramp-up on German language
Responsibilities
1. To ensure quality of Software.
2. Contribution in design, coding, integration, analysis and documentation in the assigned project
3. Timely delivery of assigned development tasks/modules.
Qualifikationen
Skills
Business analyst/ PO role requires problem solving skills i.e. to start with just a simple problem statement from users, and come out with a clear solution. This is especially true for non-IT users. At present, most of the POs are acting as communication bridge between the technical team and end users, to validate a solution from users, rather than coming up with the solution themselves. There are specific business analyst courses and certifications available in the market (not within MBRDI) that can help in bridging this gap.
PO community. We do not have this as of today. This will help in sharing demand management best practices in terms of process and tools. As an Eg: We learnt about the NPS concept from Elite team in the early days of Product orientation.
Estimation related trainings. POs need to have a good understanding of how estimation techniques work. Currently, this is purely based on technical team’s evaluation and sometimes guess work, with little or no inputs from the POs. There are various estimation techniques available like use case estimation, function point estimation etc. There may be even newer forms of estimation techniques in Agile methodology. We need to go through the techniques available and nominate our POs for these trainings.
Cross project contribution within PICAO on short term assignments to increase domain knowledge. For Eg: A PO from ISTDaWo can come and join requirement meetings for CIS 2 for a period of 3 months, but not necessary for them to actively contribute in CIS 2. Meaning they can just observe the requirements in CIS 2.
Resource pooling – In order to position ourselves as ready to taken on new PICAO topics, we can ask existing POs on a voluntary basis, to be available to take up PO roles for new topics as a stretch assignment. Meanwhile, we can look to hire additional POs from the market. Once we have a replacement (new hire) from the market and the handover is complete, the PO that came from another project can go back to the previous project (it can also be a joint decision between the employee and the manager/LS)
Travels – This is proving to be a challenge due to current Covid situation. PO roles requires strong collaboration with users. Therefore being collocated with the end users definitely has certain advantages.
Technology like data modelling, data analysis using AI and workflow design tools like PNM, Pipefy, Bizagi etc. This is increasingly becoming the market trend where POs/BAs are no longer expected to be playing pure functional roles. They need to have to skill in the area of Data analytics or Big Data and AI. At a minimum level, they need to be able to do data modeling using Database/SQL tools.
Tools – There are a number of BA tools like Balsamiq, Pencil, Mural etc. Our POs need to actively use these tools because PPTs are not effective.
Product management training. There are multiple aspects to product development, like branding, pricing, target focus group, source of revenue, market research, product roadmap etc. While all of these concepts may not be relevant for internal products, it is definitely useful to have the knowledge. The XLRI product trainings can be rolled out selectively to POs by nomination.
UX skills. While we do not expect POs to be experts in UX, they should at least have intermediary knowledge on UX, to come up with wireframes themselves and/or constructively review the wireframes given to them. We can leverage our UX CoE to impart this knowledge through workshops.
German language focus. Despite the support from senior leadership from our German stakeholders to communicate in English, the end users sometimes are not comfortable to communicate in English especially during brainstorming sessions. MBRDI POs need to have a clear plan/timeline to ramp-up on German language
Responsibilities
1. To ensure quality of Software.
2. Contribution in design, coding, integration, analysis and documentation in the assigned project
3. Timely delivery of assigned development tasks/modules.

Disclaimer : ebusinessarticle.com is only helping our audience to check various job listing in various companies. We have not providing any job nor taking any registration fees. We have no legal responsibility over the details mentioned on our website. candidates are requested to check company profile before joining.

Leave a Comment

Your email address will not be published.