October 27, 2020
4 min readFrankly, We Have No Top Secrets That We Could Bring to Public Notice.
Also, it is not a secret that the first-place tool of a project manager — is personal responsibility. The Project manager who has this quality well-developed will seek and use the approaches described below regardless of reading this article. Work experience brings my colleagues to about the same paths. The information provided here will help newbies to speed up.
Secrets of Project Management in UDS
1. Functional testing is not enough.
We implement regression and smoke testing. It is especially relevant for the released systems, where the process of active development is still underway.
2. Make technical documentation.
We make technical documentation. Certainly, when you are running Agile, you always focus on a product first. But, if you manage - make technical documentation.
3. Document a technical debt.
It will simplify to "return" the depth in the future. If you document a technical debt, you will not waste time trying to recall all the nuances to get improved and all subsequent changes.
4. Use different bug-responding procedures.
Don‘t get hung up on the second-priority aspects! Make minor edits to a well-functioning one-piece system. Do not launch a pretty awful product but with a perfect bow tied on it.
5. Set up a Monitoring System with Telegram notifications about the problem in the system.
We find out about the "freezing" functionality or failure in the work of services BEFORE the client does. Thus, we have time to correct the situation BEFORE receiving complaints from users. It is a plus for credibility.
6. Use DIFFERENT templates to create new tasks and bugs.
If possible, we make them mandatory for filling in our bug tracking system. In the templates, we prescribe sections for important information and the rules for filling them out.
The above-mentioned increase the chances of getting an understandable task or bug into work and not wasting time on clarifying the standard conditions and requirements.
7. Create visual boards to control bugs in the bug-tracking system.
By opening aboard, we get complete and up-to-date information on the current bugs in the system and their status. Thus, we fully control the situation without any risk of missing anything.
8. Turn the Technical Design section into the task template (for new functionality).
The developers fill out the section and prescribe how a certain solution/functionality is technically implemented.
Such information helps a lot when documentation is absent. You can always find a task for the required functionality and see how the functionality SHOULD WORK and how the functionality IS IMPLEMENTED INDEED.
This will be enough for a successful start. Dear colleagues, I wish you well-deserved success, skilled advisors, and talented juniors. If anybody of you has questions, please contact us.