Category: Scrum
-
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;… Read more
-
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… Read more
-
Collective Code Ownership
Collective Code Ownership is a software development practice that promotes shared responsibility for code among all team members. It emphasizes that every developer is responsible for the quality and maintainability of the codebase, not just the original author of a particular piece of code. Here are techniques to implement collective code ownership, its benefits, and… Read more
-
Small Releases
Small Releases involve delivering software increments that are relatively small in scope but add value to the product. When used in collaboration with Scrum, small releases can enhance development practices and ensure that valuable functionality is delivered consistently throughout the project. Here’s how to use small releases in collaboration with Scrum, its benefits, and considerations:… Read more
-
Continuous Integration
Continuous Integration (CI) is a software development practice where code changes are automatically built, tested, and integrated into a shared repository frequently. When used in collaboration with Scrum, CI enhances development practices and streamlines the integration of new features and bug fixes. Here’s how to use CI in collaboration with Scrum, its benefits, and considerations:… Read more
-
Pair Programming
Pair Programming is an agile software development practice in which two programmers work together at a single computer, with one typing (the “driver”) and the other reviewing the work and providing input (the “observer” or “navigator”). When used in collaboration with Scrum, pair programming can enhance development practices and improve the overall quality of the… Read more
-
Cancelling a Sprint?
Only Product Owner can cancel a sprint – Scrum Guide Circumstances for Canceling a Sprint: A Sprint, once started, is typically not canceled. However, there are exceptional cases where it may be necessary: Sprint cancellations should be rare and considered as a last resort to ensure that the team remains focused on delivering value, and… Read more
-
Delegation of responsibilities – PO
In Scrum, the Product Owner plays a critical role in defining, prioritizing, and ensuring the delivery of valuable product increments. While they have significant responsibilities, there are tasks they can and cannot delegate: Tasks the Product Owner Can Delegate: Tasks the Product Owner Cannot Delegate: Read more
-
Project Manager in Scrum
In Scrum, the traditional role of a project manager undergoes significant transformation. Instead of a project manager, Scrum introduces the concept of a Scrum Master and Product Owner. However, there is still a role for individuals with project management expertise in the Scrum framework. This role typically involves the following: It’s important to note that… Read more
-
Sprint burndown charts – what do they measure
Sprint Burndown Charts are visual tools used in Agile and Scrum to track the progress of work in a sprint (a time-boxed iteration). They plot the amount of work remaining to be completed on the vertical axis and the time on the horizontal axis. As the sprint progresses, the chart is updated automatically to reflect… Read more