Lars Olufsen
New Member
Many RPA development tasks are different from traditional IT development, in that it doesn't change any systems, but mere automates the manual processes between existing interfaces. This usually (definitely in our case) allows the RPA developers to use less restrictive development methods, and even makes it possible to some extent, to allow business process specialists to "model" or develop the automated processes.
We try to help them by providing templates for all the needed documentation and a "shell" for development of new robots, but we lack a proper tool to manage the actual development proces, from ideation over process description to development iterations, testing, logging, SLA's and sign off of allsorts of relevant issues, such as GDPR etc. through a simple user interface that doesn't confuse the users with a gazillion artefacts that aren't relevant for their process.
Have any of you found a suitable tool for managing robotics development?
It's a 30-minute development job in a tool like Lotus Notes, but sadly that is not available to me (and no, Sharepoint is not a viable alternative). :-/
We try to help them by providing templates for all the needed documentation and a "shell" for development of new robots, but we lack a proper tool to manage the actual development proces, from ideation over process description to development iterations, testing, logging, SLA's and sign off of allsorts of relevant issues, such as GDPR etc. through a simple user interface that doesn't confuse the users with a gazillion artefacts that aren't relevant for their process.
Have any of you found a suitable tool for managing robotics development?
It's a 30-minute development job in a tool like Lotus Notes, but sadly that is not available to me (and no, Sharepoint is not a viable alternative). :-/