A Gartner research report from December 2009 predicted that by 2012 “agile development methods will be utilized in 80% of all software development projects”. Let's check if the prediction from Gartner has come true?
Scrum and Pomodoro are blended by Mangus Nord to maximize both team and individual productivity.
Andrew Montalenti on his blog pixelmoneky.org talks about viability of fully distributed teams now and in the future.
Design thinking is about creating vision of the future, not just managing the present. Bill Burnett from Stanford University recently spoke about design thinking and what questions we need to ask to shift from design to design thinking.
Mike Cohn recently suggested that the Daily Standup (or Scrum) is not a status meeting for the Scrum Master, but a forum where team members are synchronising their work. Techniques such as breaking eye contact are helpful for Scrum Masters to fix this anti pattern in their teams.
For years Agile has been encouraging teams to work together collaboratively in open spaces and encouraging developers to pair program, but lately these types of practices have been coming under fire.
Visure Solutions recently announced the availability of IRQA which denotes a solution for requirements definition and management (RDM). A sound process using professional tools is important for ensuring the quality of product and solution development with respect to the requirements specification.
VS11 will provide new tools that expedite unit testing, refactoring, and easier communication across the entire development team. These new components are intended to benefit everyone from developers, and testers to those deploying and maintaining the resulting application.
The latest version of Application Lifecycle Unification tool Tasktop Sync supports repository introspection and REST based application lifecycle artifact management. Tasktop team released last month version 2.0 of the tool. InfoQ spoke with Mik Kersten, CEO of Tasktop, about the new features in the latest release.
Agile practices should foster high-performance self-organizing teams. It is important that high-performance equals value delivery, to ensure that the team solves the right problem. It is also important to create an environment where high-performance can flourish which requires thinking and action at a management level. We examine three commentators perspectives on enabling high performance.
On the 1st November software engineer and author John R. Fox has published his book “Digital Work in an Analog World”. According to its subtitle “Improving Software Engineering by Applied Psychology”, the book does not consider software engineering in practice. Rather, it is focusing on the psychological aspects relevant and practices relevant for engineers.
There has been a lot of discussion recently about the tension inherent in the Agile Manifesto value "individuals and interactions over processes and tools". This item examines some of the points that have been made.
Most new Agile teams transition from hours based estimates to relative estimation using story points, but do we even need estimates at all?
Many people who are new to Agile are confused about the place of UI and UX design on Agile teams. Previously many teams have tried keeping the work separate from the team or having the work done one sprint ahead. Recently, there has been more talk about welcoming UI and UX into Agile teams and Lean UX has been at the forefront.
Rashina Hoda achieved her doctorate researching self-organizing Agile teams. She recently spoke to InfoQ about the work she's been doing and the results of her research. She discusses some of the factors that enable self-organization, looks at some of the risks and pitfalls that self-organizing teams face and provides some advice on how to create a culture that nurtures self-organization.