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 …
Category: Agile | এজাইল
Agile | এজাইল
Jul 14
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, …
Jul 14
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 …
Jul 14
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 …
Jul 13
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, …
Jul 12
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 …
Jul 12
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 …
Jul 12
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 …
Jul 12
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 …
Jul 12
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 …
