Definition of Ready in Scrum

Definition of Ready in Scrum

The Definition of Ready is a set of agreements that lets everyone know when something is ready to begin, e.g., when a user story is ready to be taken into a sprint, or when all necessary conditions are right for a team to start a sprint. An appropriate definition of ready will substantially improve the Scrum team’s chance of successfully meeting its sprint goal.

Continue reading
Transparency in Scrum

Transparency in Scrum

Transparency is the first important aspect of the Scrum process and must be visible to those responsible for the outcome. Transparency requires that these aspects be defined in their daily activities and artifacts so that teams can share a common understanding of what they see.

Continue reading
Develop DFD with Stepwise Refinement

Develop DFD with Stepwise Refinement

One of the effective way to solve a complex problem is to break it down into simpler sub-problems. You start by breaking down the whole task into simpler parts. Step-by-step refinement is essentially a decomposition of the system to gain insight into the subsystems that make up the system, known as the top-down decomposition method.

Continue reading
Scatter Diagram Tutorial

Scatter Diagram Tutorial

A Scatter Plot (also known as a scatter Chart, and Correlation Plot) is a tool for analyzing the relationship between two variables, used to determine the degree of correlation between two variables. One variable is plotted on the horizontal axis and the other on the vertical axis. The pattern of their intersection points graphically displays the relational pattern. It is one of the Seven Basic Tools of Quality.

Continue reading
Fault Tree Diagram Tutorial

Fault Tree Diagram Tutorial

Fault tree analysis (FTA) is a top-down deductive fault analysis in which Boolean logic is used in conjunction with a series of low-level events to analyze the unexpected states of the system. This analysis method is primarily used in safety engineering and reliability engineering to understand how systems fail, determine the best way to reduce risk, and determine (or feel) the event rate of safety incidents or specific system-level (functional) failures.

Continue reading