Rozhdestvenskii Stanislav Igorevich
Business Analyst - DataArt
Talks (4)
  • 16.11.2020
    Sins of User Stories

    Everyone writes User Stories (well, almost everyone). This is easy and fun. But most BAs don't do this right. Beyond the seeming simplicity, there are traps that are not easy to avoid. In this talk, I'd like to tell you about the most common User Story mistakes (with real examples) and check if we could fix them to get the maximum benefit out of the User Story format.

    • Average
    • 20 min
    • Analyst Days / 12
  • 28.02.2019
    Choosing requirements quality

    Requirements quality is the key aspect of BA's work. The quality criteria are well-known. But is it possible to have ideal requirements? In this talk, I'd like to discuss the requirements quality definition, its constraints, as well as some practical recomendations for writing good quality requirements and process improvements related to the quality.

    • Average
    • 40 min
    • Analyst Days / 10
  • 31.01.2018
    Building Business Analyst qualification assessment system

    Assessment of Business Analyst qualification level is a challenging task due to many reasons. First of all, expectations from a BA may vary in different industries, companies, projects and project phases. Also, any assessment run by a human is subjective: different experts may provide different results for the same person. And this can lead to misunderstanding and conflicts. Lastly, the assessment approach should be flexible enough to improve over time and meet changing demands.

    In our talk, we'd like to share our successful experience of building Business Analyst assessment procedure at DataArt.

    • Hard
    • 40 min
    • Analyst Days / 8
  • 29.02.2016
    Approaches to changes’ specification

    Changes do happen on every IT project and are frequently the most challenging part of it. Key goal of each BA is to capture each change and make sure the actual application does not go too far from what's documented. In this presentation I will tell about two high-level approaches to specifying changes in requirements, their strengths, weaknesses and a way to combine them.

    • Average
    • 40 min
    • Analyst Days / 5
To leave a feedback you need to

Chat with us, we are online!