Blogs/Articles
-
Scrum role to Accountability – What does this change mean
The shift from “Scrum roles” to “Scrum accountabilities” reflects a change in how Scrum is defined and understood, emphasizing a more flexible and adaptive approach to the framework. This shift is not a formal change in Scrum itself but a shift in how it is talked about and implemented. Here are some reasons behind this…
-
Know the Agile Manifesto
History The Agile Manifesto emerged in February 2001 when a group of 17 software development experts met in Snowbird, Utah, to address the challenges of traditional, heavily planned software development methodologies. Frustrated with inflexible processes and documentation-heavy approaches, they sought a more adaptive and customer-focused approach. This meeting led to the creation of the Agile…
-
Scrum and Agile
The Agile Manifesto values and the Scrum framework are closely connected, as Scrum is an Agile framework that aligns with these values: Scrum, a popular Agile framework, operates within the Agile Manifesto’s principles and values, making it a powerful methodology for iterative and customer-centric software development. It helps teams apply these values in practice while…
-
Anti Patterns that Scrum Masters should avoid
Scrum Master anti-patterns are behaviors or practices that are counterproductive to the effective functioning of a Scrum Master. They hinder the successful implementation of the Scrum framework and its principles. Some common Scrum Master anti-patterns include: Recognizing and addressing these anti-patterns is essential for Scrum Masters to fulfill their role effectively and help teams achieve…
-
Anti Patterns that Product Owners should avoid
Product Owner anti-patterns are detrimental behaviors or practices that hinder the effective performance of a Product Owner in Agile product development. Common anti-patterns include: These anti-patterns can impede product development, communication, and team collaboration. Recognising and addressing them is crucial for a Product Owner to fulfill their role successfully and deliver valuable products.
-
Anti Patterns that Scrum Developers should avoid
Scrum Developer anti-patterns are counterproductive behaviors or practices that can hinder the effectiveness of development teams in Scrum. Common Scrum Developer anti-patterns include: Identifying and addressing these anti-patterns is essential for Scrum Developers to work cohesively and deliver valuable, high-quality software in the Scrum framework.
-
Manager as a Scrum Master
When a manager takes on the role of a Scrum Master, it can be both challenging and beneficial. To become an effective Manager-Scrum Master, consider the following best practices, things to avoid, and steps to improve your effectiveness: Best Practices: Things to Avoid: Becoming Effective: Balancing the roles of manager and Scrum Master requires a…
-
Developer as a Scrum Master
A developer taking on the role of a Scrum Master can be both challenging and beneficial. Here are some considerations and tips for a developer acting as a Scrum Master: Benefits: Challenges: Tips for Success: While it’s possible for a developer to serve as a Scrum Master, it’s important to strike a balance between the…