|
shortki
|
 |
« Reply #1 on: November 02, 2016, 01:47:28 AM » |
|
Thank you for sharing your workflow.
Unfortunately, I have little experience in the preparation of the participation in such events, but there are a few general points I can comment on.
First, almost all projects have one "source" or reason, this is, in fact, the goal of the project, so in this respect your process is not unique.
Secondly, your example is a classic case of the checklist project. Here, it should be noted that composing a well-written checklist is the art, for example, the military spent a lot of effort and money to learn how to make such lists properly.
inShort, you do not need to strive to do everything at once, even if it is possible.
1. Select several processes:
a) early implementation of which gives an advantage,
b) processes that contain possible contingencies,
c) long-term processes.
2. Make an initial linear list out of them, then add in the beginning the processes that in fact should be fulfilled before selected ones.
3. Add the remaining items.
4. Select the items, the result of execution of which can "deteriorate" over time, or it is expensive to be stored for a long time — move them closer to the end.
5. And only now, make separate processes, which are executed by different people and do not depend on each other, parallel.
6. For each process, create a resource that lists easily verifiable criteria for successful implementation.
Oh, and you also have an inaccuracy in the diagram "Travel & Accommodation": the inputs of the process "Reservation" must have different ports of activation, as is clearly seen that only one of them can be active. Also, it is not clear why the process "Travel Binder" is designed as a folder, though it does not seem to be a separate independent project.
P.S. Try to use the ISH format when exporting, it is more complete, WFL files are intended for the exchange of diagrams with workflow.link system.
|
