A naukri.com initiative
Scrum
1d
34
Image Credit: Scrum
What a Waste!
- Applying leadership concepts for simple and predictable environments to an Agile environment can create inefficiencies and waste
- The idea of maximizing utilization of people and resources backfires in an Agile environment, where flexibility and cross-skilling is of utmost importance
- Velocity is a measure of how much work can be delivered per Sprint and is used for planning purposes only
- Velocity is specific to a team and cannot be compared between two Scrum teams, because different teams assign different point values based on their complexity, skill levels and goals
- Sign-off requirements, used as controls to limit changes, creates tension and delays. Instead, Agile teams must be nimble, adaptable and prioritize the outcomes over rigid processes and metrics
- Agile empowers Product Owners as a single authority for their Product Backlog by enabling swift adjustments that keep the team aligned with delivering the most value
- In Agile environments, success depends on adaptability, prioritization, and focusing on outcomes rather than outdated metrics or rigid processes
- Agile leaders who want to learn more about Scrum can signup for Rebel Scrum's upcoming Applying Professional Scrum course
- Agile leaders who want to signup for Professional Agile Leadership class can learn more about it
- By rethinking traditional concepts like utilization, velocity, and sign-offs, organizations can avoid waste and fully realize the value of Agile
Read Full Article
2 Likes
For uninterrupted reading, download the app