Technical Debt is defined as the eventual consequences of poor or evolving software architecture and software development within a codebase. Sometimes you have to pay it if you want that you can continue to maintain your application. But sometimes it is better to leave the situation unchanged as Ken Rubin wrote in his book.
Scrum requires that members of the team collaborate. One of the agile software development practice used to collaborate is pair programming. In his blog post, Erik Brickarp reports his experience when pairing a programmer and a software tester.
The Cumulative Flow Diagram (CFD) provides typical information about status of your Scrum project: how much work is done, ongoing and in backlog, what is the pace of progress, etc. In this blog post, Pawel Brodzinski explains that you can also use the Cumulative Flow Diagram to detect the issues that a Scrum team might face.
Pair Programming is one of the eXtreme programming (XP) original practices. Continuously in surveys about Agile, it is one of the least used Agile practices. In this blog post, Dave Nicolette do an extensive survey of pair programming trying the question: “does pair programming work?”.
When your organization is thinking to adopt Scrum or is just beginning to use it, there are always questions that people will ask about how Scrum really works. As an independent Agile Coach, Roger Brown has collected 85 of them that he has arranged under major topics like people or technology.
This short (and humorous) video presents the 3 most common mistakes and 5 best-practices to improve your Scrum Sprint Retrospective meeting.
Metrics are an important tool when you want to manage something. It is very important to define what you want to measure as this will also impact your project team activity. In this blog post, Bob Boyd proposes 9 metrics for Scrum.
Scrum Expert Copyright © 2009-2024 Martinig & Associates