anna-shvedova

Разработка

Управление требованиями

Куратор секции: Анна Шведова

Привет всем! Я - Анна Шведова, руководитель направления аналитики в компании SimbirSoft. Мы - единственная компания в регионе, где деятельность по сбору, анализу и управлению требованиями к разрабатываемому ПО выделена в самостоятельное направление и ведется согласно международным стандартам REQB / IREB.

Я приглашаю вас принять участие в обмене опытом и знаниями по системному и бизнес анализу; обсудить, что же делать, если требования все время меняются, хорошо это или плохо; и за кем же последнее слово: за аналитиком, QA специалистом или руководителем проекта.

Темы докладов будут интересны всем, кто так или иначе сталкивается в своей работе с постановкой задач на разработку, а именно - сбором, описанием и моделированием "хотелок" Заказчика. Также затронем вопросы управления отдельными требованиями и проектом в целом. Приходите, будет полезно! Встретимся на «Стачке».

Мои контакты для любых вопросов:
E-mail: anna.shvedova@simbirsoft.com
Facebook: https://www.facebook.com/anka.zykova


Maxim Nikitin
Big Boss @ ITSalt.ru
Moscow

Who the analysts are, what they are doing and why they are needed in the process of developing IT systems. I will tell you:

- the difference between business analysis and system analysis,

- the difference between use-cases of the system and business functions;

- how to link business functions, usage scenarios, interface structures, and data classes into a single model;

- how to use the obtained model of requirements to develop test scenarios;

- how to link the steps of the test script with the requirements to understand what needs to be re-tested when the requirements change.

Based on examples from real projects.


Dmitriy Bezugliy
Coprocessor @ System Approach LLC
Moscow

Things get more complex and unique ...

The amount of knowledge required to achieve the desired result cannot fit into an individual mind, so a team is needed ...

No trace of silver bullets is left, only legends ...

No one sharpens a saw now just to make it sharp—it needs to be done for something—something that might not exist yet ...

Whether you are a manager or an employee, you are always concerned about how to be successful.

This report will offer you the key:

- guidelines for successful activity and growing culture;

- tools for self-organizing and developing processes;

- ways to speed up development of competence.

These are generic guidelines, but there will cases from business- and system-analysis.


Irina Mironova
Director for Analytics and Design @ Pro100
Ulyanovsk

Problems of development and implementation of CRM-system. Preparation for implementation, analysis of workplaces and users. The most frequent implementation problems on the ground level and how to avoid them.


Natalia Gracheva
Analyst @ SimbirSoft
Ulyanovsk
  • Levels of requirements in Agile
  • Who takes part in development of requirements in Agile?
  • What does development of requirements in Agile include?
  • Managing requirements in Agile

Ilya Zhemanov
Junior consultant SAP MM @ SD @ IBS Ulyanovsk
Ulyanovsk

1. Absence of primary information about SAP at job placement. Fears.

2. About myself and the start of work of the 24-hour SAP Support Center

2.1. Functions performed

2.2. How to build smooth operation with round-the-clock support

2.3. Possible difficulties in organizing round-the-clock support and how to overcome them.

2.4. Roles in SAP

3. How do I see SAP?

4. Where to move. Extensive career opportunities in SAP.

5. My view on working in SAP today.

6. Entry points in SAP.

6.1. Periods of implementation at the enterprises

6.2. University courses

6.3. Internship programs in IT companies


Hans (Petrus Johannes) Loenhoud
Consultant @ IREB e.V.

Recently, the Requirements Engineering Qualifiactions Board (REQB) and the International Requirements Engineering Board ((IREB) have joined forces. They continue together under the name of IREB.

IREB offers a broad training and certification scheme, starting with a common Foundation Level, containing several specialized modules at the Advanced Level and (coming soon) capped with an Expert Level.

This scheme comprises all steps of the fundamental Requirements Engineering process: elicitation & consolidation, documentation & modelling, validation & negotiation, and requirements management.

IREB develops a new module to service the needs of modern development, called RE@Agile. It builds a bridge between the Requirements Engineering world and the Agile community.

In this development, IREB sees a shift in the focus of requirements engineering from descriptive to creative, from elicitation to solutions. We summarize it in a 4 sentence RE Manifesto and map these sentences on the Kano model. This is valid for both Agile and traditional project, hence RE@Anywhere.


Гузель Рахимова
Руководитель направления @ Центр Высоких Технологий
Ижевск

На примере нескольких неудачных проектов мне хотелось бы рассказать о такой важной роли на проекте как владелец продукта (продакт оунер). Как может пострадать разработка продукта при отсутствии четкого понимания самого образа продукта и конечного ответственного человека. Обозначим зону ответственности владельца продукта и результат его работы


Anna Vlasova
Analyst @ SimbirSoft
Dimitrovgrad
It's hard to be an analyst
of Голосование
  • Analyst in an IT company. Profile.
  • Education, certification
  • Skills which come useful in work
  • Skills which can be detrimental