InfoQ Homepage Agile Content on InfoQ
-
Integrated ALM Tools Are Fundamental to Success
The typical software delivery project captures requirements numerous times, describes tests in multiple places, is indiscriminate of what is in a particular build, and often requires a large amount of analysis to know who is doing what and why. Dave West looks at the problems this causes and argues for holistic, integrated ALM approach.
-
Automated Builds: The Key to Consistency
If there's one thing software developers are good at, it's automating things that used to be done manually. Making life easier for everyone by letting computers handle tedious repeatable tasks, allowing people to focus on what matters to them is what we’re here for. However, development teams often neglect the one audience that would benefit the most - themselves.
-
Interview with Yves Hanoulle on the Agile and Lean Mindset
At the XP Days Benelux 2012 conference, Yves Hanoulle did a session about the agile and lean mindset. InfoQ spoke with him on the mindset, his experiences with pair working, and how he collaborates in the agile community.
-
Tradeoffs: Giving up Certainty
While organizations operate under an illusion of certainty, tradeoffs are inevitable. Giving up certainty does not mean giving up predictability. This article examines four flow choices for software delivery and presents three choices for IT Delivery: Throughput, Flexibility and all out speed.
-
Why the Agile Project Manager is the Secret Sauce for Development Projects
The Agile project manager is sometimes referred to as the “secret sauce” for software development projects? Leo Abdala describes a recent development project at a Fortune 50 company where the Agile PM instilled confidence with and produced a value-generating product for the client
-
Why Agile Methods Work
There is great economic value in looking at software processes from an execution perspective to examine their strengths and weaknesses. Keeping this perspective in mind keeps us at a safe distance from abusing buzzwords like Agile methods without really understanding the underlying principles that make them work.
-
Visualizing the Big Picture of your Agile Project
Agile is all about the whole team experience. We plan together, code together, test together, and retrospect together so that everyone in the team is all on the same page. However, once your project grows bigger, teams start to get lost in pile of user stories and it gets harder for everyone to see that same big picture. This article discusses various ideas to visualize this big picture.
-
Interview and Book Review: Essential Scrum
Essential Scrum by Kenny Rubin is a book about getting more out of Scrum. It’s an introduction to Scrum and its values, principles and practices, and a source of inspiration on how to apply it.
-
Metrics-Driven Development
In this article the author shares his thoughts and experience gathered while working together with DEV teams, trying to make sense of metrics. He introduces the practice of Metrics-Driven-Development: using metrics to drive the entire application development.
-
Book Review: The Scrum Field Guide
Mitch Lacey has written the book The Scrum Field Guide: Practical Advice for Your First Year in which he presents advice on how to implement many of the Scrum and XP practices. Shane Hastie from InfoQ reviewed the book and asked the author some questions about the approach. The publishers have made a sample chapter available for InfoQ readers.
-
The Prioritization Divide: With Numbers or Without?
While there are many methods that use stories as a means for prioritizing development, there's a basic divide that asks whether it should be done with numbers or without. There are arguments on both sides, but instead of examining these, people tend to fall into one side naturally. Once there, they can become quickly entrenched in the belief that the other camp is foolishly mistaken.
-
An Alternative to Agile Coaching
Phil Abernathy asserts that the role of the Agile Coach may be due to sunset - he proposes an alternate based on his vision of an Agile Practitioner Manager embedded within an agile team. The Agile Practitioner Manager will have "skin in the game" being responsible not just for helping the team with their process but also being accountable for the deliver of customer value through the product.