Category: Agile | এজাইল

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. …

Continue reading

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. …

Continue reading

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 …

Continue reading

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? …

Continue reading

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? …

Continue reading

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 …

Continue reading

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 …

Continue reading

Code quality metrics help the team judge whether the code is easy to understand, safe to change, reliable, efficient, and not creating future problems. Your Agile metrics slides describe code quality as how well-written, maintainable, and defect-free the codebase is, including readability, consistency, efficiency, standards, and technical debt reduction. Code quality area Meaning Example Maintainability …

Continue reading

For a customer, the most useful number is usually: Lead Time Because lead time measures the customer’s waiting time. Simple comparison Metric Who cares most? Why Lead Time Customer “How long from my request until I get the result?” Cycle Time Team / manager “How long did the team actively work on it?” Throughput Team …

Continue reading

For a Sprint Burndown Chart, the x-axis is usually the days inside the sprint. Sprint burndown Axis Meaning X-axis Days of the sprint Y-axis Remaining work Example: Day Remaining work Day 1 100 points Day 2 85 points Day 3 70 points Day 4 50 points Day 5 25 points Day 6 0 points So …

Continue reading