Hard Things by Easy Words: How the laws of the system approach in IT Projects can be Violated. Part 4

laws of the system approach

Continuation. How systems break down. We do not really support the statement “I know exactly how it is supposed to be as I have experience in … for several years”. I stand for common sense, flexibility and the constant expansion of knowledge boundaries. The theme of the need for a business analyst in IT projects … Continue reading "Hard Things by Easy Words: How the laws of the system approach in IT Projects can be Violated. Part 4"

Read More

Types of requirements. Examples

Requirements types

Continuation of the Requirements types overview. The previous post see here. “Transitional requirements” is the group of requirements, which operates while the solution is being formed. Transitional requirements are formulated while searching for solutions to the business problem. At this stage, the analysis of business processes is carried out pretty often, which brings us to … Continue reading "Types of requirements. Examples"

Read More

SGS Model

SGS Model

SGS model by Robertson: Stakeholders SGS model as a basis for requirements development and business modelling is suggested by James and Suzanne Robertson. SGS stands for Stakeholders, Goals, Scope (of the project). All three components are interacting (see the picture below) and define the space in which project requirements are being shaped. Stakeholders notion Stakeholder … Continue reading "SGS Model"

Read More

Three Pillars of Business Analysis in Information Technology

Business Analysis in Information Technology

The space in which project requirements are shaped appears in the result of SGS-model parts interaction (SGS stands for Stakeholders, Goals, and Scope). Carrying on this topic, it is possible to point out three fundamental aspects of Business Analysis in Information Technology (IT) Solution/product idea (project/product view and scope), Stakeholders, Requirements.

Read More

It’s All About Numbers – the Price of business analysis mistakes (Part 2)

Regardless of occasional economic turmoil all over the world, companies keep increasing their investments into software products. At the same time, the costs of the business analysis mistakes in the software development process are impressive. According to CIO Magazine, 71% of software projects that fail do so because of poor requirements management.

Read More

Business and System Analysts: Two Points of View

System Analysts

Probably the most arguable moment in understanding who is actually a business analyst – is the question of differentiation between business and system analysts. Let’s have a look at two existing Points of View in this respect. Point of View #1 Suggests that all analysts can be divided into business analysts and system analysts (depending … Continue reading "Business and System Analysts: Two Points of View"

Read More

It’s All About Numbers – Business analysis value and the Price of BA Mistakes

Business analysis value and the price of mistakes

Business analysis value is demonstrated in the table below. It shows the relative expense of fixing defects depending on when they’re introduced and when they’re found (including Requirements stage). Time detected Time introduced Requirements Architecture Construction Testing Post-Release Requirements 1 3 5-10 10 10-100 Architecture – 1 10 15 25-100 Construction – – 1 10 … Continue reading "It’s All About Numbers – Business analysis value and the Price of BA Mistakes"

Read More

Hard Things by Easy Words: Basics of System Approach. Part 1

system approach

Talking about self, advanced IT experts very often mention the system approach and system thinking, pointing out at the same time to a personal organization, the ability to foresee and take into account, time management and following the plan, discipline, regularity of self-education activities, raising the level of qualifications, etc. Undoubtedly, these are the key … Continue reading "Hard Things by Easy Words: Basics of System Approach. Part 1"

Read More