Agile Development Methods
Agile Development Methods
Agile Development Stories
|
What Do Our Customers Really Want?Agile teams can create software quickly, but how quickly can they gather and process feedback from customers? Here is one team's experience, with some tips and resources to help you introduce a community of practice in your own organization. | 
|
|
Busting Agile Prediction MythsWhen first hearing about agile processes, you might think that teams using an agile process cannot provide estimates, predictions, or commitments about what they will deliver. But, you can be agile and still manage risk and commit to a subset of what you predict. | 
|
|
Learning by OsmosisWe've got access to more information than at any time in history, but all that information can be a benefit or a burden. Don't squander your attention. Spend it intelligently, and make sure you get something of value in return for your time by adjusting your information intake. | 
|
|
Hero Culture or Crisis Culture?Organizations should avoid developing a "hero culture," but keep in mind that the heroes themselves aren't the villains. It's the organization's inability to handle difficult situations on a regular basis that leads to trouble. |
|
|
Learning to Self-organizeThe concept of self-organizing teams is one of the most important foundations of successful software development but also one that is often misunderstood. |
|
|
Agile: Not Just for IT Anymore—Or Is It? Should agile expand to other areas of business functions, such as marketing, human resources, public relations, finance, etc.? Joe Townsend believes the answer is "yes," "no," and "it depends." |
|
|
Agility through TeamworkAgile teams deliver business value frequently, adapting to the changing needs of the business, while working at a sustainable pace (paraphrasing Elisabeth Hendrickson’s Agile Acid Test). What’s the secret to achieving true “agility”? Why do so many software teams fail to achieve it? |
|
|
Fat Companies and Lean RequirementsHistorically, large companies relied on waterfall methods, but many of these organizations could benefit from a little "agile mojo." Applying aspects of hypothesis-driven development to requirements writing can help cut through the bureaucracy and put your team on a leaner path. |
|