Category: Root

Scrum master vs Product owner

Both are Scrum accountabilities, but they focus on different things. Product Owner Scrum Master Focuses on what should be built Focuses on how the team works effectively Maximizes product value Improves Scrum effectiveness Manages and orders the Product Backlog Coaches the team in Scrum and Agile practices Clarifies user stories and acceptance criteria Facilitates events …

Continue reading

Scrum versus Kanban at scale

Yes—basic Scrum is primarily a team-level framework. Scrum Scrum explains how one cross-functional team manages work through: Scrum itself gives only limited detail about coordinating many teams. Multiple Scrum teams can work on the same product, but they normally need additional coordination arrangements, such as: Kanban Kanban can be used at several levels: For example, …

Continue reading

LPM — Lean Portfolio Management

LPM — Lean Portfolio Management Lean Portfolio Management is the SAFe approach for connecting an organization’s strategy and funding to the work performed by value streams and Agile Release Trains. Team level asks: What stories should we complete?ART level asks: What features should the teams deliver during the PI?Portfolio level asks: Which major initiatives should …

Continue reading

Story points: Fibonacci, Poker, Agile

Story points Story points estimate the relative size of a user story. They consider: Story points do not directly mean hours or days. A 5-point story is expected to be larger or more uncertain than a 3-point story, but it does not necessarily take exactly five hours or five days. Fibonacci scale use the Fibonacci-style …

Continue reading

How to Prioritize all the stories using MoSCoW

• Prioritize all the stories using MoSCoW You assign every user story one of four MoSCoW priorities and then arrange the Jira backlog from highest to lowest priority. Priority Meaning Guiding question Must Have Essential for the feature or first usable release Will the feature fail or become unusable without this story? Should Have Important, …

Continue reading

ValidateNotNullOrEmpty

[ValidateNotNullOrEmpty()] is a PowerShell parameter-validation attribute. It rejects values that are: Example: Valid call: Output: Invalid empty value: Invalid null value: Why combine it with Mandatory? requires the parameter to be supplied. requires the supplied value to contain something. They are commonly used together: Array example Call: Important limitation A string containing only spaces is …

Continue reading

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