A Scrum board and a Kanban board may look similar, but they manage work differently. Area Scrum board Kanban board Work cycle Work is organized into fixed-length sprints Work moves continuously Board scope Usually shows work selected for the current sprint Shows the ongoing workflow Planning Sprint Planning selects work before the sprint begins Work …
Category: Root
Jul 12
throughput is it used in scrum as a metric or only for kanban
Throughput can be used in Scrum too. It is not only for Kanban. However: Throughput is more strongly associated with Kanban and flow-based systems.Velocity is more commonly used in Scrum. In Kanban Throughput means: Number of work items completed during a period, such as 12 tickets per week. Because Kanban uses continuous flow, throughput may …
Jul 12
Kanban: Flow metrics
Flow metrics measure how smoothly and quickly work moves through a workflow, especially in Kanban. Metric Definition Example Lead time Total time from when work is requested until it is delivered. Request Monday, delivered Friday = 5 days Cycle time Time from when active work starts until it is completed. Work starts Wednesday, done Friday …
Jul 08
Explain: Agile Quality: • Cross-functional ownership
Agile Quality: Cross-functional ownership means: Quality is everyone’s responsibility, not only the QA/tester’s responsibility. In Agile, the whole team works together to build quality into the product: developers, testers, Product Owner, Scrum Master, UX/design, business analyst, and sometimes DevOps/security. Your Week 7 slide contrasts this with traditional quality, where QA is often separated after development. …
Jul 08
Explain: Traditional Quality:
Traditional quality means quality is often checked after most of the development work is already completed. It follows a pattern like: Plan → Build → Test → Fix → Release Your Week 7 quality slide contrasts this with Agile quality, where testing and quality practices are moved earlier and shared by the whole team. 1. …
Jul 08
Explain: Dashboard: Team: Sprint progress, quality, blockers, health
This is a team-level dashboard. It answers: How is the team doing right now, and what should we act on today or this sprint? 1. Sprint progress This shows whether the team is on track to complete the sprint goal. Question Example metric Are we on track? Sprint burndown How much work is left? Remaining …
Jul 08
Explain: Dashboard: Feature progress, dependencies, predictability
This is usually a program manager / product manager / ART-level dashboard idea. It answers: Are features moving forward, are cross-team dependencies under control, and can we predict delivery with confidence? 1. Feature progress This shows how much work has been completed for major features. Example questions: Question Example dashboard metric Which features are started? …
Jul 08
Explain: Dashboard: Executive: Portfolio health, outcomes, risk, budget
Executive dashboard means a high-level dashboard for senior leaders, not for daily team work. It should answer: Are our major initiatives healthy, delivering outcomes, within risk tolerance, and within budget? 1. Portfolio health This shows whether the organization’s major projects/programs are generally on track. Examples: Portfolio health question Example metric Are major projects on track? …
Jul 08
Define: CSAT, NPS, CES
CSAT — Customer Satisfaction Score CSAT measures how satisfied customers are with a specific product, feature, service, or interaction. Usually the customer is asked: “How satisfied were you with this experience?” Common scale: 1 to 51 = very dissatisfied5 = very satisfied Example: After using a new checkout feature, customers rate it 4.5 out of …
Jul 08
define static analysis: Tools detect bugs, vulnerabilities, code smells.
Static analysis means: Using automated tools to examine source code without running the program. These tools scan the code and detect possible problems such as: Static analysis checks Meaning Example Bugs Logic or coding mistakes that may cause failure Null pointer issue, unreachable code Vulnerabilities Security weaknesses SQL injection risk, hardcoded password Code smells Code …
