In every EDI application, knowledge of the business needs and functions is of paramount importance. If you don't understand a "purchase order" or a "load tender" or a "health care claim or encounter" you'll never be able to map the ANSI or EDIFACT EDI data format for these transactions. In my experience, logistics is the toughest because of the many, many unrelated (by ownership) parties who need to be in the loop.
Well, you’ve identified the software functionality you need and have talked to your sources to get their opinions on how to go about developing it. In the back of your mind, though, you still think it should be part of the base translator package and ought to be included in a future release. What’s your next step?
We are seeing a trend in IT project management methodologies : the need for projects to be smaller and faster. Gone are the days of the multi-year, beaucoup dollars, cast of hundreds kind of project. Rather than planning a huge project from start to finish before holding the "kickoff meeting," CIOs need to fly with shorter projects which keep the customer on top. There is a need to learn to manage unknowns until they are known. There is also a need for speed in project management methodologies. CIOs must adapt their IT project management methodologies while still limiting risks and taking care of business problems.