Benefit Without Change
In recent years, the pressure to be more productive has led many organizations to look at alternative approaches to software development. A common problem, however, has been that even though the project team is supposed to use the new approach to be more productive, they were not supposed to stop doing any of their current software development activities. Needless to say, this is not very effective. It also creates a lot of tension for developers because they are never really sure which process they are supposed to be following.
Many organizations want to get the benefits from a new approach to software development without having to change anything. This happens all the time and is why it is sometimes necessary to talk about the difference between the espoused process and the actual process. My experience has been that the larger the gap between the espoused process and the actual process, the more stressed the team.
— Pete McBreen, Questioning Extreme Programming, Chapter 15
No Comments
This entry is filed under Questioning XP.
You can also follow any responses to this entry through the RSS 2.0 feed.
You can skip to the end and leave a response. Pinging is currently not allowed.