The risks will not cope with themselves, and the backlog will not do itself
Today’s issue contains 2 videos from our project managers. Just 30 minutes with a cup of hot tea or coffee and you are up to date on working methods. Isn’t this the most important thing?
How to manage project risks without slipping into formalism
Ivan Zverev, project manager
There is a definite point from which to start managing risks. And they don’t write about this in any PMBOK. When to manage risk? How to attract a team? What is the algorithm? What are the practical benefits? Vanya will tell you how he figured it out himself.
1:18 What will the report be about? Borders
3:15 Modeling the situation about Peter’s email
5:31 What questions should you ask yourself?
7:30 Risk management format
8:34 When should risk be managed?
11:47 Whom to attract?
13:37 How to overcome resistance and convince the team to participate?
15:50 How to Prepare for a Risk Management Session?
19:05 Session algorithm
26:45 Typical errors
28:05 Conclusions – briefly about the main
Backlog autoscoring
Pavel Zimin, project manager
In the report, the speaker shares how to prioritize tasks based on incomparable factors and build a system where important tasks will not be lost.
0:47 About product and team
2:41 Team disputes – what to develop next?
5:54 Priority system. Model criteria
7:10 Reach
8:30 Confidence
10:53 Impact to tech
12:52 Impact to money
14:35 Impact to user
17:32 Effort
18:12 Scoring model
18:37 An example of comparing two bugs
19:48 How the backlog autoscoring process works
23:25 How to instill such a model in a team?
27:04 What profits can you get from the model?
All reports from the big IT conference YuMoneyDay… Materials on PM, testing and mobile development are on the way.
- Financial service architecture
- Make massive changes to microservices, automate code reviews and save the team’s nerves
- More, more frontend
- Our rake is the key to your success. DevOps and SQL Command Cases
