InfoQ Homepage Agile Content on InfoQ
-
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.
-
Agile 2009 Coverage
Several InfoQ editors will be attending the Agile conference this week and reporting on the sessions. Stay tuned to InfoQ to read the latest about the happenings at the conference and get reports about the most interesting and provoking sessions.
-
DeMarco Reflects on 40 Years of Software Engineering Evolution
40 years after the NATO Conference on Software Engineering, Tom DeMarco paused to reflect on the discipline's evolution, wondering whether the metrics orientation he championed has distracted from the real point of computing: "transformation, creating software that changes the world." Is his earlier advice valid, though? "No", he said, in Software Engineering: An Idea Whose Time Has Come and Gone?
-
Agile Adoption: Projects Should Dive-In, Organizations Should Toe-Dip
Hearty debate abounds about whether agile adoption is better done in a gradual "toe-dipping" manner or with an all-or-nothing "head-first dive" approach. Johanna Rothman says do both: projects should dive all-in, while organizations should take it gradually.
-
How to Transfer Knowledge in an Agile Project
Knowledge transfer is characterized by transfer of understanding, about a context, from one unit (individual, team, department, organization) to another. In a series of interesting experiments, Steve Bockman tried to figure out the best way to transfer knowledge in an Agile project.
-
Categorizing Tests
What's the difference between unit tests, functional tests, system tests and integration tests? What about developer tests, story tests, and acceptance tests? There seems to be no consensus on naming and categorization of tests although they are central to many Agile development processes. A discussion on the TDD discussion group examines these categorizations and attempts to clear the waters.
-
How Can Management Contribute to an Agile Project?
Mark Balabanian, new appointed COO of Accunote, asks the question how can a manager/management help a Scrum team. Having read one Scrum book, he was trying to understand what do next. Cory Foy, John Galvin, Peter Stevens, Lysaa Adkins and Micheal Spayd provide advice.
-
Two Types of Agile Documents - No More, No Less!
The Agile Manifesto suggests “ Working software over comprehensive documentation”. This has led many teams to believe that there is no need for documentation in Agile projects. Critics of Agile use limited documentation in Agile to showcase the weakness of Agile methodologies. Eelco Gravendeel suggested that there are just two types of documentation in Agile.
-
Enabling the Last Responsible Moment in Deployment
An interesting question can be asked during a design decision: "Does this approach create a commitment" rather than "is this the right design?". A conversation on the KanbanDev Yahoo! group explores this question, different approaches to implement an effective answer, and the benefits to be reaped by this approach.
-
A Quick Look At The 7 Wastes of Software Development
Fundamental to Lean Software Development is the pursuit of minimizing waste. The TPS publicized 7 primary wastes of manufacturing, and the Poppendiecks have since translated these wastes to our world of software development. Jack Mulinsky has recently been posting an introductory series on these wastes at agilesoftwaredevelopment.
-
Software Debt Adds Up to Substantive Costs
In a recent article entitled “Continued Delivery of High Values as Systems Age”, Chris Sterling discusses the concept of Software Debt – “Software debt accumulates when focus remains on immediate completion while neglecting changeability of the system over time.” Software Debt goes beyond technical debt an encompases a variety of aspects that impact on the ability to deliver value.
-
Agile Addresses "The Five Dysfunctions of a Team"
Tathagat Varma, general manager with a large provider of IT management solutions, wondered whether Agile's productivity improvements could be linked to how it improves teamwork. His article analyses Agile values and practices by mapping them against Patrick Lencioni's business fable "The Five Dysfunctions of a Team."