RPA Project Documentation in small team

I work in a small RPA team (2 developers and 3 BA, most people participate in RPA projects part time) and we try to find out how to document our robots.
Since we don’t have separate Robot architect role, this task is a developer responsibility.
In our opinion, with this division of roles in the team, there is no need to create as many as 3 robot project documents (PDD, SDD, DSD).
We are planning to reduce it to two - one PDD prepared by BA, describing process as-is and how it should look like after automation.
Second document, written by developer would describe robot architecture, technical issues and implementation detail.
What is your experience and the standard used when working in a small team. Do you use templates provided by UiPath, adapt them to your requirements, or have you created templates from scratch?

Hi @MaciejSartys,

The level of documentation depends on who is your customer. Internal or external.

Internal - I have a 1-slide template before the PDD.

Problem description, extent of the problem, desired outcome, projected capabilities, title of automation, department and area of work. The BA should fill the 1-slide template with functional user.

The key idea is being able to articulate the problem concisely within 1-slide. If unable to do so, could meant the problem is unclear or don’t know the problem well enough to solve it.

PDD… user needs the bot, don’t care about the document. Can the user some time together with the developer ?

The second document is not required - technicalities should be addressed already by BA to determine if automation is feasible in the first place.

External - provide as little documentation as mandatory and spend more time with functional user - requirements, bot building and acceptance.

With a small team, the BA and developer should rotate roles. Focus on what really matters to customer.