What is Case Management Model and Notation (CMMN)

What is Case Management Model and Notation (CMMN)

CMMN is a graphical notation used for capturing work methods that are based on the handling of cases requiring various activities that may be performed in an unpredictable order in response to evolving situations. Using an event-centered approach and the concept of a case file, CMMN expands the boundaries of what can be modeled with BPMN, including less structured work efforts and those driven by knowledge workers. Using a combination of BPMN and CMMN allows users to cover a much broader spectrum of work methods.

Continue reading
How to Perform Gap Analysis with BPMN?

How to Perform Gap Analysis with BPMN?

Gap analysis involves the comparison of actual performance with potential performance. For example, a company does not make the best use of current resources, it may perform below an idealized potential. In other words, gap analysis is the process people use to examine their current state (or as-is process) with their desired state (to-be process) of a company. It typically is used to determine if the company is meeting expectations and effectively using resources that measure time, money and labor. The management team can then create an action plan to move the organization forward and close the performance gap.

Continue reading
Cross-Functional Flowchart – with Templates and examples

Cross-Functional Flowchart – with Templates and examples

Cross functional flow charts show who did what and when in swimlane or grid charts. These charts are organized into multiple parts to provide additional dimensions by assigning each process step to a category. In other words, you can use a cross functional flowchart to describe the relationship between the steps in the process and the department or functional area responsible for those steps.

Continue reading
Writing Good User Stories

Writing Good User Stories

User stories are part of the agile approach and help shift the focus from writing requirements to discussing them. All agile user stories include one or two written sentences and, more importantly, a series of conversations about the desired functionality.

Continue reading
Agile Estimation: Relative estimates vs Absolute estimates

Agile Estimation: Relative estimates vs Absolute estimates

Whether a team is developing a product or a project, we need to answer the question “When will we be able to finish it?” , or how far we will be able to go at a certain point in time, so as with traditional development models, we need to estimate the workload before we start the project. Agile estimation is the process of estimating the effort required to complete a priority task in the product backlog. This effort is usually measured in terms of the time required to complete that task, which in turn leads to accurate sprint planning.

Continue reading
The seven most popular agile development methods

The seven most popular agile development methods

When the Agile Manifesto was created, there were quite a few “lightweight” development processes; Other such methods have since emerged. They are now collectively referred to as “agile” methods. Since the birth of the Agile Manifesto in 2001, there has much buzz around being agile. The Agile approach is just a way of thinking that enables teams and organizations to innovate, quickly respond to changing demand, while mitigating risk. Organizations can be agile using many of the available frameworks available such as Scrum, Kanban, Lean, XP, etc…

Continue reading