13 questions you should ask your client during BPM Requirements meeting
For workflow based projects Business requirements discussions normally span across multiple meetings where you ask more and more about Client's AS-IS and TO-BE processes. Some questions could help you determine if the chosen BPMS can achieve expected functionality. Given below are some questions that can help you get what you are looking for:
1. What is the process and what does it achieve?
This question will help you get introduces to the process. Asking what it achieves will help you get the reason why this process exists. It will also help you understand how critical is this process for business.
2. How does the current process (AS-IS) work?
This will be more detailed analysis possibly accompanied with a flowchart. If one does not exist, this is a good time to pick up a pen and start drawing.
3. Who are the participants in the process and what are their roles?
This will get you the roles and responsibilities. This will also help you in assigning performers to various steps. Also find out how would you find out (logically) who are the people who will be in this role. Most probably client will have LDAP or some other System from where you can lookup. There is also a possibility that you might need to lookup some other application or maintain the rules with you.
4. Which business units participate in the process?
This will help you understand who all will be the stakeholders and how complex it will be to design the process. The general rule is that if there are more units, the more complex the process will be and the more effort you (and client project team) will spend bringing everyone to a common accepted stage.
5. What will be the TO-BE Processes?
Now you start asking questions about what needs to be built. Ask them what they envision as the ideal process and then start drilling into finer details.
6. How does the process start and end?
This is very important. Sometimes you will realise that people are not sure how the process should end. They know just their part of the process. Also, make sure you ask the question whether the process can be reopened. This is essential because not all BPMS allow this.
7. What information flows from one person to another?
This will help you determine what the screen and data fields should be. Sometimes you could be dealing with complex sets of data. Do ask questions. If the data needs to be pulled from somewhere, do ask about the integration capabilities of that system or try to get a contact who can give you that details.
8. Which systems will this process interact with?
Find out what level of integrations are you looking for. Most of the business process will be integrated with some or the other systems. Sometimes integrations could lead to complex processes, screens and routing.
9. Are there any business rules associated with the process?
Ask what business rules are there. Also ask how often do they change. This will help you determine if rules should be embedded into the process or put in as a separate component.
10. What are your reporting requirements?
Your data layouts, your process routing could depend upon what reporting requirements are there. If user needs reports business unit wise or region wise, you will need to incorporate those fields into your workflow.
11. What existing forms/reports and documents do you have?
Get all the documents you can. This will help you in the overall project implementation.
12. What are your implementation timelines and constraints?
Determine what are the timelines and constraints (if any). Its possible that the client asks you the question “when can I have this?”. Be sure you keep it open. Unless your implementation team has analyzed everything do not give an estimate. Determine what constraints client has and figure out how the project can still go through.