In Agile We Trust | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Opinion
Executive
Resources
|
Home > Departments > Methods & Means
It’s tough to build a foundation of trust on the quicksand of uncertainty. By focusing on today’s results and making consensus adjustments along the way, agile development helps project teams and customers focus on successes rather than failures. And it makes for happier humans, too.
This article is one in an ongoing series that invites project professionals to share practical advice, personal insights and pet peeves based on their experiences in the field. Anonymity, if desired, is assured. To submit an article for consideration, contact the editor.
Building trust between the customer and service provider is extremely difficult on software projects, yet without trust there is almost no way a project can succeed. One reason trust is so difficult to build is that the customer often cannot describe clearly enough what needs to be accomplished by the service provider. This may be because the customer doesn’t yet fully know what they want, or because the specifications supplied are incomplete, incorrect or subject to varied interpretations.
Whatever the reason for the lack of clarity, it is always hard to build a foundation of trust on the quicksand of uncertainty.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement