Blogs/Articles
-
Product Owner and Daily Scrum
The Product Owner (PO) in the Scrum framework has a vital role to play, but their involvement in the Daily Scrum should be carefully considered to avoid potential conflicts of interest and to maintain the meeting’s purpose. Let’s delve into the role of the Product Owner in the Daily Scrum, the conflicts that may arise,…
-
Kanban for Software Development – Blog for Beginners
Kanban for Software Development is an agile and lean methodology that helps software development teams manage and optimize their workflow. It is inspired by the Kanban system originally developed by Toyota for manufacturing and was adapted for knowledge work, including software development. Here’s a detailed overview: History of Kanban: Kanban Practices: Kanban Principles: Benefits of…
-
Doing Agile vs Being Agile
Doing Agile and Being Agile represent two distinct approaches to Agile methodologies, and both are important in achieving the full benefits of Agile practices: Importance of Both: Consequences of Imbalance: Responsibility for Adherence: Benefits to the Company: To fully realize these benefits, organizations should strike a balance between Doing Agile by implementing the processes and…
-
Understanding Definition of Ready
Definition of Ready (DoR) is a concept in agile development that outlines the criteria that a user story or backlog item must meet before it is ready to be taken into a sprint for development. It sets the expectations for the completeness and clarity of requirements and ensures that the team can effectively and efficiently…
-
Definition of Done – What, Why and How
Definition of Done (DoD) is a crucial concept in agile development that defines the criteria a product increment must meet to be considered complete and potentially releasable. It ensures that work items, such as user stories or tasks, have been thoroughly completed and meet the team’s quality and acceptance standards. Here’s a breakdown of the…
-
When a Sprint Backlog item is not “Done”
When sprint backlog items are not completed within the designated sprint, it’s important to follow a structured approach to address these unfinished tasks. Here’s what to do with sprint backlog items that are not done: In the agile, incomplete sprint backlog items are not considered “failures.” They are opportunities to learn, adapt, and continuously improve…
-
Estimate for better Sprint outcomes
Estimation in the context of agile development typically falls into two broad categories: Size Estimation and Effort Estimation. Each category has its own methods and techniques for facilitating, and specific prerequisites and success criteria. Size Estimation: Size estimation focuses on quantifying the relative size or complexity of items in the product backlog. This helps teams…
-
Choose from this 10 Product Backlog prioritisation techniques
Prioritizing the product backlog is a critical activity in agile development, ensuring that the most valuable and important items are worked on first. Here are ten prioritization techniques, along with explanations, facilitation processes, prerequisites, benefits, and considerations for each: The choice of prioritization technique depends on the specific needs of the project, the availability of…
-
Types of TDD
Test-Driven Development (TDD) is a software development practice that involves writing tests before writing the actual code. It helps ensure that the code meets the specified requirements and functions correctly. There are several types of TDD, and the implementation requires a specific mindset: Mindset Needed to Implement TDD: TDD is not just a technical practice;…
-
On-Site Customer
An On-Site Customer is a practice in agile software development where a customer representative works closely with the development team on-site, providing real-time feedback, clarifying requirements, and making decisions. This practice is often associated with extreme programming (XP) and other agile methodologies. Explanation: An on-site customer is physically present at the development location, allowing for…