Герасимов Сергей Владимирович
Analyst's diary or terrible practices to write on gherkin
Scattered description of requirements. The description of one object in the set of requirements leads to contradictions in the requirements and errors.
Long descriptions of business processes lead to errors in understanding and omitting branching conditions.
We will talk about the using of the formal gherkin language, rules, and mistakes.
Requirement management tools, or from simple text to structured data
1) Analysts conduct requirements development at Gherkin
2) Requirements are verified using GIT
3) Visualization of the structure of requirements is provided using a mindmap
Duration of implementation - 1 year
The story includes information about the tools, processes, and practices needed to support the process.
How to improve the quality of software when implementing agile in a large company with a lot of contractors
The process of transition from large slow projects to fast small deliveries in a large enterprise solution with high criticality for the business.
Where the development is carried out by several contractors, and the third company is responsible for the product - it is not easy.
But we did it. We not only introduce changes but also to raise the quality along with the speed of development.