# 19  Aim for the stars
As your business vision is a vision and may never be achieved, your project vision must be open and wide. Don’t exclude ideas or solutions at the beginning. Think about all the integra-tion possibilities or features that would be great to use. As long as you stay realistic and know that aiming for the stars may result in landing on the moon, all is good. If you block yourself too early, you may even not reach a lift off.


It’s like always a fully unscripted recording ! 
Happy to get your feedbacks! 
If you liked .. spread the news !
If you can’t wait for next week https://www.pibeco.com/book/
If you want to support me  https://coindrop.to/Pirmin or   https://www.buymeacoffee.com/pirmin

IT - ERP - Projects 33 years of experience - 99 thoughts - 66 minutes to read: Not Another How To Book, available on Amazon.

Support the show

www.pibeco.com/book

#18Coca Cola is not Pepsi 
One difficult thing for people is to imagine similarity or mak-ing abstractions. A Cola beverage is mainly water, sugar (or substitute), color, flavor, CO2. (Some details missing  ... don’t hate me for that). If you now discuss at Pepsi a software im-plementation where you use the (perfect) slides you made for a Coca Cola project, the audience will in 90 % of the cases complain that „We are not Coca Cola and all is different“. They can’t abstract that making a Cola beverage is for nearly all Cola recipes the same… Just a different brand. If you want to get the buy-in from your team, especially if key users are involved, get as soon as possible reasonable test data, which reflect your company. Otherwise you will fight that users don’t understand the test case. (Comment form the author (me): if someone from a Cola beverage company is reading this and does not agree, please invite me for a call and tell me where I‘m wrong, happy to learn the differences.)


It’s like always a fully unscripted recording ! 
Happy to get your feedbacks! 
If you liked .. spread the news !
If you can’t wait for next week https://www.pibeco.com/book/
If you want to support me  https://coindrop.to/Pirmin or   https://www.buymeacoffee.com/pirmin

IT - ERP - Projects 33 years of experience - 99 thoughts - 66 minutes to read: Not Another How To Book, available on Amazon.

Support the show

www.pibeco.com/book

# 17 A partner is a partner 
If you choose to implement a larger software project, you should consider the role of external persons / your implementa-tion partner. Complex software implementations need a deep understanding in your business and a deep trust from you in your partners. You should consider your implementation part-ner as partner not as a vendor/contractor! Same applies for other involved persons like freelancers, developers, sub-contractors. If you integrate them in your team structure and have a work relation like a partnership, things will go easier when troubles arise. Like everywhere finding the „right“ part-ner is a hard task. It is not sure that you will find the perfect one, but changing your partner when the slightest troubles arise will not help for stability and success.


It’s like always a fully unscripted recording ! 
Happy to get your feedbacks! 
If you liked .. spread the news !
If you can’t wait for next week www.pibeco.com/book
If you want to support me coindrop.to/Pirmin or  www.buymeacoffee.com/pirmin

Support the show

www.pibeco.com/book

#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 it sounds more logi-cal/easier using step 1, 2 from method A and 3, 4 from method B and then back to method A. In most cases this will not work because of the fact that methods are a closed universe.  Open-ing it and mixing will create most likely issues. Don‘t try to be more intelligent than the inventor / creator of a method which was successfully used before


It’s like always a fully unscripted recording ! 
Happy to get your feedbacks! 
If you liked .. spread the news !
If you can’t wait for next week www.pibeco.com/book
If you want to support me coindrop.to/Pirmin or  www.buymeacoffee.com/pirmin

Support the show

www.pibeco.com/book

# 15 If a plan will fail, why should I plan?
Good question. Like a famous quote in military lessons „No plan will survive the first contact with the enemy“ (attributed as quote to many historical military persons). This has been proven by many battle plans in history, but military does not stop making plans. Are they stupid? Wasting time with plans? No they are highly intelligent! (However you can generally question if any kind of military action is intelligent). By play-ing / making the plans you start thinking about alternatives and different ways. In case your plan fails, you have an alternative.  


