Ervaren IT Consultant / requirements engineer

General
Looking for someone with deep insight into IT-solutions and the Siebel platform, with actual development experience in the Siebel platform, but who has moved towards requirements engineering / IT Consultancy and also has solid experience in those areas. Someone who can manage an ‘ocean of detail’ content-wise to the letter and at the same time can handle project management tasks, like creating status reports, aligning release planning, driving sub-projects, participate in business case reviews.
Subject will operate in a key project for Daimler, hereafter referred to as ‘project Y’.
Timeline Requirements
Subject must start in Week 1 2018 (Latest in Week 2 2018) and be on site for 90 chronological working days, until May 12th. Holidays or other timeline related availability constraints MUST be agreed upfront.
Tasks
Maintain a project independent, fully detailed well documented overview of the entire Project Y functionality as implemented in the Compass System during the various phases of the project.
Create System Requirements Specification (SRS) documents for the Project Y and align it with all stakeholders resulting in fully signed specifications latest the day before development starts. SRS should form a statement of work, against which the quality and quantity of deliverables can be checked.
Coordinate creation of test-scenario’s and validate them.
Evaluate reported bugs against the SRS, classify them, assign to development, retest when development reports they are fixed and closed them when indeed fixed.
Be the first to test newly developed functionality.
Assist in and coordinate troubleshooting issues found in test and production environments.
Answer and advice in response to questions about specs and functionality.
Align project Y activities with Compass release-planning.
Pro-actively identify and address potential issues with specifications, testing, deployment or release-planning.
Act as IT-Sub-Project manager for Project Y, provide status reports, drive sub-tasks that involve coordinating people from various IT sub departments forward.

Skills & Experience
Getting things done. Fluent in Requirements Engineering. Technical deep understanding, together with functional end-user focus and not afraid of project management related tasks. Anticipate potential issues and mitigate them. Highly pro-active attitude, excellent theoretical skills, but also pragmatic; see compromise coming while it still can be avoided and try to avoid it while still possible. Only willing to make compromises if all else fails.
Technical background and understanding of REST interfaces is a must (writing specifications for them, as well as making sure that both sides of the interfaces are 100% aligned and all involved parties, like firewall people and network people are also fully up to date), as well as technical background and understanding of user-interfaces. These are often seen as two different disciplines – we are looking for someone who can handle both easily. So someone with only business analyst/requirements engineering like skills who often states things like “I’m not that technical” should not be forwarded as a potential resource.
Excellent communication skills, able to effectively cooperate with people with varying degrees of know-how about a subject, both on the development as on the business side.
Ability to describe in words how IT solutions actually work, without being vague, without hiding behind terms or abbreviations or reverting to authority. Ability to understand business drivers, business processes and how the IT solutions help to achieve them. Ability to thus communicate effectively with both IT Development and Business, bridging the gap.
Good understanding of SQL, Oracle databases, XSLT, SOAP.
Siebel Development experience, ideally in diverse areas.
Siebel Requirements Engineering experience, ideally in diverse areas. Especially in this area the expectation is meticulous, non-ambiguous functional specifications that please IT Development, making their work crystal clear without leaving tough decisions undecided or IT Development not being aware of design decisions. Alignment is key. System Requirements Specification reviews should not result in surprises. For Project Y the content is about three things that are all connected:

• A Contact Center solution (which is integrated with an existing solution, not much changes needed here)

• A solution for an external Contact Center, based on an openUI application

• Interfacing with a large Mercedes back-end API. Also in this area expectations are high. Experience with projects that involve interfaces is required: Defining the interfaces functionally, such that development knows what to build, testers know what to test and troubleshooters know where to look. Dealing with exception scenarios caused by the interfaces, like time-outs. Bridging the gap between what happens in the interface and what happens in the user interface by being able to imagine how it will work out and formulate solutions for potential problems with this. All meticulously documented in the System Specifications Document.

Siebel is not rocket-science, deep understanding the Siebel framework from physical schema to UI objects should be somewhat trivial.
Experience with projects that involve many interfaces that all cooperate in achieving the desired functionality.
Affinity with requirements engineering, Use Case methodology (Jacobsen, Rational), write user stories instead of lists of requirements. Understanding of object oriented principles and methods (e.g. explain encapsulation and inheritance and how they apply to functional modelling).
English (German big Pre).
Master’s degree in IT