It happens all the time. Two programmers on different sides have to develop a piece of interface which integrates a couple of systems. It looks like that:
1. Customer’s Representative decides there has to be some integration work done. Vendor A is informed.
2. Here comes Project Manager from Vendor A. She agrees all the functional details.
3. Project Manager contacts Chief Developer and explains what has to be done.
4. Chief Developer finds victim er… Developer A who will do the job.
5. Developer A has a lot of technical questions (I mean a lot).
6. Questions are passed to Chief Developer.
7. Questions are passed to Project Manager.
8. Questions are passed to Customer’s Representative.
9. Customer’s Representative looks for someone from the Vendor B (deliverer of another system which is to be integrated) in panic. He finds Analyst.
10. Questions are passed to Analyst.
11. Questions are passed to Lead Developer on the B side.
12. Questions are passed to Developer B who implemented second system.
13. Answers are passed to Lead Developer.
14. Answers are passed to Analyst.
15. Answers are passed to Customer’s Representative.
16. Answers are passed to Project Manager (Vendor A).
17. Answers are passed to Chief Developer.
18. Answers are passed to Developer A.
19. Answers are vague. Darn. We go back to point 5.
In the meantime a bunch of emails was exchanged. A lot of time passed. Why don’t you just find a person who is able to understand enough details to satisfy all sides and let her bypass all other steps connecting directly with concerned developers? Why don’t you try to connect both developers directly? OK, with the customer in the middle it can be tough, but I’ve seen that so many times within the single organization.
I always try to shorten chain of information flow. Less hassle. Less delay.
Subscribe RSS feed
Follow on Twitter
Subscribe by email
