|
What's It Mean? ...Reducing Imprecision to Improve Verification Imprecise language makes understanding and, therefore, software verification more difficult. This article describes techniques for detecting and repairing vague and ambiguous software requirements.
|
|
|
Navigating Conflict On good agile teams, conflict is frequent and viewed as normal. On great agile teams, conflict is constant and welcome as a catapult to high performance. What can we do to help teams chart their course through conflict so that it turns into a constructive force for greatness?
|
|
|
Are You a Good Listener? Some people freely admit that they're not good listeners. But many who claim to be good listeners aren't. That's because they fall short in a critical aspect of listening. In this week's column, Naomi Karten offers ideas and examples that will help you be-and be perceived as-a good listener.
|
|
|
Six Ways to Build Trust and Three Ways to Break It Esther Derby has been thinking about trust in the workplace a lot lately, and the absence of trust, too. When she asks people what it's like to work in a group where people trust their managers, they tell her information flows freely, conflict is productive, and that they can tell their managers what they think without fear of retribution. On the other hand, when trust is absent, people hide information, look out for themselves, don't bring up new ideas, and withhold effort.
|
|
|
The Missing Measurement In these times, many of us are being told to "do more with less." A more useful approach is "invest our organization's scarce resources where the return is the greatest." To do so, we must define the financial benefits sought when developing a system in addition to its requirements.
|
|
|
What's Going Right Around Here? Instead of focusing on the problems, focus on what works. That is the simple premise of "appreciative inquiry." In this week's column, Ellen Gottesdiener explains how to help your team focus on the processes that work by outlining what should be included in your appreciative inquiries, in order to make more positive organizational changes.
|
|
|
Go, Team! Fed up with good-ol'-boy salesmen, a manufacturing mindset, and just-get-it-out-the-door directions? A little assertiveness, a few ounces of patience, a dash of charm, a lot of leadership, and some attitude adjustment by everyone might help. Read how one manager made the world a better place to work one small victory at a time.
|
|
|
Not Wanted on the Voyage Back in the day of cross-Atlantic boat travel, luggage that wasn't needed during the long journey was labeled "Not Wanted on the Voyage" and stowed away below decks. In this column, Fiona Charles suggests that testers can also be viewed as heavy baggage and not exactly welcome by some parties during the journey of software development. To understand why others might think this way, Fiona takes a good, hard look at what testers do that could possibly make them undesirable team mates.
|
|
|
An Agile Approach to Scheduling When we schedule too many variables, things start to slip and soon the schedule is out the window. Paying attention to your project's constraints can help you set realistic scheduling goals that you will actually be able to stick to.
|
|
|
Retrospectives in Action - Looking Back at the Conference In this last-day, last-hour session, Jean Tabaka invites you to apply a fundamental practice of agile teams-retrospection. Jean guides you in facilitating your own retrospectives about the Agile Development Practices conference you have just attended. You will mine your experiences by creating a timeline of your conference observations, your high points, your low points, and your conference activities. Each team will then use their timeline of observations, impressions, and actions to interpret how their overall conference experience might impact what they could do differently at the next conference, what they would recommend as changes for the Agile Development Practices conference organizers, and what they might recommend even outside of the conference context. Finally, each team will prioritize their recommendations to be collected and delivered to the Agile Development Practices conference organizers.
|
Jean Tabaka, Rally Software Development
|