development

Articles

On Sumo, Architecture, and Enterprise Agile

In order to be successful in the ring, a sumo wrestler needs to maintain a heavy body weight and at the same time be in peak physical condition. Just as these Japanese athletes have to find the right balance through a well thought-out combination of diet and training regimen, software development organizations need a balanced approach to implementing application architecture on agile projects.

Identifying and Improving Bad User Stories

A written user story is a very short narrative—a sentence or two—describing some small piece of functionality that has business value. User stories are intended to foster collaboration and communication, but writing these short narratives poorly can negate agile’s flexibility. Charles Suscheck and Andrew Fuqua explain some common failure patterns that will help you focus on the right role, value, and business functionality when writing stories.

The Two Metrics that Matter

This article is designed to provide specific steps for understanding your development effectiveness. Getting this right will help move your software development group toward being a true business partner, if it is not already.

Neil Fox's picture Neil Fox
Continuous Integration and the Automated Database Update Process

Developers must have good feedback to ensure productivity. Most shops have a continuous integration (CI) build process that allows the developer to quickly know if a build failed, and some shops have an automatic deploy of the CI build to provide website feedback. Lance Lyons writes about an approach to automating the update of databases in a CI environment.

Lance Lyons
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.

My Experience with Test-Driven Development

Vinay Krishna explains why agile development includes testing and coding concurrently, which is also what test-driven development emphasizes. The transformation from coder to developer to tester is needed in all agile software development projects.

Vinay Krishna
Becoming Lean: The Why, What, and How

This article presents a different way of looking at lean software development; one that is independent of lean’s manufacturing heritage. It begins by presenting lean as a collection of a body of knowledge applying lean principles to software development.

Al Shalloway's picture Al Shalloway
Feature Injection: Part One

We are leaving the "last responsible moment" for a while. This month we start a discussion of Feature Injection, an analysis process based on real options and Kolb's circle of learning. The first episode ( of five ) introduces the "Information Arrival Processes.

StickyMinds Editorial's picture StickyMinds Editorial
What Software Developers Can Learn from Their Cafeteria

Did you know that Starbucks sells a cup size called "short"? It's a small cup that is less expensive than the other cup sizes. They never mention it on their menu; you have to know it exists before you can order one. Why? By having a smaller, cheaper option, they give their budget-conscious customers an opportunity to pay for coffee rather than go without. This kind of thinking has important repercussions to software developers.

Clarke Ching's picture Clarke Ching
Refactoring Doesn’t Mean Rewrite

Peter Schuh writes that it is not a good thing that the use of the term refactoring has grown so common, which makes him cringe every time he hears a business person say the word. Refactoring is meant to be one skill of many that is second-nature to a journeyman programmer.

Peter Schuh

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.