IAPM Essentials #80 - 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 November 16, 2021
This week, these three articles were particularly inspiring:
4 Reasons Data Analytics Projects Fail
Digital transformation projects are difficult by definition. They challenge and restructure the way companies work. For this reason, here is a list of the four most common mistakes in these projects. Firstly, they start straight away without planning. It is important not to deal with data, tools or models at the beginning, but where possible to focus on the goal and not the path. Secondly, there is often a lack of results. People get stuck on one thing instead of achieving anything. The motto here should be: achieve the goal in a reasonable time or at least fail quickly to get it right afterwards. The third mistake is not presenting the product properly to the stakeholders. How the product is presented is at least as important as what is presented. A good presentation creates trust and is remembered. The last mistake is not assigning the right team. Without the necessary know-how, no matter how great the resources used, the project will probably still fail.
Click here to read the original article.
„Scrumban“ – How 5 Kanban practices help your Scrum team - German language
Although Scrum and Kanban cannot be combined, it is still possible to merge them. Then it is neither Scrum nor Kanban but "Scrumban". So how can you improve sprints with Kanban? For example, through visualisation on the Kanban Board: this creates a better overview and transparency. A division into task and team board additionally ensures that the overview is equally given for clients and team. Furthermore, a maximum can be set for the "Work in Progress" column, so that the team does not get overwhelmed. In addition, a system can be implemented that ensures that important, urgent and unplanned tasks have priority when they arise. Process rules that are clearly defined from the start ensure less confusion and discussion later on, and the implementation of feedback loops ensures continuous improvement and optimisation.
Click here to read the original article.
Are Fixed-Price Projects Agile?
How agile a team is depends on various factors. Three friends developing an app in a garage are probably more agile than a large team developing strictly regulated software for medical purposes. The latter requires extensive documentation and agreements, which certainly reduces agility. So how do fixed specifications affect agility? Can the team then work agilely at all? Yes, perhaps. As mentioned at the beginning, this depends on various factors, the context and the team. After all, constraints are only what the team makes of them. Does a contract prohibit or prescribe a certain communication structure? A good team adapts to that. Even if the relationship between provider and client is clearly regulated, this does not necessarily mean that collaboration is not possible. At the end of the day, it's about responding appropriately to change rather than strictly sticking to the process.
Click here to read the original article.
Digital transformation projects are difficult by definition. They challenge and restructure the way companies work. For this reason, here is a list of the four most common mistakes in these projects. Firstly, they start straight away without planning. It is important not to deal with data, tools or models at the beginning, but where possible to focus on the goal and not the path. Secondly, there is often a lack of results. People get stuck on one thing instead of achieving anything. The motto here should be: achieve the goal in a reasonable time or at least fail quickly to get it right afterwards. The third mistake is not presenting the product properly to the stakeholders. How the product is presented is at least as important as what is presented. A good presentation creates trust and is remembered. The last mistake is not assigning the right team. Without the necessary know-how, no matter how great the resources used, the project will probably still fail.
Click here to read the original article.
„Scrumban“ – How 5 Kanban practices help your Scrum team - German language
Although Scrum and Kanban cannot be combined, it is still possible to merge them. Then it is neither Scrum nor Kanban but "Scrumban". So how can you improve sprints with Kanban? For example, through visualisation on the Kanban Board: this creates a better overview and transparency. A division into task and team board additionally ensures that the overview is equally given for clients and team. Furthermore, a maximum can be set for the "Work in Progress" column, so that the team does not get overwhelmed. In addition, a system can be implemented that ensures that important, urgent and unplanned tasks have priority when they arise. Process rules that are clearly defined from the start ensure less confusion and discussion later on, and the implementation of feedback loops ensures continuous improvement and optimisation.
Click here to read the original article.
Are Fixed-Price Projects Agile?
How agile a team is depends on various factors. Three friends developing an app in a garage are probably more agile than a large team developing strictly regulated software for medical purposes. The latter requires extensive documentation and agreements, which certainly reduces agility. So how do fixed specifications affect agility? Can the team then work agilely at all? Yes, perhaps. As mentioned at the beginning, this depends on various factors, the context and the team. After all, constraints are only what the team makes of them. Does a contract prohibit or prescribe a certain communication structure? A good team adapts to that. Even if the relationship between provider and client is clearly regulated, this does not necessarily mean that collaboration is not possible. At the end of the day, it's about responding appropriately to change rather than strictly sticking to the process.
Click here to read the original article.
Further articles worth reading and podcasts worth listening, you should not miss:
#353: Managing Projects Without a Project Manager, with Ashley Steckler
Click here to read the original article.
A pretty burn-down usually means ugly Scrum
Click here to read the original article.
Brauchen wir wieder mehr Vorfreude in unserem Leben?
(en.: Do we need more anticipation in our lives again?)
Click here to read the original article.
Die Rolle von Experimenten in komplexen Situationen
(en.: The role of experiments in complex situations)
Click here to read the original article.
Die stillen To-do-Listen
(en.: The silent to-do lists)
Click here to read the original article.
Effizienz durch Wendigkeit
(en.: Efficiency through manoeuvrability)
Click here to read the original article.
How I Got Fired As A Scrum Master
Click here to read the original article.
Is Problem Solving a Team Sport or an Individual Effort?
Click here to read the original article.
Product Backlog Refinement – Tipps für Product Owner
Click here to read the original article.
The Ultimate Guide to Agile Reporting
Click here to read the original article.
Click here to read the original article.
A pretty burn-down usually means ugly Scrum
Click here to read the original article.
Brauchen wir wieder mehr Vorfreude in unserem Leben?
(en.: Do we need more anticipation in our lives again?)
Click here to read the original article.
Die Rolle von Experimenten in komplexen Situationen
(en.: The role of experiments in complex situations)
Click here to read the original article.
Die stillen To-do-Listen
(en.: The silent to-do lists)
Click here to read the original article.
Effizienz durch Wendigkeit
(en.: Efficiency through manoeuvrability)
Click here to read the original article.
How I Got Fired As A Scrum Master
Click here to read the original article.
Is Problem Solving a Team Sport or an Individual Effort?
Click here to read the original article.
Product Backlog Refinement – Tipps für Product Owner
Click here to read the original article.
The Ultimate Guide to Agile Reporting
Click here to read the original article.
Author: IAPM internal
Keywords: IAPM Essentials, Links, News