we learn to manage not formally, but effectively

we learn to manage not formally, but effectively

I will share my own experience of working in an IT company that uses project management. I will try to highlight important things in effective work, which, it would seem, are not visible and which I had to face. I do not have a goal to delve into the management project. And that is why there are PMI standards The Standard for Portfolio Management, GOST R 54870-2011 “Requirements for project portfolio management”. I would like to note that I work in the public sector, but perhaps the experience will be useful for everyone.

A little about myself. Oksana Mykolaivna Petryashova – head of the development department for 5 years, with a lot of experience. Everything said below is personal experience and subjective opinion.

Chapter one. You cannot live without people. Personnel decides everything

Division of roles

Project managers should do projects! If the manager goes into routine processes, the ship does not sail, processes are delayed, work is not parallelized, control is lost. The connection with the team must be established firmly, but it is impossible to merge with the team because problems with routine never end. What to do? We separated people territorially. Added projects that “endure” to stay in shape. Leaders were united in a team to share experience and support.

Motivation

There are different methods of determining motivation. For example, the Harvard system. Financial motivation is the most effective, but not for everyone. For ideological people, a common spirit is needed, for some, social projects are important.

We get rid of toxic people

Toxic people in the team are not immediately visible. They know how to build good relations with management. In state structures, it is still necessary to try to release the toxic person, but they can be sent to correctional works, which will be handled well.

We pump skills and abilities. Let’s not forget about soft skills

  1. There are enough courses on project management on the market. We chose a well-known educational organization. There are no complaints against the company. The teachers are competent, but as it turned out, the percentage of settled material in the head depends on the teacher. Therefore, we choose a teacher with experience in the IT field. Everyone will be able to read the textbook.

  2. Competency assessment in the organization should be conducted and checked, but this is a separate topic.

  3. Systems thinking. Is it necessary to develop systems thinking in employees within the company? – Of course, you should. After the courses, people change, they evaluate risks from a different point of view. Fewer go astray. And it’s nice to work with smart people. You grow yourself – grow your teams.

  4. Presentations and public speaking. These employee rocks enhance the company’s identity.

  5. Ethics. Either a person has it or not. IT specialists often have a limp. Throw in slippers, but in my experience, a higher education at a prestigious faculty = intelligence in the eyes and ethics to boot.

PS Throughout my work experience, I can say that incompetent specialists and rudeness cost the company millions if there is competition. But their management will never know about this.

Chapter two. Work tools for a project approach

Why are tools in second place? – Because a good specialist will draw a diagram, describe processes, assess risks with a pencil and paper. And an intelligent system will not save a “non-sharp” specialist. And so our work experience:

  1. One of the most popular Project systems. We did not use all the functionality of the system for a number of reasons, in particular the import of the software. It helped to track plans, schedules and people employed in the project. There are much more opportunities there.

  2. CRM system. They used the functionality of working in groups for tasks, general documents, and chats. A useful thing has a lot of functionality and can be developed for yourself.

  3. There was the experience of implementing own project management system with an attempt to break the principles of project management. Sounds funny, right? But the experience was there. Don’t do that. Return to point 3 and increasing the competences of employees.

  4. Something primitively simple in the form of tables based on a cloud solution with joint editing of documents.

  5. Any Project systems. There are many of them on the market. We use the system project inside the SED. This is a great choice when you have the main SED from the same developer. All in one. Both SED and Gantt charts, deadlines, labor costs, tasks in a single window, connection with official documents, Agile board. There are many fantasies for collaborations. Also the topic of a separate article.

Chapter three. Documentation

From a wide range of communication in the IT environment. In real life, it turns out that there are huge systems that you would never think of that have no documentation.

It is very important. A tattoo on the forehead. The holiest of holies. documentation. Yes, GOST 34 – causes a lot of controversy due to the redundancy of the design and redundant composition of documents, but it is absolutely impossible to do without it. I will go through my main milestones objectively and subjectively.

  1. Project charter (problem, goal, task, risk assessment, resource assessment, analysis of implementation options). At all stages, you have to return to the goal. A controversial question has arisen – return to the goal and you will find the answer there.

  2. Collection of requirements (under the protocol).

  3. Business requirements in BPMN. It is absolutely necessary to reengineer the processes.

  4. Analysis of options.

  5. Technical task.

  6. Sketch project and technical project. Optional. depends on the complexity.

  7. Test programs and methods. Without them, the process is very long and can turn into a mess. Loss of time is loss of money.

  8. Test protocols. Audio, video recording of meetings with the customer at the stage of examination, testing, acceptance. (Very, very necessary in complex projects with a large number of customers, saved many times).

  9. Acts of work.

  10. Software code, if shared, then Git.

  11. User and administrator instructions. The latter is often forgotten. And what then?!

  12. Courses for users in the format of your learning system. We are for Scorm.

I hope the information will be useful, even if it is brief. I wish you success and development. Although the life cycle is a ring, it moves forward in a spiral. Go to the goal and achieve. All strength and energy.

Related posts