Articles
 |
Try Mob Programming to Inspire Team Growth If you're familiar with pair programming, you know how much it can increase code quality and encourage developers to learn from each other. You should try mob programming—the same concept, but with an entire team of up to eight people and only one keyboard. It's a great way to explore new techniques and solve problems as a team. |
|
 |
Defining Acceptance Criteria for Agile Requirements Acceptance criteria can be helpful in expanding on user stories in order to capture requirements for agile projects. However, acceptance criteria should not be a route back to long, detailed documents, and they are not a substitute for a conversation. This article tells you how and when acceptance criteria should be written and employed. |
|
 |
The Benefits of Pair Programming This article details a team’s experience in implementing pair programming as a way to get work done as part of its agile transformation. It delves into the many positive results from the pairing experiment, as well as some of the negatives that were encountered, and weighs whether developers think pair programming is a worthwhile endeavor. |
|
 |
BSC West 2015 Keynote: Better Thinking for Better Software: Thinking Critically about Software Development Software developer Laurent Bossavit delivered the second keynote presentation, about why we need to think more critically about software development. He began his presentation by saying his intention was to make you question what you know—or what you think you know. |
|
 |
Always Read the Label: Getting the Most from Your Tools It is possible to find a new, innovative use for a tool, but it’s much more likely that you’ll do better using the tool in the way its creators intended. And whenever you reach for a tool, check that it’s actually going to help solve the challenge you’re facing. This article explains why first and foremost, conversation is more important than a shiny new tool. |
|
|
Top Twelve Myths of Agile Development When it comes to agile development, Allan Kelly has noticed a lot of misinformation is being passed off as fact. In this article, Allan takes a closer look at twelve of the most common agile myths he has encountered while training new agile teams. |
||
 |
Pair Programming in the Clink In this personal experience story, Daryl Kulak relates the day he spent behind bars. He was there to participate in a program that pairs prisoners with software developers “from the outside” to explore the art and science of agile software development. “It’s like a code retreat,” Kulak notes, “except it’s inside a prison.” |
|
|
Feature Injection: Part Two The tag-line for Feature Injection is "As we pull value from a system, we inject features." So before we can start, we need to identify the business value. But how do we do that? This edition also expands on the 20/20 vision conference concept. |
||
|
Mocks and Making Tests Easier to Read There has been a lot of recent discussion on Twitter about the use of mocking frameworks and writing readable tests. Here is a roundup of some of the recent blogs on the subject.
Making Tests More Readable |
||
|
Learning from Reading (and Rewriting) the Tests Automated unit tests verify that a component is working as expected. They also serve as a way to understand how code works, though this doesn't always happen by reading tests. Sometimes understanding comes from tweaking the tests to observe new failures, or rewriting the tests themselves. |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.