Articles, Blog Posts, Books and Quotes on Agile Project Management
As many testers have, I struggled in my first year on a Scrum team. How do I write tests without a spec? How do I know when I am done with software testing when there is no test plan? I present this article to show the important contributions that software testers on Scrum teams can make in the phase of feature and user stories creation.
Technical debt due to bad code quality is one the problem that every Scrum development team might face in their application. In this blog post, Henrik Kniberg discusses the causes of technical debt and provides some hints on how to manage it.
Velocity can be defined as a measurement of how much the Scrum team can get done in a Sprint, based on past results. In this article, Beth Macy discusses how reliable is velocity and how you can use it.
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?”.