How do you link the specifications to the flow? Do you design the entire flow and so write the specification in each assignement?
In my organization we usually write the specification in a microsoft word document and create in Pega, whitout any link, but it's very difficult to the developer team to identify in what moment of the process each specification should be developed. What do you suggest to improve our process?
Thanks for the post. I have a suggestion listed below which has been helpful on multiple projects for me in the past. I would also recommend the Business Architect essentials course on the PDN if you have not taken that recently.
Suggestion --> Provide the team a simple Visual Specification Map that tie the specifications to something that is easy and quick for the team to understand. For example, create a visual that shows how the specifications link to the business process, specific business scenarios, user scenarios, major features, etc you are trying to implement. Depending upon your situation you may be able to do this linking and create documentation directly from Pega yourself or with an SA from your team. In other situations, it might be more appropriate to start with a picture in Visio or Powerpoint to help get the team grounded. Referring the team to these types of visuals has been helpful on multiple projects that I have worked on both at the Initiation stage as well as during project execution.
I completely agree with the method David suggested, I have also used the same method. It proved to be the best way out to align specification with process step. Create Visio flow or Powerpoint and do call out for specification. This way you will be attach more than one specification to a flow shape which you will not be able to achieve using Pega flow as each assignment or flow action can have only one specification and due to Agile nature of a project you might have more than specification associated to an assignment.