No matter how well you've built it, no users will benefit from your product unless you can convince the buyers to purchase it. Selling to buyers is different than satisfying users—and you have to do both well to succeed. Consider the needs of the buyer as stakeholder. When you have no buyers, you have no users.
People collaborate—and don't—in a variety of ways. Johanna Rothman examines what happens when collaboration isn't working, and how to make it work. Watch for several barriers to collaboration including those imposed on people by the organization itself.
A software tester re-examines the role of software testers in quality assurance work, helping implement software development processes. If testers are knowledgeable, helpful, and supportive, they may be in the best possible position to help the team improve its software development process.
Jean Tabaka believes in the power of an entire agile organization. These ten characteristics of an agile organization may seem counter to market success, but she explores why they are wholly embedded in twenty-first century business success.
It's been said that, over time, charismatic movements often evolve to become "bureaucratic"—focused on a set of standardized procedures that dictate the execution of the processes within the movement. Has Scrum evolved to this point or is there still a place for agility in our processes?
Pair programming is an Agile practice that has been shown to greatly improve code quality without a huge increase in development time. This article explains the ins and outs of pair programming and some things you need to consider before you tell team members to grab a partner and get programming.
Requirements risks are among the most insidious risks threatening software projects. Whether it is having unclear requirements, lack of customer involvement in requirements development, or defective requirements, these troubles are a major culprit in projects that go awry. As requirements expert and agile coach Ellen Gottesdiener explains, agile practice can go a long way in mitigating the top five requirements risks.
How do you adapt inspections to a twenty-first century distributed workforce? A key part of the inspection process is the team meeting, which provides peer pressure to participate and consensus on defects. Teams working in multiple time zones have limited opportunities for the team meeting. A list of requirements and the functions needed to solve this problem based on real-world experiences should help anyone faced with this problem.