InfoQ Homepage Agile Content on InfoQ
-
Seniority, Respect, Authority and an Agile Team
Senior members, who have been working in traditional teams, can face issues related to respect and authority when they come to an Agile team. An interesting discussion on Scrum Development group and Agile India group tries to uncover answers that Agile might have for the situation.
-
Interview: Segundo Velasquez and Agile as Seen Through the Customer's Eyes
In an interview taken during the Agile 2007 conference, Deborah Hartmann interviewed Segundo Velasquez, co-founder of Mano a Mano Medical Resources, about his experience as customer with an Agile team during the initial phase of software design of a product.
-
Are there weaknesses with Collective Code Ownership?
The Agile development community has been practicing Collective Code Ownership for long enough now that we had enough time to find some of the faults.
-
Why Traditional Test-Automation Tools Stifle Agility
In recent times, much excitement has circulated about the direction of "next generation functional testing" tools. Alas, many agile organizations still struggle to make their traditional record-and-playback automated testing tools work for them. Elisabeth Hendrickson, aka "test Obsessed", tells them why to stop.
-
Article: Software Development Lessons Learned from Poker
There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? In this article, Jay Fields says: "It depends". The right choices varies with context, people, and more. This article touches upon how a lot of things must impact a choice; learning culture, skill levels, teamwork, incomplete information, metrics - and context.
-
Does Sustainable Pace mean a 40 hour week?
Sustainable Pace is a well known XP practice however, different people relate to it in different ways. Could an Agile team increase its sustainable pace by working longer? An interesting discussion on the Scrum Development group tries to debate the correlation between the number of work hours per week and sustainable pace.
-
Presentation: David Hussman on Automating Business Value with FIT and Fitnesse
In this presentation, David Hussman, founder of DevJam, discusses about user stories, the origin and authoring of story tests, focusing on how FIT and Fitnesse (FIT living within a Wiki) can be used to automate acceptance tests.
-
Does Your Team Have a Mission Statement?
Is your team juggling conflicting requests? Is your Product Owner struggling to decide which customer's to serve and which to ignore for now? Does it seem that everyone has a different agenda? Perhaps you need a mission statement
-
Impediments To Your Value-Stream
Scrum defines an impediment as "anything keeping the team from being more productive" and clearly stresses that teams establish means to remove them as continuously as possible. Joe Little proposes an impediment's scope may be better established as being anything keeping the organization from delivering value.
-
Lessons for the Agile Community from 8aweek
InfoQ recently had the opportunity to ask 8aweek co-founders Dave Fowler and Zachary Garbow some questions about how they connect with users, prioritize work, and get things done.
-
Don't Worry About Scaling Scrum
Most Scrum adopters have their first doubt in terms of its scalability. Tobias Mayer suggests that before looking into quick solutions for complex problems, adopters should focus on understanding the principles of Scrum. Once the foundation is correctly laid, Scrum will take care of scaling itself.
-
Stories of Scrum Adoption in China
This recent inquiry, by InfoQ China editor Jacky Li, looked at five very different cases of Scrum adoption in China, which got different results. He asked: Why did you use Scrum? How did you adopt it? What problems did you encounter, and why did it succeed or fail? Despite the small sample size, it's an interesting comparison, pointing out that improvement doesn't ensure success.
-
Complaint-Free Iterations
No software project is perfect, nor is the organization in which the project takes place. When your software project goes wrong, do your team members complain, or do they take corrective action? The Complaint Free World project encourages people to take notice of how often they complain, and reduce the frequency of the complaints, aiming for a goal of twenty-one complaint-free days.
-
Agile Version Control for Multi-Team Development
Many agree that the minimum set of Agile practices includes disciplined version control. In particular, when several development teams work in the same codebase, to ensure there's a clean, releasable version at the end of every iteration, they need a plan. Henrik Kniberg's proven scheme is a useful guide for teams. This detailed paper includes the entire method and even a cheatsheet.
-
Creating The Culture For An Agile Environment
Greg Smith offers an in-depth practical perspective on making your agile transition just as much about culture change as it is about process change.