InfoQ Homepage Agile Techniques Content on InfoQ
-
The Further Value of Collapse
Mike Burrows started a discussion on the Kanbandev group which has led the community to explore the Expand / Collapse pattern. The discussion was covered elsewhere on InfoQ, in an article which followed the viewpoints of many practitioners who see more value in expansion than collapse. However, many people found both aspects of the pattern useful.
-
The Value of Collapse?
Agile methods recommend decomposing ("expanding") features into many small user stories. After the code has been written, however, should we collapse these small stories back into the original feature so we can deal with them all as a unit? Are there any advantages in doing that collapse, and if so, what are they?
-
BDD: ATDD done well?
A new form of an old question has been asked in the Behavior Driven Development community: is BDD merely Acceptance Test Driven Development done well? While the community calls out the differences, Dan North makes a request to avoid focusing on them, calling TDD "amazing".
-
Agile is Just a Piece of the Puzzle
Recently, there were a lot of views expressed around the so called downfall of Nokia and whether Scrum was helping the organization at all. Similar concerns and thoughts were raised when Toyota had recalled cars dues to quality issues. Is Agile 'the core' factor in product development ?
-
Adaptive Leadership to Accelerate Organizational Agility
Responsive strategy, being and doing Agile are keys to effective adaptive leadership within an Agile organization. Jim Highsmith spoke recently at AgileAustin event about adaptive leadership and how it can accelerate and sustain organizational agility. He said that agile leaders should focus on aspects like quality and speed to value as executive levers to achieve business goals.
-
Taking a Break From Sprinting
Over the long term, can teams sustain constant work on the product backlog? If a break is needed, what's the most effective way of doing it?
-
Should the Product Owner Also Be the ScrumMaster?
What are the advantages and disadvantages of having the same person fill both the Product Owner and the ScrumMaster role on the same Scrum project? Is this really a workable option?
-
Starting Test Automation for a Legacy Project
It is always a herculean task to write automated regression tests for a legacy application. The questions vary from where to start, how much to automate and deciding on the best strategy for automation.
-
Myths of Kanban
How has the Lean development practice of Kanban been misunderstood? Learn to separate fact from fiction when it comes to Kanban.
-
Swarming: What's the Point?
Agile teams are encouraged to focus all their effort, as much as possible, on one story at a time--a practice known as "swarming." But why do this? What are the benefits you can expect to see by swarming each story?
-
Getting the Customer Involved
Agile methods place a strong emphasis on customer feedback and interaction. Projects with involved customers have much higher chances of success than projects which lack customer interaction. So, how do Agile teams keep the customer involved.
-
Should We Move a Failed Story Back?
What should we do with a story on our task board when it fails testing?
-
Agile/Scrum Retrospectives–Tips and Tricks
Retrospectives and feedback loops are at the heart of any successful Agile/Scrum implementation. They’re the tool we use to help teams improve. Yet in two day introduction to Agile classes they often get glossed over. Lacking time trainers (including this one) often race through the topic outlining only one simple type of retrospectives.
-
Is the Agile Retrospective Prime Directive Patronizing?
Angela Harms recently blogged about the Agile Retrospective Prime Directive. She discusses how the language of the prime directive around "everyone doing their best" could be seen as patronizing and insulting to team members. Other commentators who have discussed the intent of the Prime Directive include Esther Derby and George Dinwiddie. How useful is the Retrospective Prime Directive?
-
How To Pay Down Technical Debt
Technical debt can be difficult to connect directly to customer value, but delivering customer value is what Agile processes are all about. So how can we track and reduce technical debt in an Agile development environment?