Client centricity as quintessence in everything we do
Integrity and trust
Striving for excellence
Agility as a mindset across the flat organization
Salary Levels – per the prevailing labor laws & competitive market conditions.
Reporting Hierarchy
Administrative Assistant reports to Chief Enterprise Architect.
Educational qualifications
Preferably Undergraduate degree, but not a must.
Skills
Job Description
Solves organizational information problems and requirements by analyzing requirements; designing computer programs; recommending system controls and protocols. Business Systems analysts generally need to have a 2-4 years’ hands on programming experience.
Salary Levels – per the prevailing labor laws & competitive market conditions.
Experience – Minimum of 2 years in I.T. programming (any programming language); preferably about 2-4 years of industry experience, which can overlap with programming experience.
Reporting Hierarchy
Business Systems Analysts reports to and receive general directions from Chief Enterprise Architect.
Educational qualifications
University Degree, 4 years Engineering Degree (10+2+4) with Computer Science and Mathematics is preferable. Candidates with Masters in Computer Science also suitable for this position.
Skills
Job Description / Job Duties
Salary Levels – per the prevailing labor laws & competitive market conditions.
Experience – Minimum of 3 years in I.T. Project Management; preferably about 7-10 years of industry experience, but not a must.
Reporting Hierarchy
Project Manager reports to and receive general directions from Chief Enterprise Architect.
Educational qualifications
Skills
Job Description / Job Duties
As part of Logistics Solution delivery, EDI (Electronic Data Interchange) is a very important building block. EDI Practice Head must understand the Logistics business and how the data is exchanged between trading partners in Client specific business scenarios, analyze the As-Is processes, recommend best practices in the context of Enterprise Architecture. EDI Practice Head must also be leading configuration driven EDI implementations.
Salary Levels – per the prevailing labor laws & competitive market conditions. Ramakrishnan Sankaran is being offered $70,000 per annum at this time.
Experience – Total I.T. experience of 5+ years with a minimum of 3 years in EDI Technologies.
Reporting Hierarchy
EDI Practice Head reports to and works very closely with C.T.O to design the Technical solutions and practices.
Educational qualifications
4 years Engineering Degree (10+2+4) with Computer Science and Mathematics as the primary specializations is a must. Alternatively, candidates with Masters in Computer Science are also eligible.
Technical skills
| Activity | Purpose | Deliverables | Responsible | ||||
|---|---|---|---|---|---|---|---|
| Focus on gaps in As-Is and To-Be | Focus on gaps between what is in the legacy system and what is desired (include every aspect, functional, performance, scalability etc) | To-Be business scenarios and gaps | SwiftAnt Project Manager | ||||
| Keep it Simple | Plan an adequate, but simple solution (in line with Client vision of on premise) to a potentially more general, but complex solution. | High Level To-Be Solution design | SwiftAnt Project Manager | ||||
| UML Models for To-Be | Deliver the documentation in use cases, and UML models |
|
SwiftAnt Project Manager | ||||
| UI / UX Prototypes | Develop a prototype of the new concept and evaluate it with respect to the new, emerging requirements & making sure that current requirements are met. | UX Prototype preferably in Axure (or any preferred tool of Client) | SwiftAnt Project Manager | ||||
| Interface specifications | External / Internal system interfaces by applying Industry best practices to deliver integrations via Integration Platforms (as well as any other middleware preferred by Client) | Interface specifications | SwiftAnt Project Manager | ||||
| Knowledge Transfer & Sign Offs | Conduct workshops with all stakeholders and deliver the documentation and also get the required sign-offs | Final signed documentation | SwiftAnt Project Manager |
| Activity | Purpose | Deliverables | Responsible | |||||
|---|---|---|---|---|---|---|---|---|
| Record Business Rules | Document the information as per Client documentation standards and also by applying UML and PMI best practices. |
|
SwiftAnt Project Manager | |||||
| Record potential Risks (aligned with most valuable requirements first) | Document the potential risks, with probability & impact and Risk Mitigation strategies. | Risk register with potential impact (possibly in Client SharePoint) | SwiftAnt Project Manager | |||||
| Meet and Present | Showcase to the stakeholders the smallest results that can demonstrate real value. | Meeting minutes | SwiftAnt Project Manager | |||||
| Refine the Documentation | SwiftAnt Project Manager | |||||||
| Knowledge Transfer & Sign Offs |
|
SwiftAnt Project Manager |
| Activity | Purpose | Deliverables | Responsible | ||||
|---|---|---|---|---|---|---|---|
| Read the Code & Documentation | Understand the code and available documentation | Input deliverable: as-is code in Client servers and documentation | Client Project Manager | ||||
| Chat with Maintainers | Professionally working with maintainers like “Brothers in arms”, understand the system history and the people-related issues that influenced history. | SwiftAnt Project Manager | |||||
| Involve the (Business / Operations) Users | Understand the business users perspective of the system | SwiftAnt Project Manager | |||||
| Re-read the Code | Based on inputs from Maintainers and Users, re-read the code and focus on most valuable aspects | SwiftAnt Project Manager | |||||
| Step through the execution for most valuable aspects | Gain total command on details for most valuable aspects | SwiftAnt Project Manager | |||||
| UML and Data Model for As-Is | Deliver the documentation in use cases, and UML models |
|
SwiftAnt Project Manager |
| Activity | Purpose | Deliverables | Responsible |
|---|---|---|---|
| Agree on Maxims | Establish the key priorities for the project and identify guiding principles that will help the team to stay on track. | Mini Charter for every functional module | SwiftAnt and Client Project Managers |
| Identify the Personas | Understand who is using the system and why is it important for them and what aspects are most important for them. | User personas (internal and external) | SwiftAnt and Client Project Managers |
| Appoint a Navigator (Business & Technical) | Appoint a specific person whose responsibility in role of navigator is to ensure that the business architectural vision is maintained throughout the project duration (minimal changes are acceptable). | Client Project Manager | |
| Speak to the Roundtable | Hold brief, regular round table meetings. | SwiftAnt Project Manager | |
| Identify the most valuable first | Start working on the aspects which are most valuable to the project first. | SwiftAnt and Client Project Managers | |
| Identify what can be left as-is | Which aspects of the system should be left in their current state (such that time and resources aren’t wasted where not necessary) | SwiftAnt and Client Project Managers |