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...
16 Pirmins Podcast Thought #16 Stay with your methods
Pirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast
5 minutes
1 year ago
16 Pirmins Podcast Thought #16 Stay with your methods
#16 Stay with your methods Once you start implementing a major software solution you will choose an implementation method, agile, scrum, waterfall, a special method from your partner, data first, logic first or what else is on the market and you think suits your business case best. All of these methods have shown that they work, at least for the business case they were developed. Make sure you have a suitable method and approach for your project. You should avoid mixing methods because ...
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...
