IAPM Essentials #77 - News from the project management world
What was eventful last week? What has happened in project management? Here you can find articles worth reading and links to videos or podcasts that we warmly recommend.
To put it briefly: Essentials from the world of project management.
Enjoy reading!
To put it briefly: Essentials from the world of project management.
Enjoy reading!
IAPM Essentials October 26, 2021
This week, these three articles were particularly inspiring:
3 Ways Organizations Use Measures Poorly
Measurement is important. However, it is equally important to understand why you are measuring data and how you are using it. Many mistakes can be made here that can lead to undesirable results. Two common mistakes are to view measurements as a guarantee of success or failure. Instead, they should be used as a guide. Otherwise, the goal may be to achieve good numbers instead of completing a successful project. This can lead to another mistake: The customer benefit gets out of focus. This is particularly difficult to measure because it can be influenced by many factors and is very difficult to control. Multiple perspectives can be very helpful here. It is important to recognize errors in dealing with measurements and to adjust processes accordingly.
Click here to read the original article.
5 agile metrics you won’t hate
Measurements offer a good way to represent the state at a point, but fail to represent a period of time and are always in the past. While this may seem less problematic in traditional project management, in agile project management it provides no information about the effectiveness of the team. Important clues here are clear structures in the team: Is everyone aware of their role? Furthermore, it must be considered whether the sprint and product goals are clear. Additionally, there is the awareness of the "batch size". What size is best for the team? Another big point is the reliability of the team, or individual members, and the quality of their work. Last, but equally important, are the demands the team makes on itself. Teams that make high demands on themselves strive for improvement and are more motivated.
Click here to read the original article.
These four core competencies every project manager should possess - German language
IT projects often cannot be planned from start to finish. For this reason, project managers need to possess special skills, the four most important of which are presented here. The project manager must be competent. He or she is the contact person for all problems, motivates employees and must maintain an overview of the project. In addition, he must be able to plan ahead and at the same time make sure that the plan is not too rigid so that agility doesn't get lost. An agile approach is important for the whole team, but especially for project managers. In the end, they are the ones who spread the agile mindset throughout the company. A project manager should also not lack the ability to act economically. Costs and budget are always major issues, which he must not lose sight of.
Click here to read the original article.
Measurement is important. However, it is equally important to understand why you are measuring data and how you are using it. Many mistakes can be made here that can lead to undesirable results. Two common mistakes are to view measurements as a guarantee of success or failure. Instead, they should be used as a guide. Otherwise, the goal may be to achieve good numbers instead of completing a successful project. This can lead to another mistake: The customer benefit gets out of focus. This is particularly difficult to measure because it can be influenced by many factors and is very difficult to control. Multiple perspectives can be very helpful here. It is important to recognize errors in dealing with measurements and to adjust processes accordingly.
Click here to read the original article.
5 agile metrics you won’t hate
Measurements offer a good way to represent the state at a point, but fail to represent a period of time and are always in the past. While this may seem less problematic in traditional project management, in agile project management it provides no information about the effectiveness of the team. Important clues here are clear structures in the team: Is everyone aware of their role? Furthermore, it must be considered whether the sprint and product goals are clear. Additionally, there is the awareness of the "batch size". What size is best for the team? Another big point is the reliability of the team, or individual members, and the quality of their work. Last, but equally important, are the demands the team makes on itself. Teams that make high demands on themselves strive for improvement and are more motivated.
Click here to read the original article.
These four core competencies every project manager should possess - German language
IT projects often cannot be planned from start to finish. For this reason, project managers need to possess special skills, the four most important of which are presented here. The project manager must be competent. He or she is the contact person for all problems, motivates employees and must maintain an overview of the project. In addition, he must be able to plan ahead and at the same time make sure that the plan is not too rigid so that agility doesn't get lost. An agile approach is important for the whole team, but especially for project managers. In the end, they are the ones who spread the agile mindset throughout the company. A project manager should also not lack the ability to act economically. Costs and budget are always major issues, which he must not lose sight of.
Click here to read the original article.
Further articles worth reading and podcasts worth listening, you should not miss:
A Scrum Flight Checklist
Click here to read the original article.
Continuous Improvement Storyboards
Click here to read the original article.
Die drei Säulen der Agilität: Empirie, Empowerment und Ownership
(en.: The Three Pillars of Agility: Empiricism, Empowerment and Ownership)
Click here to read the original article.
Hilfe, warum sind unsere Mitarbeiter so passiv?
(en.: Help, why are our employees so passive?)
Click here to read the original article.
Ignite Continuous Improvement In Your Scrum Team
Click here to read the original article.
Mein Umgang mit Unterbrechungen und Ablenkungen
(en.: My approach to interruptions and distractions)
Click here to read the original article.
Stacey Matrix (II)
Click here to read the original article.
Stillness & Curiosity
Click here to read the original article.
User Story Splitting: Wie geht das „richtig“?
(en.: User Story Splitting: How does it work "correctly"?)
Click here to read the original article.
Work Improvement before Equipment Improvement
Click here to read the original article.
Click here to read the original article.
Continuous Improvement Storyboards
Click here to read the original article.
Die drei Säulen der Agilität: Empirie, Empowerment und Ownership
(en.: The Three Pillars of Agility: Empiricism, Empowerment and Ownership)
Click here to read the original article.
Hilfe, warum sind unsere Mitarbeiter so passiv?
(en.: Help, why are our employees so passive?)
Click here to read the original article.
Ignite Continuous Improvement In Your Scrum Team
Click here to read the original article.
Mein Umgang mit Unterbrechungen und Ablenkungen
(en.: My approach to interruptions and distractions)
Click here to read the original article.
Stacey Matrix (II)
Click here to read the original article.
Stillness & Curiosity
Click here to read the original article.
User Story Splitting: Wie geht das „richtig“?
(en.: User Story Splitting: How does it work "correctly"?)
Click here to read the original article.
Work Improvement before Equipment Improvement
Click here to read the original article.
Author: IAPM internal
Keywords: IAPM Essentials, Links, News