Pirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast
Pirmin Bercher
33 episodes
1 month ago
Watch it till the end, and next time when you have breakfast, think of the complexity # 33 Give me what I want not what I asked for The typical problem is that the requirements are not clearly defined which leads to a different solution. Make sure that the persons involved in the requirements definition understand the business case, understand to communicate this requirement to different stakeholders and to abstract their problem from the direct use case. Developers think different than func...
All content for Pirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast is the property of Pirmin Bercher and is served directly from their servers
with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
Watch it till the end, and next time when you have breakfast, think of the complexity # 33 Give me what I want not what I asked for The typical problem is that the requirements are not clearly defined which leads to a different solution. Make sure that the persons involved in the requirements definition understand the business case, understand to communicate this requirement to different stakeholders and to abstract their problem from the direct use case. Developers think different than func...
20 Pirmins Podcast Thought #20 Don’t change / widen your scope
Pirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast
4 minutes
4 months ago
20 Pirmins Podcast Thought #20 Don’t change / widen your scope
# 20 Don’t change / widen your scope Even though you should be open to increase the functionality, integration or usability of a solution, don’t change the scope once the project is started! Everybody tends to change or in-crease the project scope during the implementation phase as we all are learning and seeing that what we originally defined is not sufficient. Changing / adjusting the scope should only be done if there is an immediate and massive business value in-crease which over rules t...
Pirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast
Watch it till the end, and next time when you have breakfast, think of the complexity # 33 Give me what I want not what I asked for The typical problem is that the requirements are not clearly defined which leads to a different solution. Make sure that the persons involved in the requirements definition understand the business case, understand to communicate this requirement to different stakeholders and to abstract their problem from the direct use case. Developers think different than func...
