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.
How do effective Agile and Scrum leaders act? Agile advice often mentions abstract concepts, like allow the team to self-organise, without illustrating what a leader should do if this doesn’t happen or things go wrong.
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.
The patterns and anti-patterns of human system design sound familiar. This presentation discusses a few of them, including: Good/Bad UX, Enlightening/Confounding Data, Robust/Weak Architecture.
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.