The Latest
|
agile 2008 -Jon Stahl - Sustainable Fun for Agile Development[article]
Podcast
Bob interviews Jon Stahl at the Agile 2008 conference. |
||
|
Metrics that Motivate[magazine] To implement a meaningful incentive system for your team, you need to select metrics that encourage the behaviors you need and the results you want. But first you have to decide what you need and want. |
||
|
Follow the Process[magazine] Building better software does not rely on methodologies. "Following the process" omits important human factors that ultimately lead us to success. |
||
 |
Simple Summaries Of Complex Projects[magazine] How can we meaningfully summarize—in a brief status report without losing important details—the successes and setbacks our projects experience? |
|
 |
Google Web Toolkit: Writing Ajax Applications Test First[magazine] In part two of the series, Daniel introduces Google Web Toolkit's testing infrastructure and demonstrates how to build an Ajax application test first. |
|
|
Getting Agile With User-Centered Design[magazine] Agile practices go a long way toward providing value to our customers. But in today's market, we must endeavor to adopt a more user-centered approach to create products our customers can't live without. |
||
|
Cover or Discover?[magazine] Excellent testing isn't just about covering the "map"–it's also about exploring the territory, which is the process by which we discover things that the map doesn't cover. |
||
 |
Keep Non-developers in the Loop[magazine] Keeping QA members up to date on changes as they happen–through meetings, wikis, and email–can reduce the number of unnecessary bug reports and save you time and frustration. |
|
 |
Encapsulation and Vampires[magazine] Encapsulation is more than just using the "private" keyword when defining a class. You need a boundary that keeps the vampires out. |
|
|
Does Name Matter?[article] The names we give to things can have a powerful influence on how we think about them and also on how we get others to think about them. In thiscolumn, tester, test manager, and consultant Fiona Charles examines names we have given to two essential roles in software development and explains why at least one of them is both inaccurate and a problem for testers. |
||
|
Unit vs. System Testing-It's OK to be Different[article] There are two distinct roles in many software projects that are involved with testing: developers and testers. Should they take the same approach to testing, or are there some principles that apply to only one of the roles? What should they do to coordinate their work? Danny Faught went through an exercise to compare and contrast and found that the questions he couldn't answer were as interesting as the questions he could answers. |
||
|
Multitasking Is Evil[article] Multitasking is often seen as a desirable skill—you can buy books or pay to attend courses that will teach you how to do it—but it is a surprisingly debilitating idea. |
||
|
Keep Both Oars in the Water - Tips for Modeling Requirements[article] If you hear that someone doesn't have "both oars in the water," you know he's out of control, he doesn't "get it," or he's going in circles. Why? To move forward in a rowboat, you need both oars in the water to steer and to gain speed. In this week's column, Mary Gorman explains how this concept applies to modeling requirements. |
||
|
Integrating Agile Practices With a Global Delivery Model[article] Agile development is getting increased attention from IT professionals all over the world. Agile practices help to overcome many of the challenges in traditional approaches with its emphasis on lightweight processes, flexibility to deal with changing business priorities, short delivery cycles, higher team collaboration, and a host of other benefits. Agile offers a fresh approach to businesses seeking greater agility in their software projects. |
||
|
Infrastructure Refactoring[article] Early implementations of Agile focused on brand new or newer product-lines. More recently, Agile is gaining acceptance in the legacy product space where the project teams are moving away from their company's traditional (aka, waterfall) methodology and moving toward an Agile approach. In these cases, the project team that begins to use Agile methods are typically inheriting an existing infrastructure that was constructed for a phased (aka, waterfall) approach. |
Pages
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.