InfoQ Homepage Agile Content on InfoQ
-
The Management View of Agile - Unaware or Unwilling?
A series of recent articles by Steve Denning on Forbes have highlighted the challenges that the Agile community faces to get acceptance by mainstream management.
-
The Exact Science of Communication Patterns
Alex "Sandy" Pentland, professor of MIT, talks about his experiments with sociometric badges in context of teams productivity in his interview for Harvard Business Review. His research can help in defining optimal communication patters that will make you and your team members more efficient and more satisfied at work.
-
Scrum Extensions Update - 1st Quarter 2012
What's happened with scrum extensions since our 4th quarter 2011 update? We asked Alex Armstrong, VP Business Development and Director of Programs at Scrum.org. This article summarizes our interview and discussion with Alex and gives the latest proposed scrum extensions.
-
Product Owner should deliver Enabling Specifications
Scrum community leaders recommend Product Owners to deliver an Enabling Specification as a part of a User Story to improve the efficiency of the development team.
-
Drilling Down Into Agile Success Factors
Scott W. Ambler provides some analysis on the latest Agile State of the Art survey. InfoQ follows up with some other insights and questions.
-
The Most Influential People in Agile
A recent post by Paul Dolman-Darrall on the Value, Flow, Quality blog proposed a list of the 20 most influential people in the Agile community.
-
The Daily Standup/Scrum is not for the Scrum Master
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.
-
Achieving More By Doing One Thing at A Time
A recent Harvard Business Review article highlights the importance of finishing one task at a time and hence getting more work done. Some of the core Agile practices help minimize context switching and bring a similar task focus while building software.
-
Agile Humour: A Wrap Up of April Fools Day 2012
The Agile community has a great tradition of making fun of itself and April Fools Day 2012 was no exception. Here is a wrap up of some of the best gags from this year that you may have missed.
-
A Collection of Agile Resources by J. Sutherland, K. Schwaber, D. Star, M. Lacey, and D. J. Anderson
Microsoft has put together a number of resources for Visual Studio developers, containing principles, practices and guidelines for Agile development. These resources are condensed articles written by influential Agile leaders -Jeff Sutherland, Ken Schwaber, David Star, Mitch Lacey, David J. Anderson - containing the essence of several Agile methodologies and being usable by any software dev team.
-
Is Agile Stifling Introverts?
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.
-
Frustration with the Role and Purpose of Architects on Software Projects
Is software architecture a poorly done and frequently neglected aspect of software projects? That’s the position put forth in a recent blog post by Simon Brown, an independent consultant and founder of CodingTheArchitecture.com. Brown contends that miscast architects and a casual approach to architecture on agile projects have contributed to the poor state of the architecture discipline.
-
Thoughtworks Technology Radar March 2012
ThoughtWorks recently published the latest update to its Technology Radar; a report produced to help technology decision makers understand emerging trends in software development techniques, tools, languages and platforms. There are some interesting observations of interest to Agile software development teams.
-
Your Tractor Was Built With Agile
A recent agile adoption at John Deere has lessons for companies that say "Can't work here." Focusing on the big bang approach instead of an incremental adoption pattern, John Deere crafted a process that works for most of its systems development.
-
Secure Code Development: A Casualty With Agile?
Agile teams are known to produce reliable and high quality code quickly. However, it is also a fact that pressure to deliver quickly might result in short cut reviews, curtailed testing and lack of attention to secure code. Is secure development as good as wishful thinking with Agile?