'But I produced a note of my own saying that this is how programmers will organise their work and this is what I did when I first joined a team back in 1977 as a trainee programmer. ... Now I mean I went round and asked everyone and said look what I'm..the way I'm intending to organise the work is not very multi chaps, please suggest something else, I asked the consultants to suggest something else and nobody could so {so prototyping's out?} Well it is for this requirements certainly because an accounting requirement..we will try to involve them as much as we can. I mean when we have screens and reports that we can reasonably run through with them, we will. And if we don't have screens and reports that we can run through them then we will explain it in other ways. I am not going to have some kind of start programming and return to them half a year later saying, here it is guys surprise, surprise. ... 'X075 page 005.03a (tape 02.2.01f) Colin Notes/Tape 17/02/95
Social influence: | |
Technical influence: | Process: Methodology |
![]() |
Recording |
![]() |
![]() |
Story |
![]() |
Social influence | ||
![]() |
Technical influence |
![]() |
© Clare Tagg 2000