English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Tatiana K. Kravchenko - Professor, Head of Department of Business Analytics, National Research University Higher School of EconomicsAddress: 20, Myasnitskaya Street, Moscow, 101000, Russian Federation E-mail: tkravchenko@hse.ruSergey N. Bruskin - Associate Professor, Department of Business Analytics, National Research University Higher School of EconomicsAddress: 20, Myasnitskaya Street, Moscow, 101000, Russian Federation E-mail: sbruskin@hse.ru Requirements prioritization is performed by business analysts in order to analyze stated requirements and to define the required capabilities of a potential solution that will fulfill stakeholder needs. During the analysis, the business analyst transforms needs and informal concerns of stakeholders into formal solution requirements which describe the behavior of solution components in sufficient detail. Furthermore, requirements analysis may be performed to develop models of the current state of an organization. These models can be used in order to validate the solution scope with business and stakeholders, to analyze the current state of an organization to identify opportunities for improvement, or to assist stakeholders in understanding that current state. The requirements prioritization task includes the following elements. First, these are business cases which state key goals and measures of success for a project or organization. Priorities should be aligned with those goals and objectives. Business needs can be used as an alternative to the business case if no business case has been defined. Second, the prioritization requires that these requirements have been stated by stakeholders. Third, the list of stakeholders, annotated with their levels of authority and influence, is used to determine which stakeholders need to participate in prioritization. As a result, the several techniques and recommendations stated in the BABOK® Guide have been applied for requirements prioritization in a case study of a conventional commercial bank. The business needs of the organization have been identified. The main problems of the communication management process have been formulated. Underlying sources of the problem have been illustrated on a fishbone diagram (also known as an Ishikawa or cause-and-effect diagram). The list of stakeholders and the requirements have been made. The MoSCoW technique has been applied in order to identify four groups of requirements, which differ from each other by the impact the results of their implementation have on the solution of the identified problems. The list of prioritized requirements should be used on the next stages of the project. It may be useful for the project manager when planning works on the solution implementation. The results of this work should also help the stakeholders develop a common point of view on the strategic goals of the project.

Prioritization of requirements for effective support of the communication process with customers of a commercial bank