Category: Agile
-
Team Coaching Techniques for Scrum Masters
Scrum Master serves as a coach for the team. Coaching is a critical skill for a Scrum Master because it aligns with the core principles of the Scrum framework and Agile principles. Here are some coaching techniques Scrum Masters can adopt at the team level to begin with: Coaching at the team level involves a… Read more
-
Bored of same retrospective format, try this for a change
Retrospectives are a crucial part of Agile development process, providing teams with a structured way to reflect on their processes and make improvements. Here are few retrospective techniques that teams can use for a change ESVP (Explorers, Shoppers, Vacationers, Prisoners): Team members categorize themselves as explorers (eager for change), shoppers (open to change but not… Read more
-
Scrum Master and Product Owner collaboration
As there is a growing trend of developers and Engineering managers playing Scrum Master role, I am writing this blog to emphasise the collaboration between the Product Owner (PO) and Scrum Master (SM), as it ensures that the Agile principles are effectively applied and the Scrum framework operates optimally. Here’s why this collaboration is crucial:… Read more
-
Product backlog for requirement management
The Product Backlog plays a pivotal role in requirement management within Agile ways of working, particularly in Scrum. It serves as a dynamic, evolving, and prioritised list of features, user stories, and tasks that define the requirements for a software product. Here’s how the Product Backlog contributes to requirement management: In summary, the Product Backlog… Read more
-
Some tips to become better with User Stories
What are User Stories User stories are concise descriptions of software features from the user’s perspective, typically following the format: “As a [user], I want [action] so that [benefit].” User stories originated as part of Extreme Programming (XP) in the late 1990s. Kent Beck, one of the founders of XP, introduced the concept, and Mike… Read more
-
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… Read more
-
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… Read more