Pirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast
Pirmin Bercher
33 episodes
3 weeks 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...
14 Pirmins Podcast Thought #14 If plan “A” fails, the alphabet has 25 other letters
Pirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast
5 minutes
1 year ago
14 Pirmins Podcast Thought #14 If plan “A” fails, the alphabet has 25 other letters
# 14 If plan “A” fails, the alphabet has 25 other letters As mentioned in „A Plan is a Plan“, things can go wrong and will go wrong. (Remember Murphy’s laws) Most likely failure will happen the moment where it’s either completely unex-pected or most critical. A good thing to anticipate that, is to have a draft version of a backup / failure plan. This does not mean to have a detailed version of it, but having this in mind or drafted will help you to focus again if there is a major change...
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...