It’s like always a fully unscripted recording ! 
Happy to get your feedbacks! 
If you liked .. spread the news !
If you can’t wait for next week www.pibeco.com/book
If you want to support me coindrop.to/Pirmin or  www.buymeacoffee.com/pirmin

Support the show

www.pibeco.com/book

# 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 in plan „A“.


It’s like always a fully unscripted recording ! 
Happy to get your feedbacks! 
If you liked .. spread the news !
If you can’t wait for next week www.pibeco.com/book
If you want to support me coindrop.to/Pirmin or  www.buymeacoffee.com/pirmin

Support the show

www.pibeco.com/book

#13 A plan is a plan
When you handle complex projects, making a plan how to execute the different steps, identifying the critical path, defin-ing the resources and working on different scenarios is crucial-ly important. But life / your project will not follow your plan! The moment you signed off the plan, started to work on it, things will diverge from the plan. Now comes the situation everyone fears, the plan does not match the reality anymore and needs to be adjusted. The magic is about, how to keep a plan as long as possible aligned with the execution. You should have a good master plan with reasonable milestones but plan the execution not too long ahead. The longer ahead you make a detailed plan the more chances to changes/deviations from it you have.



It’s like always a fully unscripted recording ! 
Happy to get your feedbacks! 
If you liked .. spread the news !
If you can’t wait for next week www.pibeco.com/book
If you want to support me coindrop.to/Pirmin or  www.buymeacoffee.com/pirmin

Support the show

www.pibeco.com/book

#12  Don’t do too much parallel 
During project execution we will face challenges that things don’t go like they were planned. We then tend to find ways to optimize the progress.. These include strategies like adding more resources, but be careful, typical elementary school math question: if one musician plays a song in 5 min, how long does it take if you add 4 more, not 1 min.. it still remains 5 min and if they want to play it proper they need some preparation time!  Beginning already with the next step, even though the step before is not fully finished is complex. Like multitasking, this seems to be on the first glance a good way, especially when you have more people or different teams working on different steps. But like multitasking the coordination of these activities make things more complex and the overhead in coordinating and controlling these tasks eat up much of the benefits and make things riskier. If you can avoid, then go step by step, finish each step on time and diligently.


It’s like always a fully unscripted recording ! 
Happy to get your feedbacks! 
If you liked .. spread the news !
If you can’t wait for next week www.pibeco.com/book
If you want to support me coindrop.to/Pirmin or  www.buymeacoffee.com/pirmin

Support the show

www.pibeco.com/book

#11 What is said, is said
This goes with „People hear what they want to hear “, once a message is out, it's out! If you speak about budget and say any number, the moment you said it, this is the target budget, at least if it is less than the audience expected, even mentioning that it needs to be confirmed will not help in future discus-sions. The figures are in the head of the audience.
Same goes with a solution promise. If you confirm that this or that can be done, and the audience wanted to hear it, then you have to deliver, regardless how often you explain that you need to confirm / verify with the developer or so.


It’s like always a fully unscripted recording ! 
Happy to get your feedbacks! 
If you liked .. spread the news !
If you can’t wait for next week www.pibeco.com/book
If you want to support me coindrop.to/Pirmin or  www.buymeacoffee.com/pirmin

Support the show

www.pibeco.com/book

#10 People hear what they want to hear
You can have PowerPoints or Excel-sheets as many as you want. You can hold meeting and explain facts and details. In many cases the audience goes the easy way and „hears what is comfortable “. If you are on a tight budget, the finance team most likely will pay attention on any comment and information about staying in budget/reduced costs, but not hear the risks associate with it. Be careful what you say! 


It’s like always a fully unscripted recording ! 
Happy to get your feedbacks! 
If you liked .. spread the news !
If you can’t wait for next week www.pibeco.com/book
If you want to support me coindrop.to/Pirmin or  www.buymeacoffee.com/pirmin

Support the show

www.pibeco.com/book