I just got off a demo with a BA who commented "they could care less about what happen's in development", they just needed to generate the requirements doc and move on. I thought to myself the chances of that project ending in success is unlikely.
BA's and developers have to work together if projects are to be successful. The simulation tool appears to be touted for BA's only and that is a mistake. Yes, communication between the end customer and BA is vital but the BA to developer communication is just as vital if the project is to be delivered with success.
Generally speaking, the situation is BA's prefer tools enabling them to visually create screen's or visual's to supplement the documentation that is sent to development. Developer's prefer tools where they can code and can have "unlimited" behavior since they do not want to be constrained to the tool environment.
Now in order to truly achieve this communication, especially with remote teams & customers, the tool must support web based interaction. Forcing users to email files, having to install software to view something and an inability to capture timely feedback are "features" you should avoid in this market.
Simunicator is focused on providing a communication medium for technical and non-technical people on the project team, not just one functional group. Our latest version with a new visual flow logic editor, enhanced screen editor and improved Use Case/Requirements reports were added for non-technies, and with enhanced coding support for techies to "click to code mode" to create not just high fidelity, but real fidelity protoypes and simulations.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment