August 25 and 26: Online Operational Management Conference
In May, I was fortunate enough to take graduation papers from students of our annual online executive education program. 250 people, 250 phoned with each. All in order to once again make sure that all people are different. Traditionally, we teach people in two directions: working with people and project management.
Working with people turns out to be useful for everyone, but not everyone has project management. It came as a surprise :) If the manager is obviously the project management manager is very necessary. But no. It turned out that 20% of our students do not manage projects from the word at all. They manage departments, support teams, etc. That is, they are where project activities under their control do not exist. But there is a lot of process control.
Hence the idea to make a conference about process management. There is a lot about project management and conference project managers, but it seems that they don’t talk about process management separately. And let's say.
')
The concept came up with this: to invite experts who would cover the materiel + practitioners who will tell about their process management cases. It turned out a small chamber conference, where we invite everyone:
First half of the day on the air: 6-8 speakers from different companies will tell about their experience and practical cases of debugging the processes of operating activities. Participation in the conference is free. Registration >>
Below is the conference program.
Held with the support of the Association of Managers “Stratoplan” and the PMI branch in St. Petersburg .
The program of the event:
“The process model of company management is not new, and has long become the mainstream for many Russian leaders. Business process maps, regulations, scorecards, and other tools should transform a result-oriented company. But behind the apparent simple approach lies the other side. Many companies that want to go on the process of management, make a lot of mistakes, starting to describe chaotically processes, confuse the state "as it is", "as it should", etc. As a result, the processes are described, "lie on the shelf", and there are no other changes.
In my report, I want to share the 5th most common mistakes in applying the process approach that I have encountered in my projects. We will talk about process “rakes and crutches” and discuss together how to avoid them. ”
“Not every day we create something fundamentally new. The team should be able to do well and repetitive tasks - without waste of power and with a guarantee of quality. For this, you need to describe the processes, there are hundreds of books, articles and automation tools on this topic. But when in practice you try to build typical processes - it does not happen easily. The thing is that for some tasks, jagged instruction is suitable, for others - prescribed algorithms in ERP, and for the third - the rhythm of regular brainstorming sessions on typical tasks.
Together we will figure out how to act in practice in each case.
We will answer the questions:
- When you really need to describe the processes, and where to start
- What are some popular examples describing typical processes?
- What should not be done in order not to systematize the processes “on the table”
- How can you “sell” the team an idea to work on typical processes?
- How to ensure the rhythm of process implementation in a team
What will happen as a result of the meeting:
- Consider examples of managing typical processes in a team.
- We will analyze the basic concepts and techniques
“Everyone will get a training manual with key steps and templates for managing typical tasks and processes.”
Hurdling: the history of the formation of the command mos.ru
“I entered the software industry in 2002 as a test engineer. He managed to work on private and public companies, participated in the creation of medical, banking software, military software, was engaged in the development of high-load systems. He went from engineer to top manager and head of large divisions. At the moment I manage the technical department in the project mos.ru. The sites kaspersky.com, woman.ru, itar-tass.com, banki.ru went through my hands and teams, equipment saves people’s lives, manages airplanes while the pilot drinks coffee, and something stands guard over our Motherland.
I will tell you how we have experienced growth from three in-house engineers and a large participation of customized development and administration to 35 in-house engineers in one year. How the team was recruited, how the groups were formed, why for the "carousel" is not children's entertainment, but a part of daily activities that save us when there is more work than there are performers. I'll tell you why at some stages we stopped, returned to the starting one, changed the strategy and started to grow again. How we took over the work from external performers: what work and modules were taken away first and foremost, and which competencies were increased, and that we still trust in our partners. Naturally, all this could not happen at the wave of the hand of a magician. It was partly a subtle calculation, partly luck, but mostly it was a lot of work and a desire to build a team and processes in such a way that everyone would be interested and comfortable, and the output would be a good product that millions of Muscovites use. ”
Now I am a “matrix manager” - I work for EPAM in St. Petersburg. On the one hand, I lead testing on one of the many projects. On the other hand, I play the role of a resource manager for 40+ people, that is, I am responsible for their development and employment on projects. In general, I collect a puzzle from “I want interesting tasks” and “we need an experienced person to do the work”. I am responsible for the full life cycle of my employees in the company - hiring, development, rotation, retention, etc.
“In my report I would like to talk about the problems of matrix organization on the example of our company EPAM. Then I will tell you about the tools and processes that we built to solve some of the problems of human development.
I would like to highlight the following issues:
1. Exhaustibility of the market of specialists
2. How to develop people who do not have current project objectives
3. Keeping employees in the company for a long time and ensuring a controlled replacement process
4. Transparency of the growth / transition between functions
5. Employee Motivation (How to Avoid Burnout)
6. Maintenance and development of specialization inside the function "
He started his career with a courier, a production manager, a developer, a project manager, a development manager, and now he is increasing the effectiveness of divisions and companies as a playing business coach.
Pavel will tell about five conditions, the fulfillment of which will increase the quality of your processes at times. We illustrate this with experience stories.
There will be 3 cases:
- from IT, where they worked on supporting Heinz projects
- outside IT: production, where the main production process is built, which led to a change in the entire company
- the story of how to restructure the company's processes in the context of lack of resources for companies with a lot more than 10,000 employees
We will talk about the change in the company's culture as a success factor:
- Result, not efficiency: what is the difference and what to focus on
- No need to worship tools: Kanban [substitute your own version] should not be the only tools
- To see the participants of the process: we begin to respect the colleagues who bring the applications and serve the users of our product
- Dependence of company culture on processes: processes will become as advanced as company culture allows and vice versa, culture will match your processes.
The way of learning and building the process of working in stories
Step 0. The start of the team can be described as "Here are the tasks, here is the team - go ahead!".
Step 1. Initial analysis of the incoming task.
So that the Customer was satisfied and the developer did not grieve, they added a new role to the team.
Step 2. Research by the developer.
We include in the process of work mandatory periodic communication with colleagues. First, remove the symptoms, then look for the root causes.
Step 3. Verification of the result by the tester or the Customer.
Fuzzy boundaries of responsibility win: everyone tests, and Dev, and QA, and the Customer, since each has its own context and case studies, so there is no double work.
Step 4. Confirmation by the Customer of the solution to the problem.
The fact that within the scope of the task someone did something does not mean solving the problem. Standup or sitdowns?
And of course, the details, the details and the conclusions!
"Startups and budgeting process"
At the end of the webinar, participants will learn:
- Why startups need budgeting;
- How budgeting helps strategy;
- How not to get into bondage to the investor;
- What mistakes do startups make in budgeting?
Despite the fact that there are two days left, the program of the event can be updated and supplemented, follow the announcements: newsletter, facebook.
25th and 26th of August. From 10:00 to 14:00 Moscow time.
Participation in the conference is free. Entries will be sent to all registered participants.
Registration (broadcast is organized in the gotowebinar system)
Working with people turns out to be useful for everyone, but not everyone has project management. It came as a surprise :) If the manager is obviously the project management manager is very necessary. But no. It turned out that 20% of our students do not manage projects from the word at all. They manage departments, support teams, etc. That is, they are where project activities under their control do not exist. But there is a lot of process control.
Hence the idea to make a conference about process management. There is a lot about project management and conference project managers, but it seems that they don’t talk about process management separately. And let's say.
')
The concept came up with this: to invite experts who would cover the materiel + practitioners who will tell about their process management cases. It turned out a small chamber conference, where we invite everyone:
August 25 and 26, ONLINE conference on operational management
First half of the day on the air: 6-8 speakers from different companies will tell about their experience and practical cases of debugging the processes of operating activities. Participation in the conference is free. Registration >>
Below is the conference program.
Held with the support of the Association of Managers “Stratoplan” and the PMI branch in St. Petersburg .
The program of the event:
Alexey Pikulev
Kanban coach and trainer, Unusual Concepts.
“The process model of company management is not new, and has long become the mainstream for many Russian leaders. Business process maps, regulations, scorecards, and other tools should transform a result-oriented company. But behind the apparent simple approach lies the other side. Many companies that want to go on the process of management, make a lot of mistakes, starting to describe chaotically processes, confuse the state "as it is", "as it should", etc. As a result, the processes are described, "lie on the shelf", and there are no other changes.
In my report, I want to share the 5th most common mistakes in applying the process approach that I have encountered in my projects. We will talk about process “rakes and crutches” and discuss together how to avoid them. ”
Ilya Alyabushev
Federal expert on the implementation of systematic work in teams of managers and employees. Speaker of many conferences. More than 100 implementations in the companies of the country.
“Not every day we create something fundamentally new. The team should be able to do well and repetitive tasks - without waste of power and with a guarantee of quality. For this, you need to describe the processes, there are hundreds of books, articles and automation tools on this topic. But when in practice you try to build typical processes - it does not happen easily. The thing is that for some tasks, jagged instruction is suitable, for others - prescribed algorithms in ERP, and for the third - the rhythm of regular brainstorming sessions on typical tasks.
Together we will figure out how to act in practice in each case.
We will answer the questions:
- When you really need to describe the processes, and where to start
- What are some popular examples describing typical processes?
- What should not be done in order not to systematize the processes “on the table”
- How can you “sell” the team an idea to work on typical processes?
- How to ensure the rhythm of process implementation in a team
What will happen as a result of the meeting:
- Consider examples of managing typical processes in a team.
- We will analyze the basic concepts and techniques
“Everyone will get a training manual with key steps and templates for managing typical tasks and processes.”
Roman Ivliev
Technical director of the project mos.ru
Hurdling: the history of the formation of the command mos.ru
“I entered the software industry in 2002 as a test engineer. He managed to work on private and public companies, participated in the creation of medical, banking software, military software, was engaged in the development of high-load systems. He went from engineer to top manager and head of large divisions. At the moment I manage the technical department in the project mos.ru. The sites kaspersky.com, woman.ru, itar-tass.com, banki.ru went through my hands and teams, equipment saves people’s lives, manages airplanes while the pilot drinks coffee, and something stands guard over our Motherland.
I will tell you how we have experienced growth from three in-house engineers and a large participation of customized development and administration to 35 in-house engineers in one year. How the team was recruited, how the groups were formed, why for the "carousel" is not children's entertainment, but a part of daily activities that save us when there is more work than there are performers. I'll tell you why at some stages we stopped, returned to the starting one, changed the strategy and started to grow again. How we took over the work from external performers: what work and modules were taken away first and foremost, and which competencies were increased, and that we still trust in our partners. Naturally, all this could not happen at the wave of the hand of a magician. It was partly a subtle calculation, partly luck, but mostly it was a lot of work and a desire to build a team and processes in such a way that everyone would be interested and comfortable, and the output would be a good product that millions of Muscovites use. ”
Andrey Degozhsky
Since 2001 in the IT industry. Since 2006, in QA, of which for 8 years I have been building teams / departments and developing people.
Now I am a “matrix manager” - I work for EPAM in St. Petersburg. On the one hand, I lead testing on one of the many projects. On the other hand, I play the role of a resource manager for 40+ people, that is, I am responsible for their development and employment on projects. In general, I collect a puzzle from “I want interesting tasks” and “we need an experienced person to do the work”. I am responsible for the full life cycle of my employees in the company - hiring, development, rotation, retention, etc.
“In my report I would like to talk about the problems of matrix organization on the example of our company EPAM. Then I will tell you about the tools and processes that we built to solve some of the problems of human development.
I would like to highlight the following issues:
1. Exhaustibility of the market of specialists
2. How to develop people who do not have current project objectives
3. Keeping employees in the company for a long time and ensuring a controlled replacement process
4. Transparency of the growth / transition between functions
5. Employee Motivation (How to Avoid Burnout)
6. Maintenance and development of specialization inside the function "
Pavel Kolosov
Business trainer. Works with Gazprom Neft and Rosneft on transformation in an IT company. In the past, Mail.ru, Rambler & Co, Tenzor, Alfa-Bank and others.
He started his career with a courier, a production manager, a developer, a project manager, a development manager, and now he is increasing the effectiveness of divisions and companies as a playing business coach.
Pavel will tell about five conditions, the fulfillment of which will increase the quality of your processes at times. We illustrate this with experience stories.
There will be 3 cases:
- from IT, where they worked on supporting Heinz projects
- outside IT: production, where the main production process is built, which led to a change in the entire company
- the story of how to restructure the company's processes in the context of lack of resources for companies with a lot more than 10,000 employees
We will talk about the change in the company's culture as a success factor:
- Result, not efficiency: what is the difference and what to focus on
- No need to worship tools: Kanban [substitute your own version] should not be the only tools
- To see the participants of the process: we begin to respect the colleagues who bring the applications and serve the users of our product
- Dependence of company culture on processes: processes will become as advanced as company culture allows and vice versa, culture will match your processes.
Max Vyaznikov
The former head of the technical support team, currently the owner of the product (Product Owner) is a self-service product of a large advertising network operating under the brand PropellerAds. He has experience in outsourcing as a project manager. Ex-owner of his own web studio. Entrepreneur.
The way of learning and building the process of working in stories
Step 0. The start of the team can be described as "Here are the tasks, here is the team - go ahead!".
Step 1. Initial analysis of the incoming task.
So that the Customer was satisfied and the developer did not grieve, they added a new role to the team.
Step 2. Research by the developer.
We include in the process of work mandatory periodic communication with colleagues. First, remove the symptoms, then look for the root causes.
Step 3. Verification of the result by the tester or the Customer.
Fuzzy boundaries of responsibility win: everyone tests, and Dev, and QA, and the Customer, since each has its own context and case studies, so there is no double work.
Step 4. Confirmation by the Customer of the solution to the problem.
The fact that within the scope of the task someone did something does not mean solving the problem. Standup or sitdowns?
And of course, the details, the details and the conclusions!
Alexander Sertakov
CFO with 10 years of experience in IT, banking and the oil and gas sector. He consults Russian startups on financial management, organization and strategy.
"Startups and budgeting process"
At the end of the webinar, participants will learn:
- Why startups need budgeting;
- How budgeting helps strategy;
- How not to get into bondage to the investor;
- What mistakes do startups make in budgeting?
Despite the fact that there are two days left, the program of the event can be updated and supplemented, follow the announcements: newsletter, facebook.
25th and 26th of August. From 10:00 to 14:00 Moscow time.
Participation in the conference is free. Entries will be sent to all registered participants.
Registration (broadcast is organized in the gotowebinar system)
Source: https://habr.com/ru/post/421009/
All Articles