Agile Software DevelopmentAddison-Wesley, 2002 - 278 páginas Written for developers and project managers, this book compares software development to a game. Team members play the game knowing that the ultimate goal is to win - always remembering what they have learned along the way, and always keeping in mind that they will never play the same way twice. Players must keep an open mind to different methodologies, and focus on the goal of developing quality software in a short cycle time. Based on a decade's work and research, and interviews with software project teams, this book presents sound advice for bringing difficult projects to successful conclusion with a minimum of stress. |
De dentro do livro
Resultados 1-3 de 40
Página 96
... meeting in which a senior designer ruined a meeting's original plan by standing up and taking over the whiteboard for the rest of the meeting . In this case , the lack of anonymity created a social ranking that interfered with the ...
... meeting in which a senior designer ruined a meeting's original plan by standing up and taking over the whiteboard for the rest of the meeting . In this case , the lack of anonymity created a social ranking that interfered with the ...
Página 108
... meeting at this point , her thought structure falls to the ground and she must rebuild it after the meeting . It can take 20 minutes to build this structure and an hour to make progress . Therefore , any phone call , discussion , or meeting ...
... meeting at this point , her thought structure falls to the ground and she must rebuild it after the meeting . It can take 20 minutes to build this structure and an hour to make progress . Therefore , any phone call , discussion , or meeting ...
Página 143
... meeting , and I can interview those people to find out what happened in the meeting . Can you tell me the date of such a meeting , and who was in the room ? " TESTER : " Well , we were going to have it . I mean , you really should have ...
... meeting , and I can interview those people to find out what happened in the meeting . Can you tell me the date of such a meeting , and who was in the room ? " TESTER : " Well , we were going to have it . I mean , you really should have ...
Conteúdo
THE PROBLEM WITH PARSING EXPERIENCE | 3 |
THREE LEVELS OF LISTENING | 14 |
So What Do I Do Tomorrow? | 19 |
Direitos autorais | |
20 outras seções não mostradas
Outras edições - Ver todos
Termos e frases comuns
Adaptive Software Development Addison-Wesley agile methodology Agile Software Development apply artifacts behavior Cockburn cooperative game cost create Crystal Clear Crystal Orange culture deliver described diagrams discussion documentation effective example experience Extreme Programming feedback Figure game of invention goal grammers gramming Highsmith ideas increment information radiators interview iteration Jim Highsmith Kent Beck language-games look meeting ment meth method methodol methodology design Object-Oriented odology pair programming person Personal Software Process practice principle problem project manager project team question reflection workshop regression tests requirements role situation skills Smalltalk Smalltalk programmers software development someone sponsors story strategy structure successful sweet spot tacit knowledge team lead team members techniques testers tests Theory Building View things Thoughtworks tion understanding unit tests user interface user stories whiteboard write