Agile software development teams have to assure that the products that they develop have sufficient quality. Management often also expect that they increase their velocity to be able to deliver more functionality faster to their customer. Several authors explored the relationship between quality and velocity and suggested ways to improve both quality and velocity.
Agile teams measure the velocity of their sprints. It helps them to plan and track their progress and provides insight for product owners to plan product releases. Can teams also use velocity data when they want to improve themselves? Several authors have written about velocity and shared their concerns on measuring velocity to improve the productivity of teams.
When defining a business case for adopting agile, the question can arise how you can measure the business value that can be delivered using agile software development.
Brett Slatkin from Google presented a method for visual regression testing at Velocity 2013 in Santa Clara. Perceptual diff compares screenshots of a release's webpages with its previous versions and detects changes at pixel level, filling an important gap in automated testing for Continuous Deployment. An open source version of the software has been setup on github.
Velocity, the measure of work completed by the team divided by the time taken to complete it, is increasingly being used to manage the productivity of a team and as a comparison between teams. Jim Highsmith, Mark Levison, and Scott Ambler discuss the misuse of velocity as a productivity measure.
Thymeleaf is an XML/XHTML/HTML5 template engine that works for web and non-web applications. It's an open source Java library distributed under Apache License 2.0. Thymeleaf is a replacement for JSP and other template engines like Velocity and FreeMarker. It comes in two versions, the Standard dialect and the SpringStandard (Spring MVC 3) dialect.