There is a huge amount of information on Habré, with a description of a flexible methodology. There are texts describing how cool it is when everything goes on scrum in your team. But when it comes to introducing fashionable methodologies, the information in the articles is limited to a couple of sentences in the key “fill in the backlog, do the planning, enjoy the increased team work efficiency”
This article is intended for those who have already heard something about agile methodologies, are familiar with some agile terminology and are confident that the scrum approach is really necessary in your department within the company.
How to find out that the IT department in my company really needs scrum?
A sign of a suboptimal process in the work is multiple complaints from other departments. This is exactly what happened with us. Each department within the company poured blame on the adjacent department and, necessarily, on IT.
Regarding IT, they have always said that the development of “simple” things is delayed. The concept of “simple” was usually invested in the development of entire projects, which even a well-established development team takes more than 2 months
Symptoms were visible inside the team:
- Timlid did not know what each programmer was doing , because ...
- ... because programmers accepted tasks in the corridor , from heads of other departments or company management
- The priority of tasks was measured in the range from urgent to “we don’t leave until we do it”
- Deadlines never met
- Project information was passed on by word of mouth
Image from https://pikabu.ru/story/zamknutyiy_krug_rossiyskogo_biznesa_4270437
If the business processes inside your company are similar to this picture, and the developers are in eternal stress, then your situation is very similar to the one in which our company was located. Further steps describe one of the solutions to this situation. I hope that the next 10 iterations of the introduction of scrum will be able to move the business and the team from a dead point and will benefit.
Team lead tools
, :
- Jira
- Gitlab / github / bitbucket
- Confluence
- Google drive
- IT
, : , , , , , Google, Apple Tesla . ? , «»?
, , , .
?
- , - , , .
- , . 10 5 .
- .
, , , 4-
. « , »
IT . 10 2. « », , .
«» IT .
: , .
.2
, . , , . IT . , , , , , . 100 100 , //.
: , .
. +2 . , - , — .
, .
.3
— . , . , , , … , , 10 19 . .
:
jira 4 : « », « », «» cost of delay, , .
4 : «», «», «» storypoint — ?
, , , , .
: . , , — . .
. .
.4
, : -?
, 10%, , .
: - , . , . , 3 .
. .

.
: , , , .
.5
, , , . , ?
: .
, , + 50%, .
: , , . , - ( ?)
.6
- , , . , . , . .
. «» . . - , - .
, , .
: .
.7
, . , !
: , . .
, -, , , .
: , . .
.8
.
- 3- — TODO-IN PROGRESS — DONE
.
- . - , , .
: , 90%, , .
- — c. , . , . , , .

, , .
: , . …
.9
, 10-15 . 5 . . , . todo ready. , , .
: - .
.10
, , , .
, .
, . , , - , 15 . .
After taking 9 difficult steps, you could clarify the work of the whole department in the company, possibly increasing its efficiency several times, but how many pains you encountered - you can’t count. It could take months for some iterations, and sometimes, without proper pressure, a rollback to the previous steps could occur, because it is always easier to go back. But if you are already here, then I am glad to congratulate you on passing this thorny path.