InfoQ Homepage Agile Content on InfoQ
-
PairWithUs: On-Demand Agile Software Development Video Examples
One thing well known by most programmers is that the best (only?) way to learn programming technique is by example; specifically, watching someone else doing it. Antony Marcano & Andy Palmer's 'PairWithUs' gives people a great place to do just that.
-
97 Things Every Programmer Should Know
The 97 Things series continues, after the architect and the project manager, with things every programmer should know. InfoQ talked to its editor Kevlin Henney.
-
Need an Answer to Context Switching? Get Disturbed
Context Switching is defined as changing focus and attention from one task to the other in relatively short periods of time. It is widely considered harmful for the team member and the project that he is working on. Charles Miller mentioned a few ways of how they handle context switching at Atlassian.
-
Opinion: Racism in the Agile Community Hinders Learning
Earlier this month we published "The Role of Project Managers in Agile" by Vinay Aggarwal which contained some non-mainstream ideas concerning self-organizing teams. Unfortunately there were racist remarks left by readers. These remarks were removed and the offenders were banned. But this brings up another question, that of, "how does racism affect or ability to write and deliver software?"
-
Ruby Static Analysis Tools Roundup: metric_fu, Simian, Saikuro and More
Code quality tools for mainstream languages have reached a certain level of maturity, but tools for Ruby are still growing and become more important as Ruby spreads from early adopters to the early majority. InfoQ takes a look at the available code quality tools in the Ruby space.
-
Stanford Study Shows: Maxi-Multitaskers' Performance Impaired
A Stanford University study confirms that multitasking is definitely counterproductive: maxi-multitaskers fared worst in several standard tests. Agile implementors take note: there's good reason to urge each team to work on one product, with one product owner - splitting time across many tasks is a less effective way to work.
-
Key Elements of a Successful Agile Retrospective: Preparation and Participation
Agile retrospective helps the team examine what went well during the past sprint and identify the areas of improvement for the future sprints. However, sometimes the exercise of conducting a retrospective ends up as a futile effort due to lack of preparation. Moreover, key members of the team end up either not attending or not participating in the meeting.
-
PMI Launches Agile Community of Practice at Agile2009
The Project Management Institute (PMI) officially launched their Agile Community of Practice at the Agile2009 conference. The group's stated mission is: "To equip PMI Members with Agile skills and knowledge" Mike Griffiths has been credited with getting things moving when he issued a challenge at Agile 2007 that PMI form an Agile Specific Interest Group.
-
Tasktop Supports Integration with ScrumWorks Pro and ThoughtWorks Adaptive ALM Tools
Tasktop Technologies, the company behind Eclipse Mylyn Application Lifecycle Management (ALM) integration framework, now supports integration with Danube Technologies Scrumworks Pro and ThoughtWorks Studios Adaptive ALM software. Tasktop also released Tasktop Pro 1.5 version back in June.
-
Top Ten Tips for An Agile Coach
Rachel Davies and Liz Sedley, co-authors of the book Agile Coaching, gave a fun session “Top Ten Tips for Agile Coaches”. The session could well have been called “Top Ten Things that Many Agile Coaches get Wrong”.
-
Lean Is More Than a Toolset
Alan Shalloway urges people to understand that behind Lean's practices are important principles that practitioners would be wise to recognize.
-
Handling Project Termination
Terminating a sprint in Scrum is a rare event, but it does happen. An abnormal sprint termination can be called by either the team or the product owner. Most of the times terminating a sprint or the project leaves a sense of bad feeling. Robert K. Hurley and Joseph T. Jimmerson discussed the ways to deal with the trauma of a terminated project.
-
The Minimum Viable Product - a tool for exposing value
In a recent interview on Venture Hacks (Advice for Entrepreneurs) commentator Eric Ries discussed the concept of the Minimum Viable Product (MVP) – doing “just enough” to meet customer needs in order to get a product THAT PEOPLE WILL PAY FOR to market as soon as possible.
-
Measuring Agile Performance with the Agile Triangle
Traditional software development teams were supposed to work within the confines of the software 'Iron triangle'. The three sides of the triangle are Scope, Schedule and Cost. Jim Highsmith suggested that the Iron triangle, imposes a lot of constraints on the flexibility of the Agile teams and suggested an alternate Agile Triangle.
-
Giving and Receiving Effective Feedback
On Monday at the first day of Agile 2009 Liz Keogh ran a workshop and Effective Feedback.