Agile, Six Sigma and No Principle

In the last article, we started diving into the development process. The first stage of this process is planning. At this stage, the project manager, together with other team members, forms a pool of tasks in accordance with some kind of project management methodology. 

Methodology is a tool. And there is always some kind of philosophy behind the choice of a tool. In this publication, we will look at the main philosophies that are applied in the IT field (and not only in it).


This approach is based on flexibility, adaptability and cooperation. Agile methodologies allow teams to work effectively on projects, especially in conditions of rapidly changing requirements and uncertainty.

Key principles:

Iterativity. The project is divided into short cycles called sprints. A certain amount of work is carried out within sprints. Each sprint leads to the creation of a product suitable for demonstration.

Cooperation and communication. Agile implies close interaction between team members and the customer. Communication contributes to a better understanding of requirements and changes.

Flexibility and change. Agile is a very flexible approach. It involves rapid adaptation to changes in priorities, requirements and other factors.

A working product as a measurement of progress. At the output of each iteration, a tangible result is obtained. This allows the customer and the team to see real progress and give feedback.

Self-organization. The team is given freedom in decision-making and work planning. This contributes to a more effective use of skills and motivation of participants.

Six Sigma

This principle is based on striving for excellence, increasing efficiency, quality of products or services and, as a result, improving customer satisfaction.

Key principles:

Focus on customer needs. The product or service must fully meet the expectations and requirements of customers.

Data usage and analysis. The focus is on data analysis to determine which aspects of the process need improvement. Decisions are made based on evidence, not based on assumptions.

A strategic approach to improvement. Within the framework of this principle, improvement is a strategic process. It should be integrated into the organizational culture and business strategy.

An iterative approach. The improvement process goes through several stages, including definition, measurement, analysis, improvement and control, or definition, measurement, analysis, improvement and design. But unlike Agile, iterations can be lengthy.

Employee training. Employees should develop regularly. With the development of employees, the quality of services improves and overall customer satisfaction increases.

Top-level leadership and support. In such projects, managers are involved in the process and provide various assistance at each stage.

Lack of principle

This is a very common project management philosophy. It is based on the oral formulation of tasks, the absence of any tools to track the progress of their implementation and the implementation of the project as a whole. All control rests on the entries in the manager's diary.

The gurus of this philosophy assume that it leads to the fastest result, since there is no need to spend time on additional planning, development, and so on. But as the company grows, this approach leads to chaos, the consequences of which can be deplorable. 


Agile is often used in the IT field. It is flexible, dynamic, minimizes the main risk for any team — burnout. This approach is often combined with other philosophies, including production ones.



Composition of the IT development team

In this article we will look at the composition of the IT solution development team


About graphs, simply.

In this article, we will begin our acquaintance with graphs, get acquainted with the breadth-first search algorithm (BFS) and implement the graph in the Rust programming language.


What is the difference between outsourcing development and outstaffing an IT employee for development?

In this article we will understand what outsourcing and outstaff development are.


UI/UX design: The creation process

In this article we will talk about the main steps in the process of creating UI/UX design.


UI/UX design: Introduction

In this article, we begin to get acquainted with UI / UX design. This is the most important stage in the development of any visual application interface.


Meet the Pentest

We are beginning to consider one of the main methods of assessing the security of computer systems and networks for potential vulnerabilities - penetration testing


Reducing the implementation period of MVP

Let's figure out the timing of the implementation of the MVP.


Choosing a programming language

In this article we will talk about choosing a programming language to study


Testing an MVP concept

We will figure out how not to waste the budget on MVP development in vain


Application Architecture Design: Introduction

In this article, we will talk about the process of creating the architecture of an IT solution.


The terms of references: Structure

In this publication we will consider the universal structure of ToR


Incorrect estimation of the cost of IT contractor services

Today we will talk about the incorrect assessment of the cost of developing IT solutions. This pain is one of the main ones for enterprises and startups, including IT contractors themselves.


Introduction to Design Patterns in Software Development

In this article, we will begin to dive into the world of optimizing application architecture using design patterns.


Choosing the direction of development for programming training

In this article, you will find out what areas of IT development there are, how they differ and in which they pay more


OSI Model Levels

In this article, we will take a closer look at each of the levels of the OSI model


Main types of application architecture

In this publication, we will look at what application architectures are


10 ways to use Rust Cargo

In this short article I have collected 10 ways to use the build system and package manager of the Rust programming language


Documenting code in the Rust programming language

In this article, we will look at how documentation takes place in Rust and consider a very useful opportunity - writing tests through documentation.


Introduction to the OSI model

In this article we begin to consider the fundamental model of network interaction - OSI


CSS animation ripple

A simple example of how to implement ripple animation using HTML and CSS


What is the purpose of an ER-diagram in the development process?

Let's discuss in general terms what an ER diagram is and what it is used for.


From concept to MVP

In this article, you will learn, by example, how to move from a concept to an MVP without unnecessary complications in the functionality of the product


What are UML diagrams used for?

In this article we will talk about what UML diagrams are, what they are and where they are used


Introduction to writing the terms of references

The Terms of Reference are an important part of the development process. In this article, we will begin to dive into this issue.


Introduction to software development

Today, most companies are faced with IT development and often do not get what they want. In this article, we begin to dive into the process of creating IT solutions.


From idea to concept

In this publication, we will talk about how the idea differs from the concept. Let's do this with an example of a specific goal


IT project management methodologies: Waterfall, Scrum, Prince2

In this article, we will consider the basic methodologies of IT project management.


Weighted graphs

In this article, we will get acquainted with weighted graphs, Dijkstra's algorithm, and its implementation in the Rust programming language.


Development Process: Planning

In this publication, we will begin to consider the development process. Let's start with the planning process.