About (page 6)

I would go as far as to say that allowing software engineers to create their own plans and design patterns and to manage themselves is an extremely effective way of running a department for software houses as well, for a number of reasons. For example:

• They (the software engineers) are free to chip in with ideas of their own, which means that more (diverse) ideas are explored. Also improves their morale and confidence, because they're being listened to and allowed to contribute.
• They have a better idea about how a concept is going to be demonstrated in the software, compared to the producers of generic and overly complex design methodologies.
• Software Engineers are generally hands-on people who are skilled at knowing how to tackle a problem at various levels of granularity (e.g. as an overview, as goals and as tasks within those goals) at the same time. Trying to express this in a formal methodology can work, but it's hard and long work. This means that ideas can be forgotten by the time the methodology has been adhered to.
• Software is, like ideas are, evolutionary. Both can end up looking very different from what they looked like originally. No methodology I've seen, at least, is so flexible it can cater for an idea being removed completely, replaced or changed significantly in a quick and convenient way.

Page: 6 [ Prev | Next | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Homepage ]