IAPM Essentials #59 - 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 June 22, 2021
This week, these three articles were particularly inspiring:
Methodik in der Softwareentwicklung: Agil versus Wasserfall - (German language)
It is said that those who still use the waterfall model in software development have not yet arrived in the modern age. The trend is now clearly moving in the direction of agile methods such as Scrum or Kanban. A look at the Fortune 500 companies shows that digital natives with modern working methods dominate the market. These companies can introduce new business models, products and innovations in much faster cycles than others. In the following article, Jochen Malinowski explains why agile methods are indispensable for companies in software development today.
Critical Chain Projektmanagement verständlich erklärt - (German language)
Critical Chain Project Management complements and improves typical project management. On the one hand, the respective resources are planned in addition to the work packages and on the other hand, no local time reserves are planned, only for milestones and the overall project. This may not sound like much of a change, but it can save a lot of time over the entire project mainly due to psychological effects. For example, it prevents time reserves from being exploited (Parkinson's Law) or tasks from being started as late as possible (student syndrome). How CCPM works in detail is explained by Dieter Zibert in the following article.
Click here to read the original article.
What Is A RACI Chart? Everything You Need To Know About This Project Management Tool
R, A, C, I means Responsible, Accountable, Consulted and Informed. The RACI chart is used to clarify the functions and responsibilities of employees for each task. Specifically, it answers the questions of who is responsible for performing the task, who decides if the task was performed correctly, who is consulted about the performance of the task, and who is informed about the results of the task. The aim is to ensure clear communication and a smooth workflow in all parts of the team. You can read all details about this topic in the following blog post by Dana Sitar and Rob Watts.
Click here to read the original article.
It is said that those who still use the waterfall model in software development have not yet arrived in the modern age. The trend is now clearly moving in the direction of agile methods such as Scrum or Kanban. A look at the Fortune 500 companies shows that digital natives with modern working methods dominate the market. These companies can introduce new business models, products and innovations in much faster cycles than others. In the following article, Jochen Malinowski explains why agile methods are indispensable for companies in software development today.
Critical Chain Projektmanagement verständlich erklärt - (German language)
Critical Chain Project Management complements and improves typical project management. On the one hand, the respective resources are planned in addition to the work packages and on the other hand, no local time reserves are planned, only for milestones and the overall project. This may not sound like much of a change, but it can save a lot of time over the entire project mainly due to psychological effects. For example, it prevents time reserves from being exploited (Parkinson's Law) or tasks from being started as late as possible (student syndrome). How CCPM works in detail is explained by Dieter Zibert in the following article.
Click here to read the original article.
What Is A RACI Chart? Everything You Need To Know About This Project Management Tool
R, A, C, I means Responsible, Accountable, Consulted and Informed. The RACI chart is used to clarify the functions and responsibilities of employees for each task. Specifically, it answers the questions of who is responsible for performing the task, who decides if the task was performed correctly, who is consulted about the performance of the task, and who is informed about the results of the task. The aim is to ensure clear communication and a smooth workflow in all parts of the team. You can read all details about this topic in the following blog post by Dana Sitar and Rob Watts.
Click here to read the original article.
Further articles worth reading and podcasts worth listening, you should not miss:
Agil sein muss man auch wollen
(en.: You also have to want to be agile)
Click here to read the original article.
Agil unter Druck
(en.: Agile under pressure)
Click here to read the original article.
Das fragmentierte Product Backlog konsolidieren
(en.: Consolidate a fragmented Product Backlog)
Click here to read the original article.
Gefangen in der Methodenfalle
(en.: Caught in the method trap)
Click here to read the original article.
How to manage your schedule when your hair is on fire
Click here to read the original article.
How to prevent scope creep when managing a project from home
Click here to read the original article.
Rindle: A New Way To Automate Project Management
Click here to read the original article.
The Scrum Team Charter Canvas
Click here to read the original article.
Warum ich überzeugt bin, dass Effectuation in den Werkzeugkoffer der agilen Verwaltung gehört
(en.: Why I am convinced that Effectuation belongs in the toolbox of agile management)
Click here to read the original article.
What’s the best way you can measure the value of Agile coaching?
Click here to read the original article.
Why Spotify Squads Are a Popular Failure for Product Teams
Click here to read the original article.
(en.: You also have to want to be agile)
Click here to read the original article.
Agil unter Druck
(en.: Agile under pressure)
Click here to read the original article.
Das fragmentierte Product Backlog konsolidieren
(en.: Consolidate a fragmented Product Backlog)
Click here to read the original article.
Gefangen in der Methodenfalle
(en.: Caught in the method trap)
Click here to read the original article.
How to manage your schedule when your hair is on fire
Click here to read the original article.
How to prevent scope creep when managing a project from home
Click here to read the original article.
Rindle: A New Way To Automate Project Management
Click here to read the original article.
The Scrum Team Charter Canvas
Click here to read the original article.
Warum ich überzeugt bin, dass Effectuation in den Werkzeugkoffer der agilen Verwaltung gehört
(en.: Why I am convinced that Effectuation belongs in the toolbox of agile management)
Click here to read the original article.
What’s the best way you can measure the value of Agile coaching?
Click here to read the original article.
Why Spotify Squads Are a Popular Failure for Product Teams
Click here to read the original article.
Author: IAPM internal / Felix Gebhardt
Keywords: IAPM Essentials, Links, News