Identifying and designing process-driven applications is both an art and a science. Many times you will know which departments could benefit most when pursuing an incremental adoption of K2 blackpearl. Other times you will need to take a look at your company's organizational entities, how they interact with each other, and which ones are the most process-based already.
Take a minute to think about a process in your company. Keep that process in mind as you read this chapter. When you are finished reading, write down the major pieces of the process and ask yourself some of the questions included at the end of this chapter. Does your process fit some or most of the criteria of a good process for automation?
Also keep in mind that the methodologies and project roles identified in this chapter are meant for an organization that has a relatively mature Business Process Management (BPM) initiative in place. While you can strive toward this "ideal" environment, don't let a few missing pieces discourage you from designing your first process-driven application. Many times the first few applications that you build will be a great learning experience and can help you identify what you realistically need to build your next process-driven application.
This chapter covers the following topics:
Evaluating potential processes for automation
Running a process-driven application project, including methodologies, time estimation, and project roles ...