Methodologies

Defining Acceptable Response Times When customers reach out for support, having clear expectations set on response times is key to providing a good customer experience. To define appropriate response time targets, companies should start by analyzing current support traffic – what are the most common issues customers face? How complex are they to troubleshoot and…

Defining the Roles and Responsibilities The Scrum Master and Product Owner play critical roles within an Agile software development team. The Scrum Master focuses on coaching the team and optimizing process while the Product Owner is responsible for maximizing business value. Despite having a common goal of delivering value to customers, tensions can arise due…

Understanding Technical Debt Technical debt refers to the implied cost of additional rework caused by choosing an easy software solution now instead of using a better approach that would take longer. It is a design or technical infrastructure issue that is expedient in the short term but sets up a technical context that can make…

In Scrum, all work related to a project must be accounted for and tracked transparently. This includes product backlog items, bugs, technical tasks,assignments, progress reporting, and closures. Comprehensive tracking ensures visibility into the true state of a project and what work remains. Defining Work Items in Scrum Scrum teams track progress by breaking down work…

Communicating Value of Iterative Development The iterative approach of agile development provides value to stakeholders through continuous delivery of working software. Rather than work for long periods to deliver functionality at the end of long development cycles, agile teams embrace building software incrementally in short iterations. This allows features to be delivered frequently, often every…