Ерофеева Кристина Сергеевна
Analyst 2.0. How information that analyst owns impacts team motivation
A newbie analyst, as a rule, spends an awful lot of resources to manage basic tasks: gathering necessary information, documenting it consistently, supplying the team with the decent amount of work for upcoming iteration and managing stakeholders relationship.
As the expertise grows, the analyst starts doing all the necessary things automatically and it leaves time and resources for processes improvement, sometimes beyond own role.
The information, which the analyst owns in his role is essential not only for analysis but for requirements building too. Some parts like context, functional architecture or specific low-level details play a dramatic role in developing team motivation and help improving work efficiency and be proud of the results.
In the talk, the speaker sums up own experience in part increasing team awareness beyond knowledge necessary for everyday work needs.
The bees and the birds. How not to complicate things
Its widely discussed in related books how an analyst shall collect and document requirements, as well as efficiency of communication process in a project.
However, when requirements are collected and written down, sometimes the resulting document is not suitable as is to be passed over to dev team to reach both goals - happy business users and code quality.
So one of main goals on performing functional analysis in this case is to transform unstructured business users input to an algorithm and related straightforward description.
In the talk I plan to tell what exact steps this transformation shall go through using as example of such a complicated system.
Leave the past behind. How to make your documentation live for ages
Just imagine - you happen to be working on really old project. 10 years at the very least. That's where a perfectly documented system would make really a favour.
Each one of us can find himself in situation like that, even on the project that you are currently working one in 10-15 years.
Information flows trough an analist in charge of the project. Some part of it are vital for developement.
The other parts gather value as the years pass by. But the moment you need this info it can be next to impossible to turn back time and go 15 years back from now.
In the talk I sum up my experience in dealing with documentation to figure out what exact information parts is the ones that make documents valuable and efficient in future.