Lately, I have been preoccupied with the feedback aspect of the design process, which is an important issue for anyone working with PI integration or PI development.
Feedback is not something you should seek at the end of a project. Why? Because it is easier to observe and correct small mistakes on the way, rather than realize there’s a huge flaw in your design when you finish. It is easier to change certain details as you go. Dissecting an enormous project and looking for design flaws is tedious work. Furthermore, changes are more difficult to make once you’re deep inside a jungle of work…who wants to turn back to a mistake made when 15% was ready, when they’re at 89%?
In order to avoid such situations, it is best to ask for constant feedback. Consulting is a crucial part of getting feedback – you can use an external consultant or ask for feedback from people working at your own organization. What matters is that the person providing feedback is knowledgeable in this field.
Your design has to be positive in all aspects. First of all, it needs to be suitable for your organization. You might also have performance requirements that you need to follow, therefore you need to think about other members of the organization as well. A detail of your design might come off as an impediment to someone else. By getting constant feedback, you will be able avoid the arising of such issues.
You also need to consider upgrade paths. If you are in the process of creating a ccBPM scenario, you have to think about migrating to BPMN soon. It is probably best if you avoid using ccBPM altogether.
Feedback can also help simplify things. Talk to a fellow developer! They might just see something you omitted. Talking about your ideas with other experts can lead to surprisingly positive results. You might realize that something can be done differently, in an easier or more advantageous manner.
Remember: you need constant feedback in order to avoid wasting time and effort in the long run. Most of the time, you’ll only need to change some minor details. However, if you let them pile up, they’ll lead to a nasty hindrance in the development process.
So don’t be afraid to talk about your projects and ask for feedback! Talking to another expert might lead you to new ideas and a better overall project.
The post Getting Feedback on Your SAP PI/PO Design appeared first on SAP PI course.