My application development experience as PM

I am a programmer at heart. He wrote his first program when he was 8 years old β€” playing on a tube TV (24 years ago). This project is a challenge for me. I personally have not written a single line of code. In the process, we outbid the main encoder. Daughter swallowed a battery - stress for a week. Coronavirus. And fakapy at the start, which led to additional costs by 25% of the budget. A team of 7 people and me. The implementation period is 4 months.


The main ideas in which it was established


  1. If your process takes more than a couple of hours a day - most likely everything is working incorrectly for you and many processes are tied to you personally .. 
  2. Everything must be done so that the team is self-organized. PM should only organize the process and only keep an eye on the processes.
  3. PM + Product is one profession, it’s a shitty result! (taken from Jobs biography). Design and UX are our everything! It doesn’t matter how cool you organize if the customer doesn’t like it !!! It is important to choose a talented designer for the project.
  4. From the start, organize the quality control department - in my case, this is a trusted tester (I emphasize trusted - I exclude collusion), which simultaneously monitors the processes 
  5. It is important to follow the step by step processes - this will greatly reduce the budget. Not all people need full time from the start.
  6. Simplify. Continuous improvement of kaizen. In my case, the periodic question is how to improve, speed up? What am I doing wrong? What can we simplify? etc
  7. , - .
  8. , β€” . . (- 100 ).
  9. . β€” . , . , β€” !
  10. . , PM. ( ) Product
  11. β€” . . . β€” 100% . β€” .



  1. PM , . . 
  2. , . β€” .
  3. . . . .
  4. β€” ( ). , . β€” 3 . 
  5. . ? ? ? ? β€” β€” , ! 
  6. . , 2-3 . - β€” !!!
  7. . β€” . 50.
  8. . ( )! β€” one to one.
  9. . 7- β€” . β€” 8+ . ( General Electric)
  10. . . 2 ( ). . β€” 2 .
  11. , . .
  12. β€” .
  13. UX
  14. . ( ). , . . .
  15. β€” (. )
  16. . , , . angular - . β€”
  17.   +2 ( )
  18. β€” , . β€” , . ? ? - .
  19. =
  20.   Zoom β€” . , .
  21. , . β€” , ( ). , , !!!!
  22. . . ( )
  23. , (. β€” ). , , . .
  24. β€” . ! . !!! ( 5- )
  25. . β€” . β€” !
  26. ! .
  27. 360 .
  28. . ? β€” . 20. . ( )
  29. . , . , - …  ( Agile)
  30. , . β€” . , .
  31. - .
  32. 1-2 3 , . . .
  33. β€” . . , . , .
  34. β€” , . .
  35. β€” 2 2
  36. β€” , , . , . , . - .
  37. It is necessary to keep a dossier on employees from the interview itself. Even those who were not taken to the project or to work. In my case, a small project was given to the interviewed employee as a freelancer. The customer is satisfied.

For work, I began to use Trello. Versatile and very comfortable. There added 4 plugins and slightly changed the logic of work on kanban. Thank you all and good code.


All Articles