Gradle 2.5 has been announced this month including a number of incubating features, such as Continuous Builds, Dependency Substitution Rules, Progress Events, Google Tests, and others.
InfoQ interviewed Jeff Sutherland about the problems that larger organizations have when adopting Scrum, how they can increase their capability for handling impediments, improving agile leadership, what Scrum masters can do to help teams to become agile, and his advice to managers when their organization is implementing Scrum.
In 2009 the Scrum Alliance registered a trademark application to register the term "Scrum User Group" as a protected trademark. Ken Schwaber, one of the original founders of the Scrum Alliance, has written a blog in which he objects strenuously to this move, and has asked for the community to respond to the move, with the possibility of filing an expensive legal challenge.
For an organization to be data-driven, it's not enough to just dump mountains of data. That data needs to be accurate and meaningful. Julianna Göbölös-Szabó, data engineer at Prezi shared how they improved the quality of its log data. Their solution involved moving from unstructured to structured data with a lightweight, contract-based approach to nudge all teams in the right direction.
Karen describes her way of creating a happy work environment.
Even with best intentions it can be challenging for people to follow up on actions that they agreed to do. They can start to doubt if they can do the actions and become afraid to fail. Several authors have recognized this and came up with suggestions for dealing with it and making change happen.
Jessie Frazzelle, member of Docker's core team, is responsible for Docker's testing infrastructure. Frazzelle described Docker's build workflows for both the master branch and pull requests as well as the various tools that are part of the testing infrastructure. Jenkins, Consul and nsq are all key components of the testing infrastructure, working together with Docker's custom tools.
The Scrum Alliance recently appointed a new Chief Executive Officer. Manuel (Manny) Gonzalez was appointed to the role after an extensive global search. InfoQ spoke to Manny about his background and his vision for the Scrum Alliance.
Tomas Rybing shared the concept of the customized kanban board named ‘Arrow’. The Arrow is based on the priority pyramids approach. Arrow is a visualization of the backlog combined with the kanban board that visualizes the work process.
The state of testing 2015 report shares results from this year's testing survey that was organized by Joel Montvelisky from PractiTest and Lalit Bhamare from Tea-Time with Testers. It provides insights in the adoption of test techniques and practices, test automation, and the challenges that testers are facing. InfoQ did an interview with the organizers of the survey.
Fred George talked about the Challenges in Implementing MicroServices and The Secret Assumption of Agile at the GOTO Amsterdam 2015 conference. InfoQ interviewed him about how make microservices as small as possible, challenges when implementing microservices and how to deal with them, why programming style matters, and what developers can do to develop their code writing skills.
Joe Mcgrath, scrum master and coach in his latest blog explained the Lego Flow Game.
An interview with Ivan Kusalic, Software/DevOps engineer at Nokia HERE in Berlin, about why they decided to apply DevOps, how DevOps has changed their way of working, which benefits they are getting, and the challenges that they had and how they dealt with them when development and operations became one team. Kusalic also gives some advice for applying DevOps with teams.
Scrum is a simple and lightweight methodology therefore, scrum alone is not enough.
James Shore presented a workshop at Agile Australia titled “Bringing Fluency to your Agile teams: Coaching for Best-Fit Agile”. The focus of the workshop was the use of the Agile Fluency model, which he and Diana Larsen have developed, as a tool for coaches to use when choosing the approach to working with teams based on their level of fluency with the agile values, principles and practices