Pirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast
Pirmin Bercher
33 episodes
4 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...
27 Pirmins Podcast Thought # 27 Multi sources for messaging create confusion
Pirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast
5 minutes
2 months ago
27 Pirmins Podcast Thought # 27 Multi sources for messaging create confusion
# 27 Multi sources for messaging create confusion If you use reminders / messages generated by workflow or systems, try to keep them to a needed minimum as they will sooner or later be ignored. Try also to avoid to have these mes-saged from multiple sources / different communication ways. They all look different, requesting different actions. The more you have different ones, the more likely is that a user oversees them or interpret them as a possibly unwanted message. This applies especially...
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...
