Мельников Никита Евгеньевич
Люблю блокчейн и продукт менеджемент.
Features of identifying and documenting requirements in blockchain projects
Software development is unthinkable without agile processes. Every year, the trend of applying Agile in the work of system and business analysts also increases. A flexible analyst is no longer an empty phrase.
However, in 2017 there was another big trend - blockchain and crypto-currencies. Projects in this industry are becoming more and more. The requirements for them must be identified and formalised too. Are there any special aspects here? Certainly. We will talk about it in this speech.
More than analysis. How do we speed up a development process taking some developer's responsiblities
An analyst works with requirements. Requirements should be gathered. Then an analyst should analyze, systematize and formalize them. Has the role of an analyst ended at this point? Should the role of an analyst is only restricted by working with requirements? We, at Systematic Consulting, answer "no" to both of these questions. I will tell you why we think so.
My lecture will be devoted to special aspects of analyst's responsibilities in our company. I will talk about "invasion" into development process and what advantages and disadvantages our project team and client have behind this. I will talk about features of working with DB, namely, I will concern database metamodel of our framework. It is worth mentioning that working with this framework simplifies things for analysts and developers. This lecture should be interested for wide audience and especially for those who
develop software using relational databases.