Value Stream Mapping Tutorial

Value Stream Mapping Tutorial

Looking for a VSM software? Our value stream mapping software makes creating professional value stream mapping easy and fast. The value stream mapping tool comes with a rich set of value stream mapping symbols. Combined with a drag-and-drop VSM editor and a powerful feature set, you can easily create professional value stream mapping.

Continue reading
Fishbone Diagram — How to Draw?

Fishbone Diagram — How to Draw?

A fishbone diagram (also known as a cause and effect diagram or Ishikawa diagram) visually shows multiple causes of a problem. It helps identify stakeholder ideas about the cause of an issue and allows users to immediately categorize ideas into themes for analysis or further data collection. It can be used in conjunction with the “Five Whys” technique.

Continue reading
Use Case — Learn By Examples

Use Case — Learn By Examples

A use case describes how a user uses a system to accomplish a specific goal. A use case diagram consists of a system, related use cases, and actors, and relates them to each other in order to visualize: what is being described? (the system), who is using the system? (actor) and what the actor wants to achieve? (use case), so that use cases help ensure that the right system is developed by capturing the requirements from the user’s perspective.

Continue reading
BPMN —Quick Guide

BPMN —Quick Guide

The Business Process Management Initiative (BPMI) has developed a standard Business Process Modeling Notation (BPMN). The BPMN 1.0 specification was released to the public in May 2004. The specification represents more than two years of work by the BPMI Notation Working Group. In February 2006, the OMG released a BPMN specification document. Version 2.0 of BPMN was developed in 2010 and the actual version of the specification was released in December 2013.

Continue reading
Project Management — What is a Project?

Project Management — What is a Project?

Modern and effective project management techniques require skills that allow the seamless integration of best practice tools with good leadership and team management within an organization for improving the likelihood of success of time-limited initiatives. These practices include establishing clear accountabilities, defining objectives and outcomes, establishing the scope, planning, monitoring, and reporting controls for project activities.

Continue reading
Scrum: Why Sprint Length should be Short?

Scrum: Why Sprint Length should be Short?

Sprinting is running over a short distance in a limited period of time. It is used in many sports that incorporate running, typically as a way of quickly reaching a target or goal, or avoiding or catching an opponent. A sprint is a time box. Each sprint has a start and end date during which a set of selected user stories have to be completed and confirmed. The following image shows you the key elements of a sprint, which includes a set of user stories, the scrum members involved, the assignment of work, the duration and end date (top-right corner).

Continue reading