Category: Root

Write-Error

Write-Error in PowerShell Write-Error writes an error message to PowerShell’s error stream. By default, it creates a non-terminating error. That means PowerShell displays the error, but usually continues with the next command. Typical result: Make it terminating Use: Example: Now the error stops normal execution. Use with try/catch Possible output: Without -ErrorAction Stop, the catch …

Continue reading

Terminating error vs non-terminating error

Terminating error vs non-terminating error in PowerShell Non-terminating error A non-terminating error reports a problem but allows PowerShell to continue running the remaining commands. Example: Possible output: The file-reading command failed, but PowerShell still ran the next line. Common examples include: By default, many PowerShell cmdlets generate non-terminating errors. Terminating error A terminating error stops …

Continue reading

Was quality truly built in???

Answer: Probably no — quality was not truly built in. The team may have done some testing, but the result shows that quality was not built into the full process. Why? Because: Evidence What it suggests Checkout crashes 40% of the time Critical functionality was not properly tested. Password reset fails Important user flow was …

Continue reading

Kanban: flow over overload.

“Flow over overload” means: In Kanban, the goal is to keep work moving smoothly through the system, instead of loading the team with too many tasks at the same time. Your Kanban slide explains that WIP limits prevent overloading and help identify bottlenecks early. Simple explanation Bad approach: overload Better approach: flow Start many tasks …

Continue reading

Self-healing tests, Automation adapts when locators change.

Self-healing tests means: Automated test scripts can adjust themselves when small changes happen in the application, especially in the UI. What does “locator” mean? In test automation, a locator is how the test finds an element on the screen. Example: The automation tool needs to find the Login button using something like: or or What …

Continue reading

Debrief?? One group shares one strong DoD item.??

Yes. Debrief means the short discussion after the activity. After students finish the RCA/Fishbone/Five Whys activity, you ask them to share what they found. Meaning of this line One group shares one strong DoD item It means: Each group should give one good Definition of Done checklist item that could prevent this problem from happening …

Continue reading

how fishbone helps to find root cause

Fishbone helps find the root cause by organizing possible causes into categories, so the team does not jump to one quick answer or blame one person too early. It is a visual RCA tool used to identify possible causes of a problem. Simple explanation for students “Fishbone does not automatically give the root cause. It …

Continue reading

Fishbone

Yes. Fishbone Analysis should usually be shown as a diagram, because it is a visual Root Cause Analysis tool. It is also called an Ishikawa Diagram or Cause-and-Effect Diagram. Your slide defines it as a visual tool for identifying possible causes of a specific problem. Simple Fishbone Diagram Example Problem: Checkout crashes 40% of the …

Continue reading

pull system

Pull system in Kanban means: Work is started only when the next person or stage has capacity. It is the opposite of a push system, where managers or upstream teams keep assigning work even when people are already overloaded. Simple explanation System Meaning Problem / Benefit Push system Work is pushed to people whether they …

Continue reading

kanban? Where would you set the limit: In Progress or Review??

In Kanban, you can set WIP limits on both: In Progress and Review They should have separate limits, because they control different types of work. Your slide says WIP limits are the maximum number of items allowed in each workflow stage, used to prevent overload and identify bottlenecks early. Simple board example Column Should it …

Continue reading