The Latest
 |
How to Hear Your Unhappy Code: An Interview with Cory Foy[interview] Cory Foy uses more than a decade of experience with agile and lean development to help developers create cleaner code, and also be able to know—or "hear"—when their code is unhappy. In this interview, Cory shows why constantly learning and evolving your language skills is so important. |
|
 |
The Agile Retrospective Wiki: An Interview with Rob Bowley[interview]
Video
The Agile Retrospective Resource Wiki provides an opportunity for agile practitioners to collaborate, share information, and gain new ideas about how to continuously improve not just the benefits from retrospectives, but also the processes behind the practice. |
|
 |
An Agile Approach to Thinking Up Front about Requirements[article] Thinking about interacting with the customer at the start of the project? Who would argue against that? Well, it depends on what you call it. It also depends on whether you then do it without the benefit of the rest of the project team. Here, Ulrika Park helps us see what an agile approach to thinking about the requirements might look like. |
|
 |
Why Dialogue Sheet Retrospectives Are Important[article] We all know we need to do retrospectives. And sometimes, it feels as if we go through the motions. Maybe with dialogue sheet retrospectives, we don’t have to. Here, Allan Kelly shares his perspective on dialogue sheet retrospectives. |
|
 |
What Are Your Metrics Trying to Tell You?[article] Joanne Perold writes that you cannot just look at the numbers; the context behind the data is often far more valuable. Metrics can tell a compelling story or provide meaningful information to anyone who wants to pay attention, but when the focus is only on the number, it can be a disaster. |
|
 |
Continuous Performance Improvement: An Interview with Marisa Müller[interview] In this interview, Marisa Müller offers advice for anyone looking to boost performance improvement at either the personal or team level. Learn how to stay motivated on the never-ending quest of continuous improvement. |
|
 |
Fix Your Agile Project by Taking a Systems View[article] Kathy Iberle writes that when working on a project, you should take a systems view, which allows you to see the whole development system at once. When you put on your “systems view” glasses, you’ll see that you need to deal with the whole system, not just a single team’s part of it. |
|
 |
What Decorating Cakes Can Teach Us about Iterations[article] Kent McDonald shares with us a story about decorating cakes and how that relates to doing agile the right way. To be truly effective, teams need to focus more on the need to reflect and adapt, and then figure out the best way to do that in their environment without worrying about whether they are doing it exactly right. |
|
 |
Keep Agile Testing Agile: An Interview with Aaron Barrett[interview] In this interview, Aaron Barrett gives advice that any QA team working with agile testing can utilize. Aaron covers everything from the importance of finding the definition of done to keeping collaboration from getting combative. |
|
 |
Piece By Piece: Test Estimation and Planning in Agile Teams[magazine] The iterative agile methodology provides a clearer vision, smaller time scale, and closer planning horizon. The authors look at approaches to estimation and planning, from product backlog grooming to task-estimating tables and more. |
|
 |
Problem Solving with Impact Mapping[article] Do your team members have a problem they can’t solve? Maybe it’s time to try impact mapping. In this article, noted author Lisa Crispin shows us how she uses impact mapping to solve problems. Impact mapping takes a lot from other brainstorming and planning tools, such as mind mapping and story mapping. |
|
 |
Agile Is Cheaper, Right?[article] Kenneth Grant explains whether or not being agile is really as cheap for an organization as its proponents claim it to be. Agile’s relentless focus on business value and just-enough work can help teams identify waste—or poor return on investment (ROI) requirements—and gives them the opportunity to change it or leave it out all together. |
|
 |
Using Mission and Risk Diagnostics to Enhance Business Continuity[magazine] Noah Gamer explains that mission and risk diagnostics provide an excellent approach to risk management for any company. Using these elements together, an organization can create a better business continuity strategy. While risk is not always bad, identifying and mitigating risks can help your organization achieve success. |
|
 |
Attacking Silos with DevOps[article] Many professionals, while having expertise in their technical niche, are sometimes less than perfect at communicating effectively with colleagues from other departments. This can result in departments failing to work effectively together; these departments resemble silos more than a collaborative and cohesive organization. This article will help you identify and understand some of the reasons why teams operate in silos and what you can do to change that. |
|
 |
Listen to What You're Saying!: An Interview with Steven "Doc" List[interview] Steven "Doc" List and Noel Wurst sit down for what starts as a standard interview about communication skills but quickly evolves into a fascinating conversation that reveals a lot about what we're saying—and what we should be saying. You may be surprised at just how much you have to learn. |
Pages
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.