Fantastic Analysts and Where to Find Them? Yuriy Shvayka, Luxoft, CEE-SECR 2017

I will present my experience for analyst recruitment. The presentation will describe different types of analysts and will answer the questions – what is the difference between them, how to understand what analyst is required on the project and how to find the suitable one. Main focus of the presentation is on the project demand and tasks, not on the standards.

The presentation could be useful to the Lead Analyst, Project Managers and Team Leads, that look for analysts for their team/projects.

Transcript

1. www.luxoft.com Fantastic Analysts and Where to Find Them? Yuriy Shvayka Software Engineering Conference Russia October 2017, St. Petersburg
2. www.luxoft.com Yuriy Shvayka, Luxoft  Lead Functional Analyst  13y+ IT industry experience  Passionate about Investment Banking and Knowledge Sharing
3. www.luxoft.com Same projects – different persons Projects highlights Analyst highlights Status • Multiple stakeholders • Poor high-level requirements documentation • Scope changes • Senior DEV team • Formal approach. • Requirements analysis and documentation on great level. • Good relationship with the team. • Not able to pull out new requirements. • Spends lots of time with stakeholders. • Pull out and document high level requirements himself. 3
4. www.luxoft.com Same projects – different persons Projects highlights Analyst highlights Status • Single stakeholder that interact with the team as PO • True Agile approach • Distributed SCRUM teams • Analyst acts as a SCRUM master. • Decompose the requirements from PO and provide detailed user stories. • Not trying to get involved in high- level requirements • Analyst trying to get Proxy PO role. • Working with stakeholders to get more involvement. • Pass the requirements without further decomposition. 4
5. www.luxoft.com
6. www.luxoft.com
7. www.luxoft.com Driver  Works on his own.  Can get requirements even from stakeholders that don't want to share them.  Love to act as a team representative  Perfect if you need to push stakeholders
8. www.luxoft.com Implementer  Focus on requirements documentation with very good level of details  Details are their precious  Ideal for vigorous Product Owner
9. www.luxoft.com So, who do we need, then? 9 Project/team questions Driver Implementer Single PO/stakeholder available x Multiple stakeholders with contradict requirements x Solid development team with skillful TL who can represent the team x Team needs the representative (talking head) in front of stakeholders x PM/TL has deep knowledge of the domain x Lack of domain knowledge, investigation is required x Number of systems in question is small x Big number of systems in question (integration question solving required) x
10. www.luxoft.com Ok, but how can I identify them? 10 Skill Driver Implementer Theory of requirements: types, qualities x x Requirements documentation x Requirements Gathering x Requirements Management x Contradictory requirements x Change management x UML/BPMN/IDEF/Other x Integration with other systems (4-5) x Team interaction x Stakeholder communication x English/Native Language x x
11. www.luxoft.com
12. www.luxoft.com Thank you for your time! Questions?  Please send feedback/complains: - yshvayka@luxoft.com - y.shvayka@gmail.com - http://www.linkedin.com/in/yuriy-shvayka  Skill matrix could be found at - https://drive.google.com/file/d/0BwytEKaxQmW3ZjRKTUFvcVZYYms/view?us p=sharing 12
13. www.luxoft.com Thank you! Copyright © 2017 by Yuriy Shvayka. All rights reserved. All content (texts, trademarks, screenshots, illustrations, photos, graphics, files, designs, arrangements etc.) on this presentation are registered and unregistered intellectual property of their respective owners and protected by copyright and other protective laws. It is prohibited to copy, distribute or any other use of the content without prior consent of their respective owners. Luxoft is not associated with or sponsored by copyright owners.